locked
WSUS clients won't connect properly to a newly reinstalled WSUS Server RRS feed

  • Question

  • Hello

    I'm having troubles with the clients of a new WSUS server reinstalled completely from scratch. The server is a Windows 2012 R2 Standard witch the proper role installed and using the Windows Internal Database.

    A GPO is in place for the whole domain for the client machines to retrieve the updates from the server. No machines reported their status and no machine downloaded updates from the server. I know the issue is with the server by I'm not capable of realizing what the problem is.

    Here's a fragment os the windowsupdate.log from a client machine running Windows Server 2008 R2:

    2016-06-27 09:29:34:031 904 6b0 Service *************
    2016-06-27 09:29:34:031 904 6b0 Service ** START **  Service: Service startup
    2016-06-27 09:29:34:031 904 6b0 Service *********
    2016-06-27 09:29:34:035 904 6b0 Agent  * WU client version 7.6.7601.19161
    2016-06-27 09:29:34:035 904 6b0 Agent  * Base directory: C:\Windows\SoftwareDistribution
    2016-06-27 09:29:34:035 904 6b0 Agent  * Access type: No proxy
    2016-06-27 09:29:34:036 904 6b0 Agent  * Network state: Connected
    2016-06-27 09:30:19:084 904 6b0 Report CWERReporter::Init succeeded
    2016-06-27 09:30:19:084 904 6b0 Agent ***********  Agent: Initializing Windows Update Agent  ***********
    2016-06-27 09:30:19:085 904 6b0 Agent  * Prerequisite roots succeeded.
    2016-06-27 09:30:19:085 904 6b0 Agent ***********  Agent: Initializing global settings cache  ***********
    2016-06-27 09:30:19:085 904 6b0 Agent  * WSUS server: http://sm-wsus:8530
    2016-06-27 09:30:19:085 904 6b0 Agent  * WSUS status server: http://sm-wsus:8530
    2016-06-27 09:30:19:086 904 6b0 Agent  * Target group: (Unassigned Computers)
    2016-06-27 09:30:19:086 904 6b0 Agent  * Windows Update access disabled: No
    2016-06-27 09:30:19:086 904 6b0 DnldMgr Download manager restoring 0 downloads
    2016-06-27 09:30:19:087 904 6b0 AU ###########  AU: Initializing Automatic Updates  ###########
    2016-06-27 09:30:19:088 904 6b0 AU  # WSUS server: http://sm-wsus:8530
    2016-06-27 09:30:19:088 904 6b0 AU  # Detection frequency: 22
    2016-06-27 09:30:19:088 904 6b0 AU  # Approval type: Pre-install notify (Policy)
    2016-06-27 09:30:19:088 904 6b0 AU  # Auto-install minor updates: Yes (Policy)
    2016-06-27 09:30:19:222 904 6b0 Agent Created new random SusClientId 7a9ed206-d811-4f41-b1a0-828b8d2e60a7. Old Id: none.
    2016-06-27 09:30:19:222 904 6b0 Report ***********  Report: Initializing static reporting data  ***********
    2016-06-27 09:30:19:222 904 6b0 Report  * OS Version = 6.1.7601.1.0.196880
    2016-06-27 09:30:19:222 904 6b0 Report  * OS Product Type = 0x00000007
    2016-06-27 09:30:19:239 904 6b0 Report  * Computer Brand = VMware, Inc.
    2016-06-27 09:30:19:239 904 6b0 Report  * Computer Model = VMware Virtual Platform
    2016-06-27 09:30:19:244 904 6b0 Report  * Bios Revision = 6.00
    2016-06-27 09:30:19:244 904 6b0 Report  * Bios Name = PhoenixBIOS 4.0 Release 6.0     
    2016-06-27 09:30:19:244 904 6b0 Report  * Bios Release Date = 2014-04-14T00:00:00
    2016-06-27 09:30:19:244 904 6b0 Report  * Locale ID = 3082
    2016-06-27 09:30:20:128 904 6b0 AU Successfully wrote event for AU health state:1
    2016-06-27 09:30:20:128 904 6b0 AU Initializing featured updates
    2016-06-27 09:30:20:128 904 6b0 AU Found 0 cached featured updates
    2016-06-27 09:30:20:129 904 6b0 AU Successfully wrote event for AU health state:1
    2016-06-27 09:30:20:130 904 6b0 AU Successfully wrote event for AU health state:1
    2016-06-27 09:30:20:130 904 6b0 AU AU finished delayed initialization
    2016-06-27 09:30:22:714 904 12e8 PT WARNING: GetConfig failure, error = 0x80244008, soap client error = 8, soap error code = 0, HTTP status code = 200
    2016-06-27 09:30:22:714 904 12e8 PT WARNING: PTError: 0x80244008
    2016-06-27 09:30:22:714 904 12e8 PT WARNING: GetConfig_WithRecovery failed: 0x80244008
    2016-06-27 09:30:22:714 904 12e8 PT WARNING: RefreshConfig failed: 0x80244008
    2016-06-27 09:30:22:714 904 12e8 PT WARNING: RefreshPTState failed: 0x80244008
    2016-06-27 09:30:22:714 904 12e8 PT WARNING: PTError: 0x80244008
    2016-06-27 09:30:22:714 904 12e8 Report WARNING: Reporter failed to upload events with hr = 80244008.
    2016-06-27 09:30:22:722 904 12e8 PT WARNING: GetConfig failure, error = 0x80244008, soap client error = 8, soap error code = 0, HTTP status code = 200
    2016-06-27 09:30:22:722 904 12e8 PT WARNING: PTError: 0x80244008
    2016-06-27 09:30:22:722 904 12e8 PT WARNING: GetConfig_WithRecovery failed: 0x80244008
    2016-06-27 09:30:22:722 904 12e8 PT WARNING: RefreshConfig failed: 0x80244008
    2016-06-27 09:30:22:722 904 12e8 PT WARNING: RefreshPTState failed: 0x80244008
    2016-06-27 09:30:22:722 904 12e8 PT WARNING: PTError: 0x80244008
    2016-06-27 09:30:22:722 904 12e8 Report WARNING: Reporter failed to upload events with hr = 80244008.

    I already tried stopping wuauserv, deleting Windowsupdate.log an d SoftwareDistribution folder and restarting wuauserv. Nothing seems to work.

    Any help would be appreciated. Thank you very much.

    Monday, June 27, 2016 1:03 PM

