• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 190
  • Last Modified:

WSUS Clients (Imaged) not reporting

I am using WSUS 3.0 on Server 2003.  Clients are XP Pro and created from an image.  The clients created with the new image I am using are not reporting.  Only one of the newly imaged machines will show up at a time and then go away to be replaced by another.  I believe this has something to do with the SID or client ID of the original image being copied to the other machines.
1 Solution
Did you use SysPrep to take care of the SID issue?
Toni UranjekConsultant/TrainerCommented:
Hi Bill_Simmons,

If you have SID issues use newsid to change it: http://technet.microsoft.com/en-us/sysinternals/bb897418.aspx
Then go to command prompt and run the following command: "wuauclt /resetauthorization /detectnow ".


Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Here is a batch script which will delete duplicate SUS SIDs.  A new SID will be created during the next detection.

Malli BoppeCommented:
With windows 2003 you need to delete

REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientId /f

You need to bother about the keys.This are for windows 2000 server

REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v AccountDomainSid /f
REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v PingID /f

Bill_SimmonsAuthor Commented:
Worked like a charm!

Featured Post

[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now