Imagine Microsoft delivering an update that requires unique SIDs while all the machines in your network uses have all the same SID.
Therefore, Microsoft assumes that unique SIDs is standard. According to Microsoft's official guidelines, it is still necessary to run Sysprep before you deploy an OS image. However, I still strongly recommend ensuring that all computers in a productive environment have a unique SID, for the following reason: Future proof ^Įven if it is true that Microsoft doesn't use SIDs to identify Windows machines, you can't be sure that this will also be the case in the future. It is interesting to note that I also never run into problems with the latest Windows versions because of duplicate SIDs. Running Sysprep every time is just too cumbersome.
I am usually testing with virtualization software and I create new test machines using cloning technology almost every day. Even today I often don't use Sysprep in test environments.
0 kommentar(er)
