locked
Clients are not updating status in WSUS RRS feed

  • General discussion

  • I have new WSUS server and none of my clients are updating their status.  I have searched through many other discussions on the topic but cannot solve my issue.  

    My server is:

    WSUS 3.0 running on 2008 R2 Datacenter

    My clients are Windows 7 and were previously getting updates from a different server.  The clients have been configured for my the correct server and report in the WindowsUpdate.log file.  My registry settings look correct.

    The WUServer and WUStatusServer have the correct url.  The Url is reachable from the client.

    Here is a portion of the WindowsUpdate.log file from one of the clients.

    2017-08-22 09:02:11:814 1020 1390 Misc ===========  Logging initialized (build: 7.6.7601.23806, tz: -0400)  ===========
    2017-08-22 09:02:11:814 1020 1390 Misc  = Process: C:\Windows\system32\svchost.exe
    2017-08-22 09:02:11:814 1020 1390 Misc  = Module: c:\windows\system32\wuaueng.dll
    2017-08-22 09:02:11:814 1020 1390 Service *************
    2017-08-22 09:02:11:814 1020 1390 Service ** START **  Service: Service startup
    2017-08-22 09:02:11:814 1020 1390 Service *********
    2017-08-22 09:02:11:815 1020 1390 Agent  * WU client version 7.6.7601.23806
    2017-08-22 09:02:11:815 1020 1390 Agent  * Base directory: C:\Windows\SoftwareDistribution
    2017-08-22 09:02:11:815 1020 1390 Agent  * Access type: No proxy
    2017-08-22 09:02:11:815 1020 1390 Agent  * Network state: Connected
    2017-08-22 09:02:56:845 1020 1390 Report CWERReporter::Init succeeded
    2017-08-22 09:02:56:845 1020 1390 Agent ***********  Agent: Initializing Windows Update Agent  ***********
    2017-08-22 09:02:56:846 1020 1390 Agent  * Prerequisite roots succeeded.
    2017-08-22 09:02:56:846 1020 1390 Agent ***********  Agent: Initializing global settings cache  ***********
    2017-08-22 09:02:56:846 1020 1390 Agent  * WSUS server: http://OSW-CASHAPP03.novelis.biz:8530
    2017-08-22 09:02:56:846 1020 1390 Agent  * WSUS status server: http://OSW-CASHAPP03.novelis.biz:8530
    2017-08-22 09:02:56:846 1020 1390 Agent  * Target group: (Unassigned Computers)
    2017-08-22 09:02:56:846 1020 1390 Agent  * Windows Update access disabled: No
    2017-08-22 09:02:56:846 1020 1390 DnldMgr Download manager restoring 0 downloads
    2017-08-22 09:02:56:847 1020 1390 AU ###########  AU: Initializing Automatic Updates  ###########
    2017-08-22 09:02:56:847 1020 1390 AU  # WSUS server: http://OSW-CASHAPP03.novelis.biz:8530
    2017-08-22 09:02:56:847 1020 1390 AU  # Detection frequency: 22
    2017-08-22 09:02:56:847 1020 1390 AU  # Approval type: Pre-install notify (Policy)
    2017-08-22 09:02:56:847 1020 1390 AU  # Auto-install minor updates: No (Policy)
    2017-08-22 09:02:56:847 1020 1390 AU  # Power management is turned off through policy
    2017-08-22 09:02:56:921 1020 1390 Report ***********  Report: Initializing static reporting data  ***********
    2017-08-22 09:02:56:921 1020 1390 Report  * OS Version = 6.1.7601.1.0.65792
    2017-08-22 09:02:56:921 1020 1390 Report  * OS Product Type = 0x00000030
    2017-08-22 09:02:56:928 1020 1390 Report  * Computer Brand = Dell Inc.
    2017-08-22 09:02:56:928 1020 1390 Report  * Computer Model = Precision WorkStation T3500  
    2017-08-22 09:02:56:929 1020 1390 Report  * Bios Revision = A15
    2017-08-22 09:02:56:929 1020 1390 Report  * Bios Name = Phoenix ROM BIOS PLUS Version 1.10 A15
    2017-08-22 09:02:56:929 1020 1390 Report  * Bios Release Date = 2012-03-28T00:00:00
    2017-08-22 09:02:56:929 1020 1390 Report  * Locale ID = 1033
    2017-08-22 09:02:57:446 1020 1390 AU Successfully wrote event for AU health state:1
    2017-08-22 09:02:57:446 1020 1390 AU Initializing featured updates
    2017-08-22 09:02:57:446 1020 1390 AU Found 0 cached featured updates
    2017-08-22 09:02:57:446 1020 1390 AU Successfully wrote event for AU health state:1
    2017-08-22 09:02:57:447 1020 1390 AU Successfully wrote event for AU health state:1
    2017-08-22 09:02:57:447 1020 1390 AU AU finished delayed initialization

    Finally, this client was listed under All Computers.  I deleted it, hoping to force something to happen. t has reappeared in my 'All Computers' listing but is still not reporting its status.

    Thanks in advance for any help provided.


    Tuesday, August 22, 2017 2:12 PM

