• State Not Answered
  • Locked Locked
  • Replies 8 replies
  • Subscribers 21 subscribers
  • Views 1318 views
  • Users 0 members are here
Options
Related
This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

WU Agent Maintenance/Repair - Locating the current WU Agents

grandgroove

I have a couple of workstations that have been experiencing issues with proper synchronization and downloading of updates via WSUS. The next step is to run Patch Manager's Windows Update Agent Maintenance and Repair to clear up a couple of things on each machine. Our WU agents are at 7.5.7601.17514 according to each machine's Windows Update Settings in Computer Explorer.

WUAgentVersionListing.JPG

The SolarWinds WSUS Diagnostic tool shows the latest update version (7.6.7600.256), so I may be reading something incorrectly. As long as I'm pushing our the proper agents, it isn't a big deal. I ran Report-WSUS Server Computers Info, and the WUA client versions all reported 7.6.7600.256 as well.

PMDiagWUVersion.JPG

Part of the WUA Maintenance/Repair procedure pushes a fresh copy of WUA to the client for installation. However, the default Microsoft-based one that I've been using is an older version.

WUAgentDownload.JPG

Our WSUS server is at 3.2.7600.226. PM is at 1.72.218.2. The machines what would need this agent reinstall are running  Windows 7 x64 Professional.

Is there a place locally where I can locate the current agents, or does anyone have an updated URL to point to the current agents?

