Sign in
 
HomeWindows Server “8” Beta20082003LibraryForums
Windows Server TechCenter > Windows Server Forums > WSUS > Help with Event ID 13032 on WSUS

Answered Help with Event ID 13032 on WSUS

    •  
      Wednesday, February 22, 2012 8:14 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Hi,

      Event 13032 keeps logging

      The description for Event ID 13032 from source Windows Server Update Services cannot be found.

      Either the component that raises this event is not installed on your local computer or the installation is corrupted.

      You can install or repair the component on the local computer.

      If the event originated on another computer, the display information had to be saved with the event.

      The following information was included with the event:

      Many client computers have not reported back to the server in the last 30 days.

      Any known fix?

      Thanks

       

    Answers

    • Thursday, February 23, 2012 6:47 AM
      Moderator
       
       Answered
      Sign In to Vote
      0
      Sign In to Vote

      Hi,

      Did you have a duplicated copy images of those clients?This issue occurs because the imaged clients may have a duplicate SusClientID value in the registry.

      Please try the remediation described in KB903262 for duplicate SusClientIDs.

      Some symptoms of this may also include computers randomly disappearing/reappearing from/into your WSUS console. Another symptom is the computer will receive updates, but not report into the server properly.

      If the above is not the cause, Run the Client Diagnostic Tool ,inspect the results and verify WUStatusServer registry values are correct.

      At last, the better place to diagnose a "not reporting" issue is the WindowsUpdate.log.Check whether there are some tips for the cause.

      Best regards,

      Clarence

      Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

       

    All Replies

    • Wednesday, February 22, 2012 9:33 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Hi,

      Please provide Windowsupdate.log from client that not reported to WSUS,

      Also how many clients not reporting ? Do they "alive" ?

       
    • Thursday, February 23, 2012 6:47 AM
      Moderator
       
       Answered
      Sign In to Vote
      0
      Sign In to Vote

      Hi,

      Did you have a duplicated copy images of those clients?This issue occurs because the imaged clients may have a duplicate SusClientID value in the registry.

      Please try the remediation described in KB903262 for duplicate SusClientIDs.

      Some symptoms of this may also include computers randomly disappearing/reappearing from/into your WSUS console. Another symptom is the computer will receive updates, but not report into the server properly.

      If the above is not the cause, Run the Client Diagnostic Tool ,inspect the results and verify WUStatusServer registry values are correct.

      At last, the better place to diagnose a "not reporting" issue is the WindowsUpdate.log.Check whether there are some tips for the cause.

      Best regards,

      Clarence

      Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.