All replies

  • My script fixes issues like this:

    Have a peek at my Adamj Clean-WSUS script. It is the last WSUS Script you will ever need!

    http://community.spiceworks.com/scripts/show/2998-adamj-clean-wsus

    What it does:

    1. Add WSUS Index Optimization to the database to increase the speed of many database operations in WSUS by approximately 1000-1500 times faster.
    2. Remove all Drivers from the WSUS Database (Default; Optional).
    3. Shrink your WSUSContent folder's size by declining multiple types of updates including by default any superseded updates, preview updates, expired updates, Itanium updates, and beta updates. Optional extras: Language Packs, IE7, IE8, IE9, IE10, Embedded, NonEnglishUpdates, ComputerUpdates32bit, WinXP.
    4. Remove declined updates from the WSUS Database.
    5. Clean out all the synchronization logs that have built up over time (configurable, with the default keeping the last 14 days of logs).
    6. Compress Update Revisions.
    7. Remove Obsolete Updates.
    8. Computer Object Cleanup (configurable, with the default of deleting computer objects that have not synced within 30 days).
    9. Application Pool Memory Configuration to display the current private memory limit and easily set it to any configurable amount including 0 for unlimited. This is a manual execution only.
    10. Checks to see if you have a dirty database, and if you do, fixes it. This is primarily for Server 2012 WSUS, and is a manual execution only.
    11. Run the Recommended SQL database Maintenance script on the actual SQL database.
    12. Run the Server Cleanup Wizard.

    It will email the report out to you or save it to a file, or both.

    Although the script is lengthy, it has been made to be super easy to setup and use so don't over think it. There are some prerequisites and instructions at the top of the script. After installing the prerequisites and configuring the variables for your environment (email settings only if you are accepting all the defaults), simply run:

    .\Clean-WSUS.ps1 -FirstRun

    If you wish to view or increase the Application Pool Memory Configuration, or run the Dirty Database Check, you must run it with the required switch. See Get-Help .\Clean-WSUS.ps1 -Examples

    If you're having trouble, there's also a -HelpMe option that will create a log so you can send it to me for support.

    If after running my script the systems do not start to report back in, it may still be required to run the following on the affected clients in an Administrative command prompt.

    net stop bits
    net stop wuauserv
    reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v AccountDomainSid /f
    reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v PingID /f
    reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientId /f
    reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientIDValidation /f
    rd /s /q "C:\WINDOWS\SoftwareDistribution"
    net start bits
    net start wuauserv
    wuauclt /resetauthorization /detectnow


    Adam Marshall, MCSE: Security
    http://www.adamj.org

    Saturday, September 2, 2017 3:42 AM