The Machine SID Duplication Myth (and Why Sysprep Matters) - Mark's Blog. The reason that I began considering NewSID for retirement is that, although people generally reported success with it on Windows Vista, I hadn’t fully tested it myself and I got occasional reports that some Windows component would fail after NewSID was used.
When I set out to look into the reports I took a step back to understand how duplicate SIDs could cause problems, a belief that I had taken on faith like everyone else. The more I thought about it, the more I became convinced that machine SID duplication – having multiple computers with the same machine SID – doesn’t pose any problem, security or otherwise. I took my conclusion to the Windows security and deployment teams and no one could come up with a scenario where two systems with the same machine SID, whether in a Workgroup or a Domain, would cause an issue.
At that point the decision to retire NewSID became obvious. SIDs Windows uses SIDs to represent not just machines, but all security principals. SIDs and Access Control Lists. How can I sysprep Windows Vista ? Sysprep is how you PREPare a SYStem for duplication, and in Windows Vista, it's quite different to the way things were in Windows XP.
This post can always be found on www.windows-noob.com Note: If you are testing SYSPREP that you should limit the total number of syspreps to 3 times maximum otherwise you may experience unusual problems. To Sysprep a Vista Machine: Open a command prompt and enter the following command to prepare themachine for imaging. c:\windows\system32\sysprep\sysprep.exe /quiet /generalize /shutdown /oobe Note At this point SYSPREP.EXE will now prepare the machine for imagingand then shut it down when it has completed the process. The /generalize switch is used to remove the unique information from the machine. If you want it to automatically reboot after running sysprep, then change the code to this c:\windows\system32\sysprep\sysprep.exe /quiet /generalize /reboot/oobe Those two scenarios are called BTP (Build To Plan) and BTO (Build To Order). Changer un SID machine: NewSID vs. SYSPREP. Mercredi, 16 Juin 2010 11:00 Augagneur Sommaire Introduction : Qu’est ce qu’un SID ?
Dans quel cas et pourquoi changer un SID ? Le SID pour « security identifier » ou en français « identifiant de sécurité » est utilisé dans un environnement Microsoft NT et est un identifiant unique attaché à une machine, un utilisateur ou un groupe de sécurité. Il doit être unique sous peine de rencontrer un jour ou l’autre des problèmes. Le changement du SID s’applique généralement dans le cadre du déploiement d’images système au sein d’un groupe de travail (Workgroup) en particulier et dans une moindre mesure dans une infrastructure Active Directory.
NewSID : Pourquoi a-t-il disparu de la circulation ? Pendant quelques années, un petit logiciel de NewSID avait pignon sur rue pour ce genre d’opération. Le logiciel est officiellement non supporté par Microsoft pour la préparation d’image système. SYSPREP : la méthode recommandée par Microsoft Lancer la commande sysprep afin de modifier le SID. Conclusion.