locked
WSUS Sync Issue between Windows 7 Clients. RRS feed

  • Question

  • Hi All,

    We have SCCM 2007 R2 with WSUS has installed on the same server and we have windows 7 clients almost 2000 machines.

    After April month patch releasing we checked wsus server "Required Cloumn for Windows 7" machines, the required count is very low "80". We checked "All Computers" field & most of Client machines status as "Not yet Reported". But servers are okey & all of the servers scanned by wsus & there is no issue. Issue with Windows 7 client. This is my issue. I updated below windows update log from one machine which is affected.

    2015-04-20 08:26:56:724 492 630 PT WARNING: SyncUpdates failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
    2015-04-20 08:26:56:724 492 630 PT WARNING: SOAP Fault: 0x00012c
    2015-04-20 08:26:56:724 492 630 PT WARNING: faultstring:Fault occurred
    2015-04-20 08:26:56:724 492 630 PT WARNING: ErrorCode:InvalidParameters(7)
    2015-04-20 08:26:56:724 492 630 PT WARNING: Message:parameters.OtherCachedUpdateIDs
    2015-04-20 08:26:56:724 492 630 PT WARNING: Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
    2015-04-20 08:26:56:724 492 630 PT WARNING: ID:a2139655-6c05-4a6d-8cf0-fd65ed75d674
    2015-04-20 08:26:56:724 492 630 PT WARNING: PTError: 0x8024400d
    2015-04-20 08:26:56:724 492 630 PT WARNING: SyncUpdates_WithRecovery failed.: 0x8024400d
    2015-04-20 08:26:56:724 492 630 PT WARNING: Sync of Updates: 0x8024400d
    2015-04-20 08:26:56:724 492 630 PT WARNING: SyncServerUpdatesInternal failed: 0x8024400d
    2015-04-20 08:26:56:724 492 630 Agent * WARNING: Failed to synchronize, error = 0x8024400D
    2015-04-20 08:26:56:724 492 630 Agent * WARNING: Exit code = 0x8024400D
    2015-04-20 08:26:56:724 492 630 Agent *********
    2015-04-20 08:26:56:724 492 630 Agent ** END ** Agent: Finding updates [CallerId = CcmExec] 

    error = 0x8024400D  - The same error code shows on scanagent.log, wuahandler.log also.

    I tried below steps but not worked.

    *We've not changed any Group Policys related with WSUS.
    *I tried client level troubleshoot like Renamed Softwaredistripution folder, Renamed ccmroot folder & Deleted root\ccm folder also.

    * Today i checked WSUS version & client's WUA version both of them showing different digits, it's on issue ?

    Update Services
    Microsoft Corporation
    Version: 3.2.7600.226

    Client version: Core: 7.6.7600.320  Aux: 7.6.7600.320

    I need your assist to resolve this issue....

    Thanks in Advance,

    Srini...



    Wednesday, April 22, 2015 11:10 PM

Answers

  • If these are cloned machines, follow this KB:

    KB903262

    1. Click Start, click Run, type cmd in the Open box, and then click OK.
    2. At the command prompt, type net stop wuauserv, and then press ENTER.
    3. Click Start, click Run, type regedit in the Open box, and then click OK.
    4. Locate and then click the following registry subkey:
      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate
    5. In the details pane of Registry Editor, delete the following registry entries:
      • PingID
      • AccountDomainSid
      • SusClientId
      • SusClientIDValidation
    6. Exit Registry Editor.
    7. At the command prompt, type net start wuauserv, and then press ENTER.
    8. At the command prompt, type wuauclt.exe /resetauthorization /detectnow, and then press ENTER.
    9. Wait 10 minutes for a detection cycle to finish.
    10. Start the WSUS console to make sure that the clients appear in the WSUS console.

    Rolf Lidvall, Swedish Radio (Ltd)

    Monday, April 27, 2015 7:11 AM

All replies

  • Hi Srini,

    Please try to runt the server clean up wizard on the WSUS server.

    Also, please try to reset the windows update components on client.

    For detailed information about how to reset the windows update components, please refer to the link below:

    https://support.microsoft.com/en-us/kb/971058?wa=wsignin1.0

    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.

    Monday, April 27, 2015 2:50 AM
  • If these are cloned machines, follow this KB:

    KB903262

    1. Click Start, click Run, type cmd in the Open box, and then click OK.
    2. At the command prompt, type net stop wuauserv, and then press ENTER.
    3. Click Start, click Run, type regedit in the Open box, and then click OK.
    4. Locate and then click the following registry subkey:
      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate
    5. In the details pane of Registry Editor, delete the following registry entries:
      • PingID
      • AccountDomainSid
      • SusClientId
      • SusClientIDValidation
    6. Exit Registry Editor.
    7. At the command prompt, type net start wuauserv, and then press ENTER.
    8. At the command prompt, type wuauclt.exe /resetauthorization /detectnow, and then press ENTER.
    9. Wait 10 minutes for a detection cycle to finish.
    10. Start the WSUS console to make sure that the clients appear in the WSUS console.

    Rolf Lidvall, Swedish Radio (Ltd)

    Monday, April 27, 2015 7:11 AM