Cloned Machines Not Reporting Into WSUS Server

By | April 30, 2009

I had several machines not checking into a new WSUS server. After some digging I discovered that after cloning machines from the same image that a registry key was preventing the machines from joining the WSUS server. You see, they all had the same SusClientID key and would compete for the connection to the server.



Create a .bat script and you can push this out with Altiris or add to a logon script. 


————Copy Everything Below This Line————

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

REG Delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v SusClientIdValidation  /f

REG Add HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate /v WUServer /t REG_SZ /d http://SERVERNAME HERE:8530 /F

REG Add HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate /v WUStatusServer /t REG_SZ /d http:// SERVERNAME HERE /F



net stop wuauserv /y

net stop BITS /y

rd C:\WINDOWS\SoftwareDistribution /s /Q

del "c:\windows\windowsupdate.log"

regsvr32 WUAPI.DLL /s

regsvr32 WUAUENG.DLL /s

regsvr32 WUAUENG1.DLL /s

regsvr32 ATL.DLL /s

regsvr32 WUCLTUI.DLL /s

regsvr32 WUPS.DLL /s

regsvr32 WUPS2.DLL /s

regsvr32 WUWEB.DLL /s

regsvr32 msxml3.dll /s

net start wuauserv /y

wuauclt.exe /resetauthorization /detectnow


————Copy Everything Above This Line————



1.      Copy this script to a txt doc and save as a batch file.

2.      Change this line to match your server path http://SERVERNAME HERE:8530

3.      FYI: The number at the end of the server path above is a port number, this may not be needed for your implementation.


***Make sure NO word wrap is happening in your script

This information is provided "AS IS" with no warranties expressed or implied.

Leave a Reply

Your email address will not be published. Required fields are marked *