locked
clients don't connect to wsus RRS feed

  • Question

  • Hi everybody,

    Got some trouble setting up via GPO a WSUS deployment. Clients (2 devices) don't connect to WSUS server.

    Windows 2008 R2 server with WSUS 3.0 SP2 and clients running windows 7 pro sp 1.

    Everything seems correct on the server side, but both clients report the same kind of error when running WSUS client diagnostic tool:

    WSUS Client Diagnostics Tool

    Checking Machine State
            Checking for admin rights to run tool . . . . . . . . . PASS
            Automatic Updates Service is running. . . . . . . . . . PASS
            Background Intelligent Transfer Service is running. . . PASS

    GetFileVersion(szEngineDir,&susVersion) failed with hr=0x80070002

    I try resetting the clients and installing standalone version of windows update client, but the issue perists:

    Those are the last lines on one of the clients for the windows update log:

    2016-01-31 20:22:03:472 1108 1634 AU ###########  AU: Initializing Automatic Updates  ###########
    2016-01-31 20:22:03:472 1108 1634 AU   # AU disabled through User preference
    2016-01-31 20:22:03:472 1108 1634 AU   # Will interact with non-admins (Non-admins are elevated (User preference))
    2016-01-31 20:22:03:472 1108 1634 AU Initializing featured updates
    2016-01-31 20:22:03:472 1108 1634 AU Found 0 cached featured updates
    2016-01-31 20:22:03:472 1108 1634 AU Successfully wrote event for AU health state:0
    2016-01-31 20:22:03:472 1108 1634 AU Successfully wrote event for AU health state:0
    2016-01-31 20:22:03:472 1108 1634 AU AU finished delayed initialization
    2016-01-31 20:22:07:544 1108 9dc Report CWERReporter finishing event handling. (00000000)

    Can someone give me some advice please?

    Thanks.

    Regards

    Sunday, January 31, 2016 7:32 PM

Answers

  • Am 31.01.2016 schrieb Eduard Vila:

    Got some trouble setting up via GPO a WSUS deployment. Clients (2 devices) don't connect to WSUS server.

    Windows 2008 R2 server with WSUS 3.0 SP2 and clients running windows 7 pro sp 1.

    Pls check first the Build from your WSUS. Here you see where you find
    the Build Number: http://www.wsus.de/images/wsus-version.png
    If your WSUS is not Build .274, install the updates for coming up to
    Build .274:

    WSUS 3.0 (SP2):     Build 3.2.7600.226
    WSUS 3.0 (SP2) + KB2720211:     Build 3.2.7600.251
    WSUS 3.0 (SP2) + KB2734608:     Build 3.2.7600.256
    WSUS 3.0 (SP2) + KB2828185:     Build 3.2.7600.262
    WSUS 3.0 (SP2) + KB2938066:     Build 3.2.7600.274

    After this, restart the whole Server und reconnect after your Clients.

    Winfried


    WSUS Package Publisher: http://wsuspackagepublisher.codeplex.com/
    http://technet.microsoft.com/en-us/windowsserver/bb332157.aspx
    http://www.wsuswiki.com/Home

    • Marked as answer by Eduard Vila Thursday, February 4, 2016 3:48 AM
    Monday, February 1, 2016 5:52 AM
  • Also,

    I run this command:wuauclt /resetauthorization /detectnow

    And here 're the logs of windows update:

    2016-01-31 21:24:31:303 1108 11c4 AU ## START ##  AU: Search for updates
    2016-01-31 21:24:31:303 1108 11c4 AU #########
    2016-01-31 21:24:31:303 1108 11c4 AU <<## SUBMITTED ## AU: Search for updates [CallId = {DED7A929-30C6-413B-A592-CB9477DB7423}]
    2016-01-31 21:24:31:303 1108 1688 Agent *************
    2016-01-31 21:24:31:303 1108 1688 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2016-01-31 21:24:31:303 1108 1688 Agent *********
    2016-01-31 21:24:31:303 1108 1688 Agent   * Online = Yes; Ignore download priority = No
    2016-01-31 21:24:31:303 1108 1688 Agent   * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
    2016-01-31 21:24:31:303 1108 1688 Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2016-01-31 21:24:31:303 1108 1688 Agent   * Search Scope = {Machine}
    2016-01-31 21:24:31:313 1108 1688 Setup Checking for agent SelfUpdate
    2016-01-31 21:24:31:313 1108 1688 Setup Client version: Core: 7.6.7600.320  Aux: 7.6.7600.320
    2016-01-31 21:24:33:613 1108 1688 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
    2016-01-31 21:24:33:623 1108 1688 Misc  Microsoft signed: NA
    2016-01-31 21:24:33:623 1108 1688 Misc WARNING: Cab does not contain correct inner CAB file.
    2016-01-31 21:24:33:623 1108 1688 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
    2016-01-31 21:24:33:623 1108 1688 Misc  Microsoft signed: NA
    2016-01-31 21:24:33:623 1108 1688 Setup Wuident for the managed service is valid but not quorum-signed. Skipping selfupdate.
    2016-01-31 21:24:33:623 1108 1688 Setup Skipping SelfUpdate check based on the /SKIP directive in wuident
    2016-01-31 21:24:33:623 1108 1688 Setup SelfUpdate check completed.  SelfUpdate is NOT required.
    2016-01-31 21:24:35:433 1108 1688 PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2016-01-31 21:24:35:433 1108 1688 PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://172.16.0.1/ClientWebService/client.asmx
    2016-01-31 21:24:35:453 1108 1688 PT WARNING: Cached cookie has expired or new PID is available
    2016-01-31 21:24:35:453 1108 1688 PT Initializing simple targeting cookie, clientId = a73b8550-4bab-4a61-bef6-1ca294bcfc5b, target group = , DNS name = laptop01.morgan.net
    2016-01-31 21:24:35:453 1108 1688 PT   Server URL = http://172.16.0.1/SimpleAuthWebService/SimpleAuth.asmx

    Hi Eduard Vila,

    What is the following log in addition to the above? The above log seems normal, there's no apparent issue by comparing it with my own update log. Could the client detect update that approved on WSUS server for this client?

    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.

    • Marked as answer by Eduard Vila Thursday, February 4, 2016 3:48 AM
    Monday, February 1, 2016 7:33 AM