-Jay

  • 0

    Greetings Jay.


    Some good points and questions from your post, and a lot of this all wraps around the WSUS update in KB2720211 that came out last month.

    The WUAgent v7.5 systems would be Win7SP1 and Win2008R2SP1 systems. SP1 updated the WUAgent from v7.4 (which shipped with WSUS3SP2) to v7.5.

    KB2720211 and any connections with AU/WU/MU since June's Patch Tuesday will result in the WUAgent being updated to v7.6.7600.256 on all supported Operating System platforms. The WSUS Diagnostic Tool will flag notable instances where downlevel WUAgents (v7.2, v7.1, v7.0, etc.) are installed, but generally anything v7.4 or newer will be reported as 'OK'. If you have not deployed KB2720211 to your WSUS server(s), but you have clients reporting a v7.6 WUAgent -- that will be problematic and is likely the root cause of your observed client failures. The new v7.6 WUAgent cannot communicate with the pre-KB2720211 (v3.2.7600.226) builds of WSUS. The v7.6 WUagent requires v3.2.7600.251 (which is what KB2720211 will update).

    The WUAgent Maintenance & Repair tool has a default pathname to the v7.4 WUAgent -- which is, sadly, still the only version available in a standalone installer format. Hopefully customer pressure will motivate the WUAgent team to bundle this v7.6 installer, and then it will also be installable from the WUAgent M&R tool. In the meantime, installing the v7.4 WUAgent is really only appropriate for Win7/Win2008R2 *RTM* and earlier systems -- and only to the extent that the WSUS server has not yet been updated with KB2720211.

    Having said that, if you need to downgrade a Win7/Win2008R2 *RTM* (or earlier) system to the 7.4 WUAgent, you can use the /wuforce parameter to force the installation of the WUAgent. But don't do this on a Win7/Win2008R2 *SP1* system, because they won't work with the v7.4 WUAgent.


  • 0 in reply to LGarvin

    There is a split in WUA versions according to OS. My Win 2003 and Win XP/Vista machines (both x86 and x64) are all at WUA 7.6.7600.256. The Win7 and Win2K8 machines (both x86 and x64) are all at 7.5.7601.17514. I confirmed that we had approved KB2720211, and it's installed on the WSUS servers. I re-ran the WU agent repair task on the Win7/Win2K8 to make sure everything was good. I did a random review of WindowsUpdate.log files, and there were no errors.

    Here is the weird thing: I ran the WU Diagnostic Tool on a few of the Win7/2K8 machines, and the agent version it shows is the current one (7.6.7600.256). I also checked a couple of files in C:\Windows\System32 (wuauclt.exe, wuapi.dll, wuaueng.dll), and they all check out at this same version. I can't figure out the discrepancy. The information I mentioned in the first paragraph came from a report in Patch Manager (Reporting->WSUS Reports->Windows Update->Windows Update Agent Version Info).

    What do you think I am missing?

    Thanks!

    Jay

    Added info re: local spot check of Win7/2K8 machines.

  • 0 in reply to grandgroove

    They should be updating from the v7.5 agent to the v7.6 agent if KB2720211 has been installed.

    While there may not be any errors, per se, in the WindowsUpdate.log, check to see if the log entries show the v7.6 agent as being available.

  • 0 in reply to LGarvin

    Here is the most recent snippet of activity from a WindowsUpdate.log file. I can't fully interpret everything, so I could be overlooking errors. Would this be enough for you to determine anything? I omitted the actual server name since this is a public posting. I can send you a full log via in private message if you want.

    **********

    2012-07-1621:20:52:465 98010b0AU#############
    2012-07-1621:20:52:465 98010b0AU## START ##  AU: Search for updates
    2012-07-1621:20:52:465 98010b0AU#########
    2012-07-1621:20:52:474 98010b0AU<<## SUBMITTED ## AU: Search for updates [CallId = {DEBCEBEE-8338-4CC5-A163-26CE94D7CF19}]
    2012-07-1621:20:52:475 9807c8Agent*************
    2012-07-1621:20:52:475 9807c8Agent** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2012-07-1621:20:52:475 9807c8Agent*********
    2012-07-1621:20:52:475 9807c8Agent  * Online = Yes; Ignore download priority = No
    2012-07-1621:20:52:475 9807c8Agent  * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
    2012-07-1621:20:52:475 9807c8Agent  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2012-07-1621:20:52:475 9807c8Agent  * Search Scope = {Machine}
    2012-07-1621:20:52:511 9807c8SetupChecking for agent SelfUpdate
    2012-07-1621:20:52:512 9807c8SetupClient version: Core: 7.6.7600.256  Aux: 7.6.7600.256
    2012-07-1621:20:55:133 9807c8MiscValidating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2012-07-1621:20:55:172 9807c8Misc Microsoft signed: Yes
    2012-07-1621:20:55:196 9807c8MiscValidating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2012-07-1621:20:55:214 9807c8Misc Microsoft signed: Yes
    2012-07-1621:20:55:237 9807c8SetupDetermining whether a new setup handler needs to be downloaded
    2012-07-1621:20:55:237 9807c8SetupSelfUpdate handler is not found.  It will be downloaded
    2012-07-1621:20:55:238 9807c8SetupEvaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
    2012-07-1621:20:57:383 9807c8SetupSetup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2012-07-1621:20:57:384 9807c8SetupEvaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
    2012-07-1621:20:57:427 9807c8SetupSetup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2012-07-1621:20:57:427 9807c8SetupEvaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
    2012-07-1621:20:57:489 9807c8SetupSetup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2012-07-1621:20:57:490 9807c8SetupSelfUpdate check completed.  SelfUpdate is NOT required.
    2012-07-1621:20:57:988 9807c8PT+++++++++++  PT: Synchronizing server updates  +++++++++++
    2012-07-1621:20:57:988 9807c8PT  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = <OMITTED>
    2012-07-1621:20:58:042 9807c8PTWARNING: Cached cookie has expired or new PID is available
    2012-07-1621:20:58:044 9807c8PTInitializing simple targeting cookie, clientId = 38b0ed20-134a-453d-a7fa-d040b6767ca0, target group = , DNS name = cpc-010.iii.terminix.com
    2012-07-1621:20:58:044 9807c8PT  Server URL = http://<OMITTED>/SimpleAuthWebService/SimpleAuth.asmx
    2012-07-1621:21:57:839 9807c8AgentWARNING: Failed to evaluate Installed rule, updateId = {189A8F50-0C3A-4FDF-8BC2-BC23A3EB11FB}.101, hr = 80242013
    2012-07-1621:22:00:192 9807c8PT+++++++++++  PT: Synchronizing extended update info  +++++++++++
    2012-07-1621:22:00:192 9807c8PT  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://<OMITTED>/ClientWebService/client.asmx
    2012-07-1621:22:01:779 9807c8Agent  * Found 0 updates and 81 categories in search; evaluated appl. rules of 1516 out of 2593 deployed entities
    2012-07-1621:22:01:783 9807c8Agent*********
    2012-07-1621:22:01:783 9807c8Agent**  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2012-07-1621:22:01:783 9807c8Agent*************
    2012-07-1621:22:01:847 98017e4AU>>##  RESUMED  ## AU: Search for updates [CallId = {DEBCEBEE-8338-4CC5-A163-26CE94D7CF19}]
    2012-07-1621:22:01:847 98017e4AU  # 0 updates detected
    2012-07-1621:22:01:848 98017e4AU#########
    2012-07-1621:22:01:848 98017e4AU##  END  ##  AU: Search for updates [CallId = {DEBCEBEE-8338-4CC5-A163-26CE94D7CF19}]
    2012-07-1621:22:01:848 98017e4AU#############
    2012-07-1621:22:01:858 98017e4AUSuccessfully wrote event for AU health state:0
    2012-07-1621:22:01:858 98017e4AUFeatured notifications is disabled.
    2012-07-1621:22:01:859 98017e4AUAU setting next detection timeout to 2012-07-17 22:00:06
    2012-07-1621:22:01:860 98017e4AUSetting AU scheduled install time to 2012-07-17 07:00:00
    2012-07-1621:22:01:862 98017e4AUSuccessfully wrote event for AU health state:0
    2012-07-1621:22:01:865 98017e4AUSuccessfully wrote event for AU health state:0
    2012-07-1621:22:06:781 9807c8ReportREPORT EVENT: {F338340F-3443-4975-B1DB-1C2E88760405}2012-07-16 21:22:01:780-04001147101{00000000-0000-0000-0000-000000000000}00AutomaticUpdatesSuccessSoftware SynchronizationWindows Update Client successfully detected 0 updates.
    2012-07-1621:22:06:782 9807c8ReportREPORT EVENT: {7311B7FE-802F-4C6F-8235-DDDE6D065CB2}2012-07-16 21:22:01:782-04001156101{00000000-0000-0000-0000-000000000000}00AutomaticUpdatesSuccessPre-Deployment CheckReporting client status.
    2012-07-1621:22:06:783 9807c8ReportCWERReporter finishing event handling. (00000000)
    2012-07-1621:28:37:926 9807c8ReportUploading 2 events using cached cookie, reporting URL = http://<OMITTED>/ReportingWebService/ReportingWebService.asmx
    2012-07-1621:28:37:944 9807c8Report

    Reporter successfully uploaded 2 events.

    **********

  • 0 in reply to grandgroove


    This one is updated:

    2012-07-1621:20:52:5129807c8SetupClient version: Core: 7.6.7600.256 Aux: 7.6.7600.256
  • 0 in reply to LGarvin

    That's what I thought, too. However, if I check the machine in Computer Explorer or run a report, the Win7 and 2K8 machines that are definitely 7.6 show the agent as being 7.5.7601.17514. Could it be an error with the data being retrieved from the machines by PM? Am I confusing two values?

  • 0 in reply to grandgroove

    Computer Explorer | Windows Update Settings should reflect the current installed version, but there may be some values that did not get updated in this process by Microsoft. I'll look into these.

    In the Report... that's based on the information inventoried from the WSUS server, which contains the version number reported by the client the last time it reported. Check the All Computers node of the Patch Manager console -- for Last Reported Date and Client Version. If that data is reporting correctly, the reports should reflect correctly after the next WSUS Inventory task. If that data is reporting incorrectly, then do a Refresh Update Server and try again. If it is still incorrect, then report that via the Customer Portal and we'll go from there.

  • 0 in reply to LGarvin

    Unfortunately, it did not do the trick. I submitted a ticket to the portal.

SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 195,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.

SolarWinds Customer Success Center Certification Media Vault Link Accounts
About THWACK Blogs For Government Edit Settings Free Tools & Trials
Legal Documents Terms of Use Privacy California Privacy Rights Security Information
©2024 SolarWinds Worldwide, LLC. All Rights Reserved.