Increase visibility into compliance and the security state of systems across the organisation with in-depth auditing and reporting.
Reduce the number of usernames and passwords needed to login.
I only have about eight Windows 8.1 machines so if I have to do that by hand for now then I will and I think my organization will be moving to Server 2012 and SCCM 2012 this summer sometime.
NOTE: It looks like Forefront is getting the definition updates just fine but even if I do a manual Windows update check the client/AV Engine updates do not even show up as an option.
Type : Error Date : 2/02/2010 Time : PM Event : 6014 Source : Get Engine Files Category : Engine Error User : N/A Computer : Dc Ex01 Description: Microsoft Forefront Server Security encountered an error while performing a scan engine update.
Scan Engine: Worm List Update Path: List Proxy Settings: Enabled Error Code: 0x80004005 Description: An error occurred while checking if an update was available.
You will know that it is not updating when you see an amber symbol with an exclamation mark on the bottom right hand corner of your screen.
If you double-click the amber symbol, you can verify that Forefront is not updating automatically by looking at the date at the bottom of the window.
I am wondering if I manually install the 4.1 client update if it will take the client updates after that.Nothing in the update logs that I can see to shed any light onto the cause.Microsoft Update (Automatic Updates) must also be enabled to receive definition updates.Only way I know of fixing it: downloading manual updates, which gets annoying over time. Recently I noticed that my Windows 8.1 clients were not getting updates from WSUS 3.2.
One quite common problem that administrators might encounter is this: Scenario: Exchange 2010 environment.