locked
2012 WSUS not showing all servers RRS feed

  • Question

  • Hello,

    I have a few targeted server groups in on our WSUS server.  However not all servers are showing for example:

    Production (70%)

    Development (80%)

    Domain Controllers (3/4 servers)

    Skype Servers (none)

    If I go onto the servers that are missing from WSUS and into their GPO and check:

    HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate\AU

    All the settings look ok, it will show the correct targeted from etc.

    I can have 2 servers on the same GPO and only 1 will be on WSUS.

    The Windowsupdate log file will list the correct WSUS server too.  This is one that was there the other day and now missing:

    2016-12-09 10:30:10:117 892 8c Agent  * Endpoint Provider: 00000000-0000-0000-0000-000000000000
    2016-12-09 10:30:10:117 892 8c Agent  * WSUS server: http://svr-wsus:8530
    2016-12-09 10:30:10:117 892 8c Agent  * WSUS status server: http://svr-wsus:8530
    2016-12-09 10:30:10:117 892 8c Agent  * Target group: Domain Controllers
    2016-12-09 10:30:10:117 892 8c Agent  * Windows Update access disabled: No
    2016-12-09 10:30:10:117 892 8c Misc WARNING: Network Cost is assumed to be not supported as something failed with trying to get handles to wcmapi.dll
    2016-12-09 10:30:10:117 892 8c WuTask WuTaskManager delay initialize completed successfully..
    2016-12-09 10:30:10:117 892 8c AU    Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2016-12-09 13:16:33, not idle-only, not network-only
    2016-12-09 10:30:10:117 892 8c AU    Timer: CF1ABEC6-7887-4964-BB93-B2E21B31CEC1, Expires 2016-12-09 13:12:31, not idle-only, not network-only
    2016-12-09 10:30:10:117 892 8c AU    Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2016-12-09 13:12:29, not idle-only, not network-only
    2016-12-09 10:30:10:132 892 8c Report WARNING: CSerializationHelper:: InitSerialize failed : 0x80070002
    2016-12-09 10:30:10:132 892 8c Report CWERReporter::Init succeeded
    2016-12-09 10:30:10:132 892 8c Agent ***********  Agent: Initializing Windows Update Agent  ***********
    2016-12-09 10:30:10:132 892 8c DnldMgr Download manager restoring 0 downloads
    2016-12-09 10:30:10:132 892 8c AU ###########  AU: Initializing Automatic Updates  ###########
    2016-12-09 10:30:10:132 892 8c AU AIR Mode is disabled
    2016-12-09 10:30:10:132 892 8c AU  # Policy Driven Provider: http://svr-wsus:8530
    2016-12-09 10:30:10:132 892 8c AU  # Detection frequency: 4
    2016-12-09 10:30:10:132 892 8c AU  # Target group: Domain Controllers
    2016-12-09 10:30:10:132 892 8c AU  # Approval type: Pre-download notify (Policy)
    2016-12-09 10:30:10:132 892 8c Misc WARNING:     IsSessionRemote: WinStationQueryInformationW(WTSIsRemoteSession) failed for session 2, GetLastError=2250
    2016-12-09 10:30:10:179 892 8c AU WARNING: Failed to get Wu Exemption info from NLM, assuming not exempt, error = 0x80240037
    2016-12-09 10:30:10:179 892 8c AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
    2016-12-09 10:30:10:179 892 8c AU AU finished delayed initialization
    2016-12-09 10:30:10:179 892 8c AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
    2016-12-09 10:30:10:179 892 8c AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
    2016-12-09 10:30:10:195 892 8c AU Adding timer: 
    2016-12-09 10:30:10:195 892 8c AU    Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2016-12-09 13:16:33, not idle-only, not network-only
    2016-12-09 10:30:10:195 892 1690 DnldMgr Asking handlers to reconcile their sandboxes
    2016-12-09 10:40:10:116 892 1884 AU Earliest future timer found: 
    2016-12-09 10:40:10:116 892 1884 AU    Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2016-12-09 13:12:29, not idle-only, not network-only
    2016-12-09 10:40:11:116 892 8c AU ###########  AU: Uninitializing Automatic Updates  ###########
    2016-12-09 10:40:11:132 892 8c WuTask Uninit WU Task Manager
    2016-12-09 10:40:11:147 892 8c AU Earliest future timer found: 
    2016-12-09 10:40:11:147 892 8c AU    Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2016-12-09 13:12:29, not idle-only, not network-only
    2016-12-09 10:40:11:163 892 8c AU Earliest future timer found: 
    2016-12-09 10:40:11:163 892 8c AU    Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2016-12-09 13:12:29, not idle-only, not network-only
    2016-12-09 10:40:11:225 892 8c Service *********
    2016-12-09 10:40:11:225 892 8c Service **  END  **  Service: Service exit [Exit code = 0x240001]
    2016-12-09 10:40:11:225 892 8c Service *************

    Friday, December 9, 2016 12:34 PM

All replies

  • >> This is one that was there the other day and now missing

    See:

    Resolving the duplicate SUSClientID issue, or “Why don’t all my clients show up in the WSUS console?”


    Rolf Lidvall, Swedish Radio (Ltd)

    Friday, December 9, 2016 2:45 PM
  • Hi TB,

    As Rolf has mentioned, the issue may due to duplicated SUSClientID, please reset SUSClientID:

    Reset SusClientId:
    1). In cmd, net stop wuauserv

    2). Delete the value in registry key " SusClientId " and "SusClientIDValidation" locates in:

    HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate

    3). In cmd, net start wuauserv
         wuauclt.exe /resetauthorization /detectnow

    Welcome to feed back the result. If the method works, please mark useful reply as answer.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, December 12, 2016 2:28 AM
  • Testing now on a server that has gone missing, how long should it take to appear do you think.
    Monday, December 12, 2016 9:13 AM
  • Hi TB,

    Normally, it will within 22 hours by default.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, December 12, 2016 9:15 AM
  • ok thanks.

    I see a few Windows 10 laptops appear to show they have 'Failed counts' of up to 70 times.  I use to be able to remote to Windows 7 and below computer's C:\windows\windowsupdate.txt but this is now gone.

    What is the best way to remote to a Windows 10 laptop through the network to check this log file now? 

    Thanks

    Monday, December 12, 2016 4:49 PM
  • Hi TB303,

    We need to use powershell command Get-WindowsUpdateLog to get windows 10 update log:

    https://support.microsoft.com/en-sg/kb/3036646

    To remote the other computers, we need to enable the win10 is allowed to logon remotely, then, we may use mstsc, and enter the IP address or FQDN to remote.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, December 13, 2016 6:21 AM
  • Hi,

    Have you got any progress with your issue? Welcome to feed back.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, December 19, 2016 2:51 AM