I messed up my VMware template setup and now I have 15 production Server 2022 VMs with identical machine SIDs. I also have a few Windows 11 VMs that I've managed to change the SIDs on using SIDCHG64.exe and SIDCHGL64 without any issues because they're mainly client machines. However, I ran into trouble when I used the tool on my VeeamOne server, which caused the reporting service to fail to start, so I reverted after taking a snapshot. I'm hesitant to act further since we haven't noticed problems with the servers, but should I just leave them as they are?
5 Answers
I don't have personal experience with SIDCHG64, but generally, duplicate SIDs are problematic mainly for domain controllers. You should still consider fixing the template.
Don't sweep this under the rug! Use Microsoft's sysprep method to generalize and rejoin your servers to the domain or consider building new servers entirely and migrating over.
Definitely address the issue! It's bad practice to ignore this, especially on servers. Consider starting over with your template before you run into big problems later.
Once machines are domain-joined, their machine SID is less of a concern. But if they're not, you definitely need to fix it. Microsoft doesn't support environments with duplicate SIDs, so this could lead to a lot of headaches for you.
Leaving the duplicate SIDs as is could create serious issues down the line. It's better to address this now rather than pay for your mistake later.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures