I maintain a complete test environment, including two DC, two SQL, three SharePoint 2007, two SharePoint 2010, SharePoint 2003, FAST for SharePoint, Exchange, Win 7, one for Windows XP. all are virtual machines supported by Hyper-V.
Once, one of my VMS completely broke down and could not be repaired, so I killed the system and added it with a clean image. after the domain is successfully added, the domain administrator cannot log on to the machine after the restart.
Error Message
==========
The name or security ID (SID) of the domain specified is inconsistent with the trust information for that domain.
Contact your system administrator or domain administrator to resolve the inconsistency.
After studying for a while, I found the cause of the problem.
==========
The image of the virtual machine I used was used in our domain. the virtual machine operating system itself has a SID, which will not be changed even if it is added to the domain. the domain controller maintains a list of the sid of all machines that have been added to the domain. the sid of all machines in the added domain cannot be repeated. what are the repeated situations? Oh, that's what I met. You can add a domain, but you cannot log on to the domain after adding a domain.
Solution
==========
Return domain.
Use the local administrator to log on.
Use a tool called newsid to generate a new random sid.
Restart.
Add domain.
Login successful.
This tool is no longer available for download by Microsoft.
References
====================
Http://geekswithblogs.net/mhamilton/archive/2005/05/01/38825.aspx
Http://blogs.technet.com/ B /markrussinovich/archive/2009/11/03/3291024.aspx
Http://technet.microsoft.com/en-us/sysinternals/bb897418.aspx