All replies

  • BTW, also applied fix KB910336 (Microsoft fix)
    Sunday, January 31, 2016 8:00 PM
  • Also,

    I run this command:wuauclt /resetauthorization /detectnow

    And here 're the logs of windows update:

    2016-01-31 21:24:31:303 1108 11c4 AU ## START ##  AU: Search for updates
    2016-01-31 21:24:31:303 1108 11c4 AU #########
    2016-01-31 21:24:31:303 1108 11c4 AU <<## SUBMITTED ## AU: Search for updates [CallId = {DED7A929-30C6-413B-A592-CB9477DB7423}]
    2016-01-31 21:24:31:303 1108 1688 Agent *************
    2016-01-31 21:24:31:303 1108 1688 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2016-01-31 21:24:31:303 1108 1688 Agent *********
    2016-01-31 21:24:31:303 1108 1688 Agent   * Online = Yes; Ignore download priority = No
    2016-01-31 21:24:31:303 1108 1688 Agent   * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
    2016-01-31 21:24:31:303 1108 1688 Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2016-01-31 21:24:31:303 1108 1688 Agent   * Search Scope = {Machine}
    2016-01-31 21:24:31:313 1108 1688 Setup Checking for agent SelfUpdate
    2016-01-31 21:24:31:313 1108 1688 Setup Client version: Core: 7.6.7600.320  Aux: 7.6.7600.320
    2016-01-31 21:24:33:613 1108 1688 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
    2016-01-31 21:24:33:623 1108 1688 Misc  Microsoft signed: NA
    2016-01-31 21:24:33:623 1108 1688 Misc WARNING: Cab does not contain correct inner CAB file.
    2016-01-31 21:24:33:623 1108 1688 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
    2016-01-31 21:24:33:623 1108 1688 Misc  Microsoft signed: NA
    2016-01-31 21:24:33:623 1108 1688 Setup Wuident for the managed service is valid but not quorum-signed. Skipping selfupdate.
    2016-01-31 21:24:33:623 1108 1688 Setup Skipping SelfUpdate check based on the /SKIP directive in wuident
    2016-01-31 21:24:33:623 1108 1688 Setup SelfUpdate check completed.  SelfUpdate is NOT required.
    2016-01-31 21:24:35:433 1108 1688 PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2016-01-31 21:24:35:433 1108 1688 PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://172.16.0.1/ClientWebService/client.asmx
    2016-01-31 21:24:35:453 1108 1688 PT WARNING: Cached cookie has expired or new PID is available
    2016-01-31 21:24:35:453 1108 1688 PT Initializing simple targeting cookie, clientId = a73b8550-4bab-4a61-bef6-1ca294bcfc5b, target group = , DNS name = laptop01.morgan.net
    2016-01-31 21:24:35:453 1108 1688 PT   Server URL = http://172.16.0.1/SimpleAuthWebService/SimpleAuth.asmx

    Sunday, January 31, 2016 8:28 PM
  • Am 31.01.2016 schrieb Eduard Vila:

    Got some trouble setting up via GPO a WSUS deployment. Clients (2 devices) don't connect to WSUS server.

    Windows 2008 R2 server with WSUS 3.0 SP2 and clients running windows 7 pro sp 1.

    Pls check first the Build from your WSUS. Here you see where you find
    the Build Number: http://www.wsus.de/images/wsus-version.png
    If your WSUS is not Build .274, install the updates for coming up to
    Build .274:

    WSUS 3.0 (SP2):     Build 3.2.7600.226
    WSUS 3.0 (SP2) + KB2720211:     Build 3.2.7600.251
    WSUS 3.0 (SP2) + KB2734608:     Build 3.2.7600.256
    WSUS 3.0 (SP2) + KB2828185:     Build 3.2.7600.262
    WSUS 3.0 (SP2) + KB2938066:     Build 3.2.7600.274

    After this, restart the whole Server und reconnect after your Clients.

    Winfried


    WSUS Package Publisher: http://wsuspackagepublisher.codeplex.com/
    http://technet.microsoft.com/en-us/windowsserver/bb332157.aspx
    http://www.wsuswiki.com/Home

    • Marked as answer by Eduard Vila Thursday, February 4, 2016 3:48 AM
    Monday, February 1, 2016 5:52 AM
  • Also,

    I run this command:wuauclt /resetauthorization /detectnow

    And here 're the logs of windows update:

    2016-01-31 21:24:31:303 1108 11c4 AU ## START ##  AU: Search for updates
    2016-01-31 21:24:31:303 1108 11c4 AU #########
    2016-01-31 21:24:31:303 1108 11c4 AU <<## SUBMITTED ## AU: Search for updates [CallId = {DED7A929-30C6-413B-A592-CB9477DB7423}]
    2016-01-31 21:24:31:303 1108 1688 Agent *************
    2016-01-31 21:24:31:303 1108 1688 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2016-01-31 21:24:31:303 1108 1688 Agent *********
    2016-01-31 21:24:31:303 1108 1688 Agent   * Online = Yes; Ignore download priority = No
    2016-01-31 21:24:31:303 1108 1688 Agent   * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
    2016-01-31 21:24:31:303 1108 1688 Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2016-01-31 21:24:31:303 1108 1688 Agent   * Search Scope = {Machine}
    2016-01-31 21:24:31:313 1108 1688 Setup Checking for agent SelfUpdate
    2016-01-31 21:24:31:313 1108 1688 Setup Client version: Core: 7.6.7600.320  Aux: 7.6.7600.320
    2016-01-31 21:24:33:613 1108 1688 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
    2016-01-31 21:24:33:623 1108 1688 Misc  Microsoft signed: NA
    2016-01-31 21:24:33:623 1108 1688 Misc WARNING: Cab does not contain correct inner CAB file.
    2016-01-31 21:24:33:623 1108 1688 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
    2016-01-31 21:24:33:623 1108 1688 Misc  Microsoft signed: NA
    2016-01-31 21:24:33:623 1108 1688 Setup Wuident for the managed service is valid but not quorum-signed. Skipping selfupdate.
    2016-01-31 21:24:33:623 1108 1688 Setup Skipping SelfUpdate check based on the /SKIP directive in wuident
    2016-01-31 21:24:33:623 1108 1688 Setup SelfUpdate check completed.  SelfUpdate is NOT required.
    2016-01-31 21:24:35:433 1108 1688 PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2016-01-31 21:24:35:433 1108 1688 PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://172.16.0.1/ClientWebService/client.asmx
    2016-01-31 21:24:35:453 1108 1688 PT WARNING: Cached cookie has expired or new PID is available
    2016-01-31 21:24:35:453 1108 1688 PT Initializing simple targeting cookie, clientId = a73b8550-4bab-4a61-bef6-1ca294bcfc5b, target group = , DNS name = laptop01.morgan.net
    2016-01-31 21:24:35:453 1108 1688 PT   Server URL = http://172.16.0.1/SimpleAuthWebService/SimpleAuth.asmx

    Hi Eduard Vila,

    What is the following log in addition to the above? The above log seems normal, there's no apparent issue by comparing it with my own update log. Could the client detect update that approved on WSUS server for this client?

    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.

    • Marked as answer by Eduard Vila Thursday, February 4, 2016 3:48 AM
    Monday, February 1, 2016 7:33 AM
  • Hello Winfried and Anne,

    Thanks for your response!!

    After 6 hours of troubleshooting and 1 more hour to sync and download updates, apparently the issue is gone.

    It tried a lot to sync updates, don't know why ... Also there was an issue accessing shared folders (slow transfer of files).

    After enabling IPv6, network discovery and disabling autotunning, everything was ok.

    Honestly, I hate to say that, but I don't know how I repair the issue.

    Thanks a lot.

    Best regards.

    Thursday, February 4, 2016 3:48 AM
  • Am 04.02.2016 schrieb Eduard Vila:

    After enabling IPv6, network discovery and disabling autotunning, everything was ok.

    Honestly, I hate to say that, but I don't know how I repair the issue.

    I think enabling IPV6 was the solution.

    Winfried


    WSUS Package Publisher: http://wsuspackagepublisher.codeplex.com/
    http://technet.microsoft.com/en-us/windowsserver/bb332157.aspx
    http://www.wsuswiki.com/Home

    Thursday, February 4, 2016 5:55 AM