locked
Windows Server 2012 R2 dont report to WSUS RRS feed

  • Question

  • Hi,

    We have WSUS 3.2 running on Windows Server 2008 R2.

    All servers are fine, but we have noe implemented two Windows Server 2012 R2, but they dont report to the WSUS server. I can see them in the list, but there are 19 days since last report. If i try the command link http://hostname/iuident.cab it gives me a file to download. I can ping the servers, and there is no local firewall enabled.

    Is there some known issues with reporting from Windows Server 2012 R2 to a Wsus running on Windows Server 2008 R2 ?


    /Regards Andreas

    Tuesday, October 7, 2014 1:21 PM

All replies

  • Is there some known issues with reporting from Windows Server 2012 R2 to a Wsus running on Windows Server 2008 R2 ?

    Have you applied the required patch from August 2012 to your WSUS Server? (See KB2734608)

    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Tuesday, October 7, 2014 7:45 PM
  • Hi,

    I tried to add the patch, but same issue. I can see from the log file te server is in the group Target group: (Unassigned Computers) but it should not be there since i have moved it to another group. I have tried the wuauclt /resetauthorization and /report now but doesnt seem to work

    The following is from the windows server 2012 R2 windowsupdate.log file:

    2014-10-07 23:16:06:741  960 33c Misc ===========  Logging initialized (build: 7.9.9600.16422, tz: +0200)  ===========
    2014-10-07 23:16:06:741  960 33c Misc   = Process: C:\Windows\system32\svchost.exe
    2014-10-07 23:16:06:741  960 33c Misc   = Module: c:\windows\system32\wuaueng.dll
    2014-10-07 23:16:06:741  960 33c Service *************
    2014-10-07 23:16:06:741  960 33c Service ** START **  Service: Service startup
    2014-10-07 23:16:06:741  960 33c Service *********
    2014-10-07 23:16:06:753  960 33c Agent   * WU client version 7.9.9600.16422
    2014-10-07 23:16:06:755  960 33c Agent   * Base directory: C:\Windows\SoftwareDistribution
    2014-10-07 23:16:06:755  960 33c Agent   * Access type: No proxy
    2014-10-07 23:16:06:755  960 33c Service UpdateNetworkState Ipv6, cNetworkInterfaces = 0.
    2014-10-07 23:16:06:755  960 33c Service UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
    2014-10-07 23:16:06:755  960 33c Agent   * Network state: Connected
    2014-10-07 23:16:06:760  960 33c Service UpdateNetworkState Ipv6, cNetworkInterfaces = 0.
    2014-10-07 23:16:06:760  960 33c Service UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
    2014-10-07 23:16:06:778  960 33c Agent ***********  Agent: Initializing global settings cache  ***********
    2014-10-07 23:16:06:778  960 33c Agent   * Endpoint Provider: 00000000-0000-0000-0000-000000000000
    2014-10-07 23:16:06:778  960 33c Agent   * WSUS server: http://WSUS-SERVER
    2014-10-07 23:16:06:778  960 33c Agent   * WSUS status server: http://WSUS-SERVER
    2014-10-07 23:16:06:778  960 33c Agent   * Target group: (Unassigned Computers)
    2014-10-07 23:16:06:778  960 33c Agent   * Windows Update access disabled: No
    2014-10-07 23:16:06:779  960 33c Misc WARNING: Network Cost is assumed to be not supported as something failed with trying to get handles to wcmapi.dll
    2014-10-07 23:16:06:786  960 33c WuTask WuTaskManager delay initialize completed successfully..
    2014-10-07 23:16:06:790  960 33c Report WARNING: CSerializationHelper:: InitSerialize failed : 0x80070002
    2014-10-07 23:16:06:791  960 33c Report CWERReporter::Init succeeded
    2014-10-07 23:16:06:791  960 33c Agent ***********  Agent: Initializing Windows Update Agent  ***********
    2014-10-07 23:16:06:791  960 33c DnldMgr Download manager restoring 0 downloads
    2014-10-07 23:16:06:791  960 33c AU ###########  AU: Initializing Automatic Updates  ###########
    2014-10-07 23:16:06:792  960 33c AU AIR Mode is disabled
    2014-10-07 23:16:06:792  960 33c AU   # Policy Driven Provider: http://WSUS-SERVER
    2014-10-07 23:16:06:792  960 33c AU   # Detection frequency: 22
    2014-10-07 23:16:06:792  960 33c AU   # Approval type: Pre-install notify (Policy)
    2014-10-07 23:16:06:792  960 33c AU   # Auto-install minor updates: Yes (Policy)
    2014-10-07 23:16:06:792  960 33c AU   # Will interact with non-admins (Non-admins are elevated (User preference))
    2014-10-07 23:16:06:793  960 33c AU WARNING: Failed to get Wu Exemption info from NLM, assuming not exempt, error = 0x80240037
    2014-10-07 23:16:06:793  960 33c AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
    2014-10-07 23:16:06:798  960 33c AU AU finished delayed initialization
    2014-10-07 23:16:06:798  960 33c AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
    2014-10-07 23:16:06:799  960 33c AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
    2014-10-07 23:16:06:805  960 17ac DnldMgr Asking handlers to reconcile their sandboxes
    2014-10-07 23:16:46:831  960 33c Misc WARNING:     IsSessionRemote: WinStationQueryInformationW(WTSIsRemoteSession) failed for session 1, GetLastError=2250


    /Regards Andreas


    • Edited by Andreas2012 Tuesday, October 7, 2014 9:36 PM more info
    Tuesday, October 7, 2014 9:34 PM
  • I tried to add the patch, but same issue.

    This doesn't really answer the question. Did you *successfully* install the required update or not?
    I can see from the log file te server is in the group Target group: (Unassigned Computers) but it should not be there
    You're misinterpreting the meaning of this log entry. If you're using Server-Side Targeting, the group name will not be logged in the WindowsUpdate.log.

    The following is from the windows server 2012 R2 windowsupdate.log file:

    This logfile is not really helpful as it covers less than 50 milliseconds of activity.

    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Wednesday, October 8, 2014 2:09 AM