A most weird WSUS problem

[mattx]

Never had much of a problem with WSUS until now and this one is really odd.

25 New PCs in our IT Room - all built and ready to go. They all update without any problems from the WSUS server but here is weird point number 1.

The PCs DO NOT appear in the console !! I have run the usual switches and checked the windowsupdate.log file and they report fine. I have even reset the clients using the:

 

wuauclt /resetauthorization /detectnow

 

Switch. I have also run a clear up of unwanted updates / computers etc. I have also removed all duplicate entries from DHCP and DNS as of course these new PCs have the same name as the old ones - they have new SIDs. So why do they update from the WSUS server but don't appear ?

Also weird point number 2 is really weird !! If I run the:

 

wuauclt /resetauthorization /detectnow on a client

 

Switch, then hit re-fresh, the PC appears !! Hooray, then if you run the same switch on another PC that PC on which you first ran it on disappears and the new PC appears !! And so on !! So all in all I can only get ONE PC out of the 24 to appear in the console !!

[strawberry]

forgive the question,but they machines do have seperate sids from each other dont they?

[greatone]

Have you reset the WSUSID on each machine?

[mattx]

http://support.microsoft.com/kb/903262

 

Have found this - will give it a bash...

 

Rem - Batch script to delete duplicate SusClientIDs
Rem - Implement this script as a "Startup" or "Logon"  script
Rem - Script creates an output file called %Systemdrive%\SUSClientID.log
Rem - If the %Systemdrive%\SUSClientID.log is already present, then the script simply exits

@Echo off
if exist %systemdrive%\SUSClientID.log goto end
net stop wuauserv
net stop bits
reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v PingID /f  > %systemdrive%\SUSClientID.log 2>&1
reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v AccountDomainSid /f  >> %systemdrive%\SUSClientID.log 2>&1
reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientId /f  >> %systemdrive%\SUSClientID.log 2>&1
net start wuauserv
wuauclt.exe /resetauthorization /detectnow         
:end
exit

Edited August 13, 2009 by mattx

[p858snake]

How did you give them new SIDs? Sysprep or NewSID?

[mattx]

How did you give them new SIDs? Sysprep or NewSID?

 

Sysprep - the script works btw - got them all where I want them now !!

[gshaw]

Yup that reg file is the usual fix as Sysprep doesn't reset the WSUS client ID

[mattx]

Yup that reg file is the usual fix as Sysprep doesn't reset the WSUS client ID

 

Now part of my build process......

[DMcCoy]

Yup that reg file is the usual fix as Sysprep doesn't reset the WSUS client ID

 

Which version of sysperp are you using? I've never had to reset the IDs here.

[mattx]

I was using the version that comes with Ghost 8.0 - I have to say this is the first time I have experienced this problem - I have upgraded rooms before with the same name in regards to WSUS and never had a problem - strange why it happened this time round....

[DMcCoy]

You should be using the Deployment tools from the current service pack on the machine, older versions can be broken by the SP updates.

 

 

Download details: Windows XP Service Pack 3 Deployment Tools

[mattx]

You should be using the Deployment tools from the current service pack on the machine, older versions can be broken by the SP updates.

 

 

Download details: Windows XP Service Pack 3 Deployment Tools

 

Thanks for the link, the new builds had SP3 streamlined - I'll use this updated version from now on though...

[DMcCoy]

Thanks for the link, the new builds had SP3 streamlined - I'll use this updated version from now on though...

 

It's just an updated sysprep.exe and the tools for sysprep to run - just replace the ones in the sysprep config folders on the ghost server in All users, although I usually run sysprep manually then take an image with ghost.