WSUS Client Fix (Win XP)

In WUS world, for the clients to report to the server, they must have a unique identifier (thats how computers are identified). Which is SID.

Since in big production areas, systems are imaged rather than individually installed. As a result, the SID is duplicated instead of generated.

That will cause WUS server to create only one record that keeps updating its information to each client.

The fix for that is to regenerate a SID.

There are many programs that can do that, a good one is called NewSID (google it).

Its free and very usefull.

In windows 2k, SID was enough to make a computer unique in WUS. But in XP there is another identification number required to make a computer unique.

It is called Susclientid. And its located in the Registry.

Unfortunatly, NewSID doesnt do that automatically.

In other words, even if you give every computer a new SID, they will still report to WUS as one computer.

So the fix for this to delete that key in the registry, and force to computer to generate a new one.



This batch file can do the job for you.

@echo off
@echo Fixing WU Client
@echo Deleting Keys
@REG DELETE "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientId /f
@REG DELETE "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientIdValidation /f

@echo Restarting WUAgent Service
@net stop wuauserv
@net start wuauserv

@echo Force a detection
@wuauclt /resetauthorization /detectnow

@echo Fix is Done. Should show up in WUS shortly.

REM @pause