Answers

  • Hi Guillermo Rontana,

    >No machines reported their status and no machine downloaded updates from the server.

    Could the clients show up in the WSUS console? Or clients show up in WSUS server, while the status shows as "Not reported yet".

    If the clients can not even show up in the WSUS console, then reset SUSClientID on clients:

    1). In cmd, enter net stop wuauserv;

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

    HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate

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

    After resetting SUSClientID, also reset windows update components:

    https://support.microsoft.com/en-us/kb/971058

    If clients can show up but not report, you only need to reset windows update components.

    After resetting, we'd better wait for a period of time for clients to report to WSUS server, you may also check the windows update log after doing the above things.

    Besides, is the WSUS server non-domain joined, also ensure the WSUS clients can resolve WSUS name "sm-wsus", in order to avoid DNS resolution issue, you may use the WSUS server's IP address in the URL instead.

    Best Regards,

    Anne


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

    Tuesday, June 28, 2016 7:51 AM

All replies

  • Hello Guillermo Fontana,

    the error code "0x80244008" means "Same as SOAPCLIENT_PARSEFAULT_ERROR - SOAP client failed to parse a SOAP fault."
    So your Windows Update agent seems to get an answer but cannot understand it.

    From the logfile you posted one can see that the Windows Update Agent tries to connect to "http://sm-wsus:8530".

    Is your WSUS configured to accept HTTP-requests on port 8530 or is your WSUS Server expecting HTTPS or traffic to another port?

    Try to connect to "http://sm-wsus:8530/ClientWebService/Client.asmx?singleWsdl" from a browser of one of the affected clients.
    If your WSUS Server is listening, it should return the WSDL of the WSUS client webservice.
    Otherwise you might get a helpful error message...


    Regards,
    PIfM

    Monday, June 27, 2016 4:00 PM
  • Hi Guillermo Rontana,

    >No machines reported their status and no machine downloaded updates from the server.

    Could the clients show up in the WSUS console? Or clients show up in WSUS server, while the status shows as "Not reported yet".

    If the clients can not even show up in the WSUS console, then reset SUSClientID on clients:

    1). In cmd, enter net stop wuauserv;

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

    HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate

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

    After resetting SUSClientID, also reset windows update components:

    https://support.microsoft.com/en-us/kb/971058

    If clients can show up but not report, you only need to reset windows update components.

    After resetting, we'd better wait for a period of time for clients to report to WSUS server, you may also check the windows update log after doing the above things.

    Besides, is the WSUS server non-domain joined, also ensure the WSUS clients can resolve WSUS name "sm-wsus", in order to avoid DNS resolution issue, you may use the WSUS server's IP address in the URL instead.

    Best Regards,

    Anne


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

    Tuesday, June 28, 2016 7:51 AM