Exchangepedia Blog is read by visitors from all 50 US States and 150 countries world-wide
If you simply copy an existing Windows OS image to create multiple virtual servers/workstations, and try to log on to a domain controller, you may get the following error:
The system or security ID (SID) of the domain specified is inconsistent with the trust information for that domain.
This happens because the SID of the computer was not changed when you made a copy of the virtual hard disk containing the OS. A good way to use a base drive image would be to Sysprep it first.
Nevertheless, if you haven't done that, log in to the computer locally. Use the PsGetSID and NewSid utilities from Sysinternals web site (www.sysinternals.com). Use PsGetSID (command-line - type PsGetSID to get the SID of local computer, copy to notepad, type PsGetSID \\DomainController -u username -p password to get the SID of the domain controller, and compare the two. If they're the same, now you know the reason why.
Proceed with the NewSID utility to generate a random SID for the computer. This takes a little while as NewSID replaces the old SID with the new one in the registry, amongst other things. Once done, the computer will reboot automatically (there's a checkmark to reboot... leave it unchecked if you don't want to reboot.)
You can now log in to the domain without getting the SID error.
The system or security ID (SID) of the domain specified is inconsistent with the trust information for that domain.
This happens because the SID of the computer was not changed when you made a copy of the virtual hard disk containing the OS. A good way to use a base drive image would be to Sysprep it first.
Nevertheless, if you haven't done that, log in to the computer locally. Use the PsGetSID and NewSid utilities from Sysinternals web site (www.sysinternals.com). Use PsGetSID (command-line - type PsGetSID to get the SID of local computer, copy to notepad, type PsGetSID \\DomainController -u username -p password to get the SID of the domain controller, and compare the two. If they're the same, now you know the reason why.
Proceed with the NewSID utility to generate a random SID for the computer. This takes a little while as NewSID replaces the old SID with the new one in the registry, amongst other things. Once done, the computer will reboot automatically (there's a checkmark to reboot... leave it unchecked if you don't want to reboot.)
You can now log in to the domain without getting the SID error.
0 Comments:
Post a Comment
Links to this post:
Create a Link
<< Home