Asha'man X
Expert Member
- Joined
- Aug 31, 2006
- Messages
- 1,401
Hey everyone
Just discovered a rather interesting issue in regards to WSUS when you clone computers on a network. We just recently set up 2computer labs running XP SP3, and as usual sysprepped the computers. However, none of them were reporting into the WSUS console afterwards.
After some digging, we found that the client id's in the registry were identical, causing only 1 computer to show up despite sysprep running before the clone.
To fix this, delete the SusClient ID and the SusClientIdValidation entries in this registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate
Afterwards, you can sysprep the machine and clone them, and they should show up in WSUS after they have done everything.
I don't know how this would work with Vista and 7, as I have not had a chance to prepare them for cloning yet.
Hope this helps somebody avoid our pain
Just discovered a rather interesting issue in regards to WSUS when you clone computers on a network. We just recently set up 2computer labs running XP SP3, and as usual sysprepped the computers. However, none of them were reporting into the WSUS console afterwards.
After some digging, we found that the client id's in the registry were identical, causing only 1 computer to show up despite sysprep running before the clone.
To fix this, delete the SusClient ID and the SusClientIdValidation entries in this registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate
Afterwards, you can sysprep the machine and clone them, and they should show up in WSUS after they have done everything.
I don't know how this would work with Vista and 7, as I have not had a chance to prepare them for cloning yet.
Hope this helps somebody avoid our pain