Updating the Windows Update Agent on Windows 7 clients

25

The last 2 months or so we’ve worked hard with many of our customers to fix a small problem with the Windows Update Agent on Windows 7.

More Information on this problem:
http://blogs.technet.com/b/configurationmgr/archive/2015/04/15/support-tip-configmgr-2012-update-scan-fails-and-causes-incorrect-compliance-status.aspx

Last night Microsoft released an update for this specific problem and this blog post will explain how to deploy this fix in your environment.

Download the update

Start by downloading the Windows Update Agent version 7.6.7601.18847 for Windows 7 here:

https://support.microsoft.com/en-us/kb/3050265

Create Collections

In this example I’m using two collections as limiting collections that I’ve created earlier.

clip_image002Β Query (x64):

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceID = SMS_R_System.ResourceId inner join SMS_G_System_OPERATING_SYSTEM on SMS_G_System_OPERATING_SYSTEM.ResourceId = SMS_R_System.ResourceId where SMS_R_System.OperatingSystemNameandVersion like “%Workstation 6.1%” and SMS_G_System_OPERATING_SYSTEM.Version = “6.1.7601” and SMS_G_System_COMPUTER_SYSTEM.SystemType = “x64-based PC”

Query (x86):

select
SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceID = SMS_R_System.ResourceId inner join SMS_G_System_OPERATING_SYSTEM on SMS_G_System_OPERATING_SYSTEM.ResourceId = SMS_R_System.ResourceId where SMS_R_System.OperatingSystemNameandVersion like “%Workstation 6.1%” and SMS_G_System_OPERATING_SYSTEM.Version = “6.1.7601” and SMS_G_System_COMPUTER_SYSTEM.SystemType = “x64-based PC”

And then I’ve created two new collections that I can use to target my deployments:

clip_image004

Query:

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client 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 < “7.6.7601.18847”

 

Create and Deploy the Software Package

1. Create a software distribution package for the downloaded Windows Update Agent installation files as shown in the screenshot below.

clip_image006

2. Create two programs for the software distribution package. One for x86 and one for x64 like this:
Wusa.exe “Windows6.1-KB3050265-<platform>.msu” /quiet /norestart

3. Create a deployment that targets the client computers that do not have the updated version on the Windows Update Agent. Specify the collection that was created in the preceding procedure.

clip_image008

4. Don’t forget to monitor the deployment. This update does require to be restarted, so don’t expect to be compliant before all clients has been restarted.

clip_image010

That’s it…

Until next time….

+Ronni Pedersen

About Author

My name is Ronni Pedersen and I'm currently working as a Cloud Solution Architect at EG A/S in Denmark. My primary focus is Enterprise Client Management solutions, based on technologies like AzureAD, Intune, EMS and System Center Configuration Manager. I'm is also a Microsoft Certified Trainer and Microsoft MVP in Enterprise Mobility.

25 Comments

  1. Pingback: Windows Update memory leak

  2. If you wanted to deploy this as an application rather than package; what would be the best detection method?

  3. Just curious, this update shows up under the list of updates when you sync the SUP. Can you not simply deploy using software updates?

  4. I think your X86 query is incorrect…simple because it looks jsut like the x64 query…I think you want the system type to specify x86…

    πŸ™‚

  5. Ronni, there is in error in your x86 query, it must be

    ….and SMS_G_System_COMPUTER_SYSTEM.SystemType = “x64-based PC”

    I think it’s just a c&p error πŸ™‚

    Ben

  6. Pingback: Windows Update Client: system performance can be decreased during scans « Yuriweb's Weblog

  7. For all of you trying to update an old or fresh installed win7:
    Leave it 24hours “checking for updates”. It will find over 200 updates πŸ˜‰

    Why ms-chat-support didn’t know this! And why do they end a chat as soon as I’m trying to explain it to them to help others. Then they don’t waist time like they did with 10 hours remote control on my pc!

    MS really is trying to let us choose to “upgrade” to win10. On win10 updates are very fast, but on win7 you need to let your pc go searching for updates days!

  8. Pingback: Windows Update Agent Build Numbers for Windows 7 | Potent Engineer

Leave A Reply