Author: Harini Muralidharan, Program Manager, Configuration Manager Sustained Engineering
Applies To: System Center 2012 Configuration Manager SP1, and System Center 2012 R2 Configuration Manager.
This article describes the steps to update to the latest Windows Update Agent version for Configuration Manager Clients.
Approve KB 2937636 through the Configuration Manager console and the update will be deployed on the client computers, just like updates for other Windows components.
The standalone installer applies to Windows Vista with SP2, and Windows 7 RTM or SP1. For Windows 7 SP1, the standalone installer will install the client version Windows Update Agent7.6.7600.320. For all previous versions, the standalone installer will install the client version 7.6.7600.256.
The following procedure provides the steps to download the installation file, create a query for computers that do not have at least Windows Update Agent version 7.6, create a collection based on the query, and create a software distribution that targets the new collection.
The following files are available for download from Windows Update.
All supported x86-based versions of Windows 7 SP1 and below
Download the package now.
All supported x64-based versions of Windows 7 SP1 and below
All supported x86-based versions of Windows Server 2008 R2 SP1 and below
All supported x64-based versions of Windows Server 2008 R2 SP1 and below
All supported Itanium-based versions of Windows Server 2008 R2 SP1 and below
SELECT SMS_R_System.NetbiosName, SMS_G_System_WINDOWSUPDATEAGENTVERSION.Version FROM SMS_R_System INNER JOIN SMS_G_System_WINDOWSUPDATEAGENTVERSION on SMS_G_System_WINDOWSUPDATEAGENTVERSION.ResourceID = SMS_R_System.ResourceId WHERE SMS_G_System_WINDOWSUPDATEAGENTVERSION.Version < "<enter latest Windows Agent version>" order by SMS_G_System_WINDOWSUPDATEAGENTVERSION.Version
Note: The latest Windows Update Agent version for Windows 7 RTM and below clients is 7.6.7600.256 and the latest Windows Update Agent version for clients with Operating System Windows 7 SP1 and higher would be 7.6.7600.320
The sample query will return all computers with a version of the Windows Update Agent that is less than the latest Windows Agent version. The query will return only the computers that have a value for the Windows Update Agent version, which requires the computer to scan for software updates at least once and then take hardware inventory.
Refresh or reload the Configuration Manager console to see the collection members. However, the members will not appear in the collection until after the first scheduled update, or until you manually select Update Membership for the collection. Depending on the complexity of the collection rule and the number of entries in the Configuration Manager database, it can take a few minutes for a collection update to complete.
Update to Microsoft Update Client – KB 2937636
Upcoming Update for Microsoft Update Client blog post
Configuration Manager Resources
Documentation Library for System Center 2012 Configuration Manager
Configuration Manager 2012 Forums
System Center 2012 Configuration Manager Survival Guide
System Center Configuration Manager Support
This posting is provided "AS IS" with no warranties and confers no rights.
How come you're not providing guidance to customers to use the new Application model? Performing this deployment using the legacy Collection / Package / Program methodology could result in greater failure, because each local system is not evaluating its
current state prior to executing the deployment.
Microsoft MVP: PowerShell
@Trevor, you are right .. How come?
Outside of your blog mentioning Vista SP2, nowhere else is Vista mentioned in
http://support.microsoft.com/kb/2887535. Can you confirm Vista is included?
Will the new WUA be made available via WSUS for Windows 7 SP1 clients?
You are right, the KB did not mention Windows Vista. There was no separate stand alone installer that was released for Vista. The stand alone installer for Windows 7 SP1 will work on down-level OS like Win7 RTM and Vista SP2, it will pull down and install
previous WU Agent 7.6.7600.256 on the down-level OS as described in the blog.
WindowsUpdateAgent30-.exe /quiet /norestart /wuforce.......
Correct Filename ist WindowsUpdateAgent-7.6-.exe
Despite that: Famous article! ;-)
@Joerg. Thank you, I have updated the blog post.
@Damon, you may be looking for this information:
WSUS KB Article: http://support.microsoft.com/kb/2938066
WSUS Blog post:
How does this affect SCCM client installations, especially re-installs? The setup will attempt to install the old agent and I'm afraid this process will conflict.
I was able to get the software deployed via the Application model using the script install method with the command line mention above.
The detection method is set to detect the wuapi.dll version 7.6.7600.320 located in the %Windir%\System32 and %Windir%\SysWOW64.
Set the Operating system so it is limited to Windows 7 or Server 2008 systems.
It seems that x64 packages are broken. Their size is only 8,97 KB... :-(
Excellent post. I'm very happy to see the return of a WUA that can be installed manually. Thank you too, GlenMunro, for helping out with the detection method on an application model.
I'am just wondering, is there any differences between WS2008 and W7 installers? They seem to be the same and both work on windows 7 and server 2008. Btw, ms recommends checking version of wuaueng.dll. Wuapi.dll is not updated until restart.
On my machines at least, wuapi.dll is was not updated until system was restarted. Use wuaueng.dll for detection rule. Btw, what are diferences between installers for windows 7 and servers 2008 r2? 2008 R2 x86 - ms just released new version of OS ?