Windows sid updating
At that point the decision to retire New SID became obvious.
I realize that the news that it’s okay to have duplicate machine SIDs comes as a surprise to many, especially since changing SIDs on imaged systems has been a fundamental principle of image deployment since Windows NT’s inception.
Care needs to be taken when cloning Windows virtual machines, particularly if they will later be used as domain controllers.
To ease the deployment task of tens, hundreds, or thousands of workstations and servers, many IT administrators use cloning techniques to clone a sample operating system that’s configured with the right applications, software, and configurations to distribute it to other computers as images.
If you start seeing this, run the Server cleanup wizard in order to clean old records but remember that it may take up to 90 days to clean all records completely.
You might notice that some computers are appearing multiple times in WSUSAdmin - Computers and some of them disappear very often. Take a look at this script which deletes duplicate SUS client IDs found on a computer.
Although other tools exist that claim to do similar things, Sysprep is the only tool that’s supported by Microsoft for this purpose.
To run Sysprep in Windows 10, open Windows Explorer and navigate to C:\Windows\System32\sysprep.If you’re unsure whether you’re using computers with duplicate SIDs, you can use the Ps Get Sid tool by Microsoft Sysinterals.