Windows Update Through WSUS Breaks After Cloning Server
In today’s rapid world of Information Technology, there is an increased demand to quickly spin up servers. If you deploy Windows servers from a template or cloning, however, there is an issue that can show up when trying to patch these servers when using Windows Server Update Services (WSUS).
The biggest symptom that I encountered was the server disappears from WSUS. The cause is that both servers have the same ID for SusClientID in the registry. (HTLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate).
To resolve the issue, perform the following steps:
- Stop the Windows Update Service on the server (net stop wuauserv)
- Delete the SUSClientId from the registry on the server (make sure you backup the registry first)
- Start the Windows Update Service (net start wuauserv)
- Run the following command:
- Wuauclt /restauthorization /detectnow
You will now see that the server has a new SusClientID and will no longer disappear from WSUS.