locked
New computers are not reporting into WSUS RRS feed

  • Question

  • Hi,

    We have a WSUS 3.0 server running on Windows Server 2003.  For the past few months we have noticed that new computers which we have joined on to the domain are not reporting their status into WSUS and therefore are not receiving updates.  All existing PCs continue to report and continue to receive updates.

    I have been working on this issue for some time and feel I have tried everything the internet has suggested.

    I have tried all the obvious things on the client machines such as re-registering Windows Update DLLs, removed the client ID key in the registry etc.  There have been no changes to the server itself and I have reviewed the settings on here and nothing seems amiss.

    Finally, we fully updated Server 2003 and also applied all hotfixes to WSUS 3.0 but this has not made any difference either!

    Can anyone please assist with this?  What is the relevance of the SOAP errors we are seeing?

    Here is an excerpt from the windowsupdate.log

    2016-03-09 16:33:01:142 964 1408 AU Triggering AU detection through DetectNow API
    2016-03-09 16:33:01:142 964 1408 AU Triggering Online detection (non-interactive)
    2016-03-09 16:33:01:142 964 16c8 AU #############
    2016-03-09 16:33:01:142 964 16c8 AU ## START ##  AU: Search for updates
    2016-03-09 16:33:01:142 964 16c8 AU #########
    2016-03-09 16:33:01:142 964 16c8 AU <<## SUBMITTED ## AU: Search for updates [CallId = {D67F2984-842B-4765-90FC-2E667E0FEAC2}]
    2016-03-09 16:33:01:142 964 11fc Agent *************
    2016-03-09 16:33:01:142 964 11fc Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2016-03-09 16:33:01:142 964 11fc Agent *********
    2016-03-09 16:33:01:142 964 11fc Agent  * Online = Yes; Ignore download priority = No
    2016-03-09 16:33:01:142 964 11fc 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-03-09 16:33:01:142 964 11fc Agent  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2016-03-09 16:33:01:142 964 11fc Agent  * Search Scope = {Machine}
    2016-03-09 16:33:01:142 964 11fc Setup Checking for agent SelfUpdate
    2016-03-09 16:33:01:142 964 11fc Setup Client version: Core: 7.6.7601.18804  Aux: 7.6.7601.18804
    2016-03-09 16:33:01:189 964 11fc Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
    2016-03-09 16:33:01:205 964 11fc Misc Microsoft signed: NA
    2016-03-09 16:33:01:205 964 11fc Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\TMP71D6.tmp with dwProvFlags 0x00000080:
    2016-03-09 16:33:01:220 964 11fc Misc Microsoft signed: NA
    2016-03-09 16:33:01:220 964 11fc Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
    2016-03-09 16:33:01:236 964 11fc Misc Microsoft signed: NA
    2016-03-09 16:33:01:251 964 11fc Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
    2016-03-09 16:33:01:251 964 11fc Misc Microsoft signed: NA
    2016-03-09 16:33:01:251 964 11fc Setup Determining whether a new setup handler needs to be downloaded
    2016-03-09 16:33:01:251 964 11fc Setup SelfUpdate handler is not found.  It will be downloaded
    2016-03-09 16:33:01:251 964 11fc Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320"
    2016-03-09 16:33:01:267 964 11fc Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
    2016-03-09 16:33:01:267 964 11fc Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320"
    2016-03-09 16:33:01:267 964 11fc Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
    2016-03-09 16:33:01:267 964 11fc Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320"
    2016-03-09 16:33:01:283 964 11fc Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
    2016-03-09 16:33:01:283 964 11fc Setup SelfUpdate check completed.  SelfUpdate is NOT required.
    2016-03-09 16:33:01:470 964 11fc PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2016-03-09 16:33:01:470 964 11fc PT  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://hull-wsus01:8530/ClientWebService/client.asmx
    2016-03-09 16:33:01:532 964 11fc PT Initializing simple targeting cookie, clientId = 9492997c-67b7-4532-998d-4cf0a94dfaee, target group = , DNS name = g-22jfz72.ad.xxxx.co.uk
    2016-03-09 16:33:01:532 964 11fc PT  Server URL = http://xxx-wsus01:8530/SimpleAuthWebService/SimpleAuth.asmx
    2016-03-09 16:34:06:928 964 11fc Misc WARNING: Send failed with hr = 80072ee2.
    2016-03-09 16:34:06:928 964 11fc Misc WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
    2016-03-09 16:34:06:928 964 11fc Misc FATAL: SOAP/WinHttp - SendRequest: SendRequestUsingProxy failed. error 0x80072ee2
    2016-03-09 16:34:06:928 964 11fc PT  + Last proxy send request failed with hr = 0x80072EE2, HTTP status code = 0
    2016-03-09 16:34:06:928 964 11fc PT  + Caller provided credentials = No
    2016-03-09 16:34:06:928 964 11fc PT  + Impersonate flags = 0
    2016-03-09 16:34:06:928 964 11fc PT  + Possible authorization schemes used = 
    2016-03-09 16:34:06:928 964 11fc PT WARNING: SyncUpdates failure, error = 0x80072EE2, soap client error = 5, soap error code = 0, HTTP status code = 200
    2016-03-09 16:34:06:928 964 11fc PT WARNING: PTError: 0x80072ee2
    2016-03-09 16:34:06:928 964 11fc PT WARNING: SyncUpdates_WithRecovery failed.: 0x80072ee2
    2016-03-09 16:34:06:928 964 11fc PT WARNING: Sync of Updates: 0x80072ee2
    2016-03-09 16:34:06:928 964 11fc PT WARNING: SyncServerUpdatesInternal failed: 0x80072ee2
    2016-03-09 16:34:06:928 964 11fc Agent  * WARNING: Failed to synchronize, error = 0x80072EE2
    2016-03-09 16:34:06:928 964 11fc Agent  * WARNING: Exit code = 0x80072EE2
    2016-03-09 16:34:06:928 964 11fc Agent *********
    2016-03-09 16:34:06:928 964 11fc Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2016-03-09 16:34:06:928 964 11fc Agent *************
    2016-03-09 16:34:06:928 964 11fc Agent WARNING: WU client failed Searching for update with error 0x80072ee2
    2016-03-09 16:34:06:959 964 1058 AU >>##  RESUMED  ## AU: Search for updates [CallId = {D67F2984-842B-4765-90FC-2E667E0FEAC2}]
    2016-03-09 16:34:06:959 964 1058 AU  # WARNING: Search callback failed, result = 0x80072EE2
    2016-03-09 16:34:06:959 964 1058 AU  # WARNING: Failed to find updates with error code 80072EE2
    2016-03-09 16:34:06:959 964 1058 AU #########
    2016-03-09 16:34:06:959 964 1058 AU ##  END  ##  AU: Search for updates [CallId = {D67F2984-842B-4765-90FC-2E667E0FEAC2}]

    Any help would be much appreciated.

    Thanks

    Allan

    Wednesday, March 9, 2016 4:47 PM

All replies

  • Hi smittyuk,

    According to your description, new joined computers don't report to the WSUS server, we may do the following things and check the result:

    1. What are the new joined computer's OS version?

    2. Check if the new joined computers have applied the WSUS GPO correctly, you may run gpresult /h C:\report.html on client to check the result, also check if the related registry keys have been changed correctly:

    Configure Automatic Updates using Registry Editor

    https://technet.microsoft.com/en-us/library/dd939844(v=ws.10).aspx

    3. Try reset windows update component on client:

    Reset windows update component:

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

    4. Also try reset SUSID on one of those clients to test if the SUSID is duplicated:

    Reset WSUS Authorization and get new WSUS SID:

    https://gallery.technet.microsoft.com/scriptcenter/Reset-WSUS-Authorization-2e26d1b0

    5. Rename the SoftwareDistribution folder on client:

    In cmd, enter net stop wuauserv;

    Find SoftwareDistribution folder located in C:\Windows\SoftwareDistribution, rename it.

    In cmd, enter net start wuauserv;

    6. On WSUS server, run server cleanup wizard; If the above methods still doesn't work, also reindex WSUS database on WSUS server:

    Reindex WSUS database:

    https://technet.microsoft.com/en-us/library/dd939795(v=ws.10).aspx

    Welcome to feed back the result.

    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.

    Thursday, March 10, 2016 2:32 AM
  • Hi,

    Apologies for the delay in replying, I have tried all of your suggestions previously to no avail and we have just completed the re-indexing of the database but this has made no difference either.

    Is there anything other than the above that you could suggest?

    Monday, April 4, 2016 3:54 PM
  • Hi smittyuk,

    Then could the clients update from the Internet?

    And it will be better if you can provide some new clues.

    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, April 5, 2016 3:21 AM