locked
Your WSUS server currently shows that no computers are registered to receive updates RRS feed

  • Question

  • I just recently installed Windows Server R2 Std and installed WSUS, this will be replacing my existing Windows 2003 Server configured for WSUS.

    * configured WSUS, approved updates

    * applied the GPO to a test OU, checked the test server which is also Windows 2012 R2 and it changed the registry settings pointing to the new server. 

    In the Update Services console it still reflects that no computers are contacting the server for registrations.  I read a few blogs and it has pointed me to the update log.  I initiated a "wuauclt /detectnow"  See log below:

    2015-05-06 09:09:01:820  940 23d0 AU Triggering AU detection through DetectNow API
    2015-05-06 09:09:01:820  940 23d0 AU Triggering Online detection (non-interactive)
    2015-05-06 09:09:01:820  940 1134 AU #############
    2015-05-06 09:09:01:820  940 1134 AU ## START ##  AU: Search for updates
    2015-05-06 09:09:01:820  940 1134 AU #########
    2015-05-06 09:09:01:821  940 1134 AU <<## SUBMITTED ## AU: Search for updates [CallId = {BEE18B80-5F64-40A2-B3E8-09955010B684}]
    2015-05-06 09:09:01:821  940 1154 Agent *************
    2015-05-06 09:09:01:821  940 1154 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2015-05-06 09:09:01:821  940 1154 Agent *********
    2015-05-06 09:09:01:821  940 1154 Agent   * Online = Yes; Ignore download priority = No
    2015-05-06 09:09:01:821  940 1154 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"
    2015-05-06 09:09:01:821  940 1154 Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2015-05-06 09:09:01:821  940 1154 Agent   * Search Scope = {Machine}
    2015-05-06 09:09:01:821  940 1154 Setup Checking for agent SelfUpdate
    2015-05-06 09:09:01:822  940 1154 Setup Client version: Core: 7.6.7601.18804  Aux: 7.6.7601.18804
    2015-05-06 09:09:01:930  940 1154 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
    2015-05-06 09:09:01:936  940 1154 Misc  Microsoft signed: NA
    2015-05-06 09:09:01:941  940 1154 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\TMP7723.tmp with dwProvFlags 0x00000080:
    2015-05-06 09:09:02:154  940 1154 Misc  Microsoft signed: NA
    2015-05-06 09:09:02:188  940 1154 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
    2015-05-06 09:09:02:192  940 1154 Misc  Microsoft signed: NA
    2015-05-06 09:09:02:355  940 1154 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
    2015-05-06 09:09:02:358  940 1154 Misc  Microsoft signed: NA
    2015-05-06 09:09:02:370  940 1154 Setup Determining whether a new setup handler needs to be downloaded
    2015-05-06 09:09:02:370  940 1154 Setup SelfUpdate handler is not found.  It will be downloaded
    2015-05-06 09:09:02:370  940 1154 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320"
    2015-05-06 09:09:03:487  940 1154 Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320" is not applicable
    2015-05-06 09:09:03:495  940 1154 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320"
    2015-05-06 09:09:03:579  940 1154 Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is not applicable
    2015-05-06 09:09:03:580  940 1154 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320"
    2015-05-06 09:09:03:653  940 1154 Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is not applicable
    2015-05-06 09:09:03:654  940 1154 Setup SelfUpdate check completed.  SelfUpdate is NOT required.
    2015-05-06 09:09:04:890  940 1154 PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2015-05-06 09:09:04:891  940 1154 PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = mynewserver/ClientWebService/client.asmx (removed link so I could post)

    2015-05-06 09:09:04:956  940 1154 PT WARNING: Cached cookie has expired or new PID is available
    2015-05-06 09:09:04:956  940 1154 PT Initializing simple targeting cookie, clientId = 2aa466b2-fa98-4310-95c7-b63aa97ee63e, target group = , DNS name = 072300-w7.server.com
    2015-05-06 09:09:04:956  940 1154 PT   Server URL

    mynewserver/SimpleAuthWebService/SimpleAuth.asmx (removed link so I could post)

    2015-05-06 09:09:04:962  940 1154 PT WARNING: GetAuthorizationCookie failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404
    2015-05-06 09:09:04:962  940 1154 PT WARNING: Failed to initialize Simple Targeting Cookie: 0x80244019
    2015-05-06 09:09:04:962  940 1154 PT WARNING: PopulateAuthCookies failed: 0x80244019
    2015-05-06 09:09:04:962  940 1154 PT WARNING: RefreshCookie failed: 0x80244019
    2015-05-06 09:09:04:962  940 1154 PT WARNING: RefreshPTState failed: 0x80244019
    2015-05-06 09:09:04:962  940 1154 PT WARNING: Sync of Updates: 0x80244019
    2015-05-06 09:09:04:962  940 1154 PT WARNING: SyncServerUpdatesInternal failed: 0x80244019
    2015-05-06 09:09:04:962  940 1154 Agent   * WARNING: Failed to synchronize, error = 0x80244019
    2015-05-06 09:09:04:963  940 1154 Agent   * WARNING: Exit code = 0x80244019
    2015-05-06 09:09:04:963  940 1154 Agent *********
    2015-05-06 09:09:04:963  940 1154 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2015-05-06 09:09:04:963  940 1154 Agent *************
    2015-05-06 09:09:04:963  940 1154 Agent WARNING: WU client failed Searching for update with error 0x80244019
    2015-05-06 09:09:05:007  940 a4c AU >>##  RESUMED  ## AU: Search for updates [CallId = {BEE18B80-5F64-40A2-B3E8-09955010B684}]
    2015-05-06 09:09:05:007  940 a4c AU   # WARNING: Search callback failed, result = 0x80244019
    2015-05-06 09:09:05:007  940 a4c AU   # WARNING: Failed to find updates with error code 80244019
    2015-05-06 09:09:05:007  940 a4c AU #########
    2015-05-06 09:09:05:007  940 a4c AU ##  END  ##  AU: Search for updates [CallId = {BEE18B80-5F64-40A2-B3E8-09955010B684}]
    2015-05-06 09:09:05:007  940 a4c AU #############
    2015-05-06 09:09:05:008  940 a4c AU Successfully wrote event for AU health state:0
    2015-05-06 09:09:05:008  940 a4c AU AU setting next detection timeout to 2015-05-06 18:09:05
    2015-05-06 09:09:05:008  940 a4c AU Successfully wrote event for AU health state:0
    2015-05-06 09:09:05:008  940 a4c AU Successfully wrote event for AU health state:0
    2015-05-06 09:09:09:963  940 1154 Report REPORT EVENT: {932CF57B-EAFF-4B6C-817D-6B8E1A2592FE} 2015-05-06 09:09:04:963-0400 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80244019 AutomaticUpdates Failure Software Synchronization Windows Update Client failed to detect with error 0x80244019.
    2015-05-06 09:09:09:967  940 1154 Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
    2015-05-06 09:09:09:967  940 1154 Report WER Report sent: 7.6.7601.18804 0x80244019(0) 0000000-0000-0000-0000-000000000000 Scan 0 1 AutomaticUpdates {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} 0

    Any assistance on how to get this working would be greatly appreciated.

    Thank you

    Wednesday, May 6, 2015 1:41 PM

Answers

  • Hi,

    Sorry for the delay.

    According to your log, I assume that you didn't add the port number 8530 into the server URL.

    WSUS server v6.2 and later uses TCP port 8530 by default. Please try to add the port into the server URL

    Here is the screenshot of my lab,

    Best Regards.


    Steven Lee 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.

    Wednesday, June 3, 2015 9:56 AM

All replies

  • The above log is for my test Windows 7 PC.  I have 2 test subjects that I am working with
    Wednesday, May 6, 2015 1:42 PM
  • Hi,

    Sorry for the delay.

    According to your log, I assume that you didn't add the port number 8530 into the server URL.

    WSUS server v6.2 and later uses TCP port 8530 by default. Please try to add the port into the server URL

    Here is the screenshot of my lab,

    Best Regards.


    Steven Lee 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.

    Wednesday, June 3, 2015 9:56 AM