locked
Computers are not showing up in WSUS admin console RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I have just deployed WSUS 3.2 on Server 2012 R2. All my client computers are Server 2012 R2 as well. I configured all the settings via the default domain GPO to point to my WSUS server and when I check the reg settings on any of the clients I see all the settings I configured in the GPO are being pushed down. But when I go to the All Computers in the WSUS console there are no clients showing up. At first I thought it had to do with the port number not being in the Specify Intranet Microsoft update service location all I had was the server name. I then changed it to 'servername:8530' and that change got pushed down but still no clients show up in the Computer's section in the WSUS admin console.

    Is there something I should check or may be missing here?

    Thanks

    Tuesday, January 6, 2015 1:59 PM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote

    Agent * WSUS server: IADWSUS01:8530
    Agent * WSUS status server: IADWSUS01:8530

    VOILA! You have not configured the URL as described in the installation dialogs and in the documentation.

    The correct format of this URL is the format of a *URL*! :-)

    http://iadwsus01:8530

    Later on in that logfile almost surely you will find an error code 0x80072EE5 which is the error code for INVALID_URL

    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, January 7, 2015 4:12 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I have just deployed WSUS 3.2 on Server 2012 R2.

    Not really, but it's a common misconception, and for the moment trivial.
    I configured all the settings via the default domain GPO
    The preferred methodology is to create a NEW GPO, and never to modify the Default Domain GPO, but that's just a point of administrative practice, and probably not relevant to this issue.
    and when I check the reg settings on any of the clients I see all the settings I configured in the GPO are being pushed down.
    Excellent!
    But when I go to the All Computers in the WSUS console there are no clients showing up.
    So, pushing down the settings you configured is one thing. Pushing down the *CORRECT* settings is an entirely different conversation.

    Is there something I should check

    Yep. Check the WindowsUpdate.log on one of your client systems and let's find out what *IS* actually happening. From there we can identify functional steps to take.

    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, January 6, 2015 3:59 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    I have just deployed WSUS 3.2 on Server 2012 R2.

    Not really, but it's a common misconception, and for the moment trivial.
    I configured all the settings via the default domain GPO
    The preferred methodology is to create a NEW GPO, and never to modify the Default Domain GPO, but that's just a point of administrative practice, and probably not relevant to this issue.
    and when I check the reg settings on any of the clients I see all the settings I configured in the GPO are being pushed down.
    Excellent!
    But when I go to the All Computers in the WSUS console there are no clients showing up.
    So, pushing down the settings you configured is one thing. Pushing down the *CORRECT* settings is an entirely different conversation.

    Is there something I should check

    Yep. Check the WindowsUpdate.log on one of your client systems and let's find out what *IS* actually happening. From there we can identify functional steps to take.

    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, January 6, 2015 3:59 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks for the help. Below is the windowsupdate.log file. I stopped the update service renamed the old log file and let it create a new one.

    2015-01-06 13:40:14:038 720 218c Misc ===========  Logging initialized (build: 7.9.9600.17415, tz: -0500)  ===========
    2015-01-06 13:40:14:038 720 218c Misc  = Process: C:\Windows\system32\svchost.exe
    2015-01-06 13:40:14:038 720 218c Misc  = Module: c:\windows\system32\wuaueng.dll
    2015-01-06 13:40:14:038 720 218c Service *************
    2015-01-06 13:40:14:038 720 218c Service ** START **  Service: Service startup
    2015-01-06 13:40:14:038 720 218c Service *********
    2015-01-06 13:40:14:069 720 218c IdleTmr Non-AoAc machine.  Aoac operations will be ignored.
    2015-01-06 13:40:14:069 720 218c Agent  * WU client version 7.9.9600.17415
    2015-01-06 13:40:14:069 720 218c Agent WARNING: SleepStudyTracker: Machine is non-AOAC. Sleep study tracker disabled.
    2015-01-06 13:40:14:069 720 218c Agent  * Base directory: C:\Windows\SoftwareDistribution
    2015-01-06 13:40:14:069 720 218c Agent  * Access type: No proxy
    2015-01-06 13:40:14:069 720 218c Service UpdateNetworkState Ipv6, cNetworkInterfaces = 0.
    2015-01-06 13:40:14:069 720 218c Service UpdateNetworkState Ipv4, cNetworkInterfaces = 2.
    2015-01-06 13:40:14:069 720 218c Agent  * Network state: Connected
    2015-01-06 13:40:14:085 720 218c Service UpdateNetworkState Ipv6, cNetworkInterfaces = 0.
    2015-01-06 13:40:14:085 720 218c Service UpdateNetworkState Ipv4, cNetworkInterfaces = 2.
    2015-01-06 13:40:14:116 720 218c Agent ***********  Agent: Initializing global settings cache  ***********
    2015-01-06 13:40:14:116 720 218c Agent  * Endpoint Provider: 00000000-0000-0000-0000-000000000000
    2015-01-06 13:40:14:116 720 218c Agent  * WSUS server: IADWSUS01:8530
    2015-01-06 13:40:14:116 720 218c Agent  * WSUS status server: IADWSUS01:8530
    2015-01-06 13:40:14:116 720 218c Agent  * Target group: (Unassigned Computers)
    2015-01-06 13:40:14:116 720 218c Agent  * Windows Update access disabled: No
    2015-01-06 13:40:14:116 720 218c Misc WARNING: Network Cost is assumed to be not supported as something failed with trying to get handles to wcmapi.dll
    2015-01-06 13:40:14:116 720 218c WuTask WuTaskManager delay initialize completed successfully..
    2015-01-06 13:40:14:116 720 218c AU    Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2015-01-06 23:16:19, not idle-only, not network-only
    2015-01-06 13:40:14:116 720 218c AU    Timer: 143FB093-8AA1-4DBC-A582-8806F8F4C1F7, Expires 2015-01-07 22:13:54, not idle-only, not network-only
    2015-01-06 13:40:14:116 720 218c AU    Timer: CF1ABEC6-7887-4964-BB93-B2E21B31CEC1, Expires 2015-01-07 15:10:18, not idle-only, not network-only
    2015-01-06 13:40:14:116 720 218c AU    Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2015-01-07 15:10:01, not idle-only, not network-only
    2015-01-06 13:40:14:132 720 218c Report WARNING: CSerializationHelper:: InitSerialize failed : 0x80070002
    2015-01-06 13:40:14:132 720 218c Report CWERReporter::Init succeeded
    2015-01-06 13:40:14:132 720 218c Agent ***********  Agent: Initializing Windows Update Agent  ***********
    2015-01-06 13:40:14:132 720 218c DnldMgr Download manager restoring 0 downloads
    2015-01-06 13:40:14:132 720 218c AU ###########  AU: Initializing Automatic Updates  ###########
    2015-01-06 13:40:14:148 720 218c AU Additional Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} with Approval type {Pre-download notify} added to AU services list
    2015-01-06 13:40:14:148 720 218c AU AIR Mode is disabled
    2015-01-06 13:40:14:148 720 218c AU  # Policy Driven Provider: IADWSUS01:8530
    2015-01-06 13:40:14:148 720 218c AU  # Detection frequency: 22
    2015-01-06 13:40:14:148 720 218c AU  # Approval type: Pre-install notify (Policy)
    2015-01-06 13:40:14:148 720 218c AU  # Auto-install minor updates: No (User preference)
    2015-01-06 13:40:14:148 720 218c AU  # ServiceTypeDefault: Service 117CAB2D-82B1-4B5A-A08C-4D62DBEE7782 Approval type: (Pre-download notify)
    2015-01-06 13:40:14:148 720 218c AU  # Will interact with non-admins (Non-admins are elevated (User preference))
    2015-01-06 13:40:14:148 720 218c Misc WARNING:     IsSessionRemote: WinStationQueryInformationW(WTSIsRemoteSession) failed for session 1, GetLastError=2250
    2015-01-06 13:40:14:148 720 218c Misc WARNING:     IsSessionRemote: WinStationQueryInformationW(WTSIsRemoteSession) failed for session 3, GetLastError=2250
    2015-01-06 13:40:14:148 720 218c AU WARNING: Failed to get Wu Exemption info from NLM, assuming not exempt, error = 0x80240037
    2015-01-06 13:40:14:148 720 218c AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
    2015-01-06 13:40:14:163 720 218c AU AU finished delayed initialization
    2015-01-06 13:40:14:163 720 218c AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
    2015-01-06 13:40:14:163 720 218c AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
    2015-01-06 13:40:14:163 720 218c AU Adding timer: 
    2015-01-06 13:40:14:163 720 218c AU    Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2015-01-06 23:16:19, not idle-only, not network-only
    2015-01-06 13:40:14:163 720 1b9c DnldMgr Asking handlers to reconcile their sandboxes

    Tuesday, January 6, 2015 6:43 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Here is a snippet of the log where it finds my WSUS server then gives a warning:

    2015-01-06 13:40:14:116 720 218c Agent  * Endpoint Provider: 00000000-0000-0000-0000-000000000000
    2015-01-06 13:40:14:116 720 218c Agent  * WSUS server: IADWSUS01:8530
    2015-01-06 13:40:14:116 720 218c Agent  * WSUS status server: IADWSUS01:8530
    2015-01-06 13:40:14:116 720 218c Agent  * Target group: (Unassigned Computers)
    2015-01-06 13:40:14:116 720 218c Agent  * Windows Update access disabled: No
    2015-01-06 13:40:14:116 720 218c Misc WARNING: Network Cost is assumed to be not supported as something failed with trying to get handles to wcmapi.dll
    2015-01-06 13:40:14:116 720 218c WuTask WuTaskManager delay initialize completed successfully..

    Tuesday, January 6, 2015 6:45 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Agent * WSUS server: IADWSUS01:8530
    Agent * WSUS status server: IADWSUS01:8530

    VOILA! You have not configured the URL as described in the installation dialogs and in the documentation.

    The correct format of this URL is the format of a *URL*! :-)

    http://iadwsus01:8530

    Later on in that logfile almost surely you will find an error code 0x80072EE5 which is the error code for INVALID_URL

    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, January 7, 2015 4:12 AM