Overview
This article explains how to resolve duplicate SusClientId issues that occur when Windows endpoints are cloned from templates.
It provides diagnostic steps and a complete solution to fix conflicting WSUS client identifiers.
Problem Description
This can happen when you clone Windows endpoints from a template if the template does not account for this problem.
WSUS uses the SusClientId to identify unique devices and then associates the computer's hostname with the unique identifier for display purposes.
The problem is that if the SusClientId on several machines is the same and that is what is used by WSUS, then when they report into WSUS, conflicts will arise, causing unexpected errors.
Diagnosis
If you suspect that multiple machines have the same SusClientId, you can run the following batch command on those machines and compare the output
| reg query HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate /v SusClientId |
Solution
How to fix. Run the following from a command prompt as an admin
#Stop the Automatic Updates service sc stop wuauserv # Delete the SUSclientID registry key from the following location: reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SUSClientID /f #Start the Automatic Updates servicesc start wuauserv #Re-register windows client in WUSS wuauclt /resetauthorization /detectnowwuauclt /reportnow |
Comments
0 comments
Please sign in to leave a comment.