JamesDS
asked on
Ramifications of Duplicate Machine SIDs on an AD Domain running W2K3R2
My 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.
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for the response, this is pretty much all I was able to find out myself.
Cheers
JamesDS