tmassa99
Thanks for the response, this is pretty much all I was able to find out myself.
Cheers
JamesDS
Main Topics
Browse All TopicsMy current client has deployed about 900 Windows 2000 SP4 machines with the same SID - IE ghosted, but without running SYSPREP or NewSID afterwards.
These machines have been joined to an AD domain, which I am about to migrate (with ADMTv3) to a new AD domain as part of an infrastructure upgrade.
I can find lots of info on how to change SIDs, but nothing on the ramifications of duplicate machine SIDs on a Windows Server 2003 R2 Domain (W2K3 functional level). I've looked at the Domain SIDs and these are all unique due to the action of the RID on joining the domain - this is a problem related to the machine SID, assuming there is even a problem.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: tmassa99Posted on 2007-07-17 at 07:20:23ID: 19505080
Then all local administrator accounts on all computers with the same SID can easily be compromised. It's not a huge deal, but since it's so easy to change, you should.
echnet/sys internals/ Utilities/ NewSid.msp x
http://www.microsoft.com/t
Duplicate SIDs aren't an issue in a Domain-based environment since domain accounts have SID's based on the Domain SID. But, according to Microsoft Knowledge Base article Q162001, "Do Not Disk Duplicate Installed Versions of Windows NT", in a Workgroup environment security is based on local account SIDs. Thus, if two computers have users with the same SID, the Workgroup will not be able to distinguish between the users. All resources, including files and Registry keys, that one user has access to, the other will as well.
Another instance where duplicate SIDs can cause problems is where there is removable media formated with NTFS, and local account security attributes are applied to files and directories. If such a media is moved to a different computer that has the same SID, then local accounts that otherwise would not be able to access the files might be able to if their account IDs happened to match those in the security attributes. This is not be possible if computers have different SIDs.
-TM