Networknet archive Blog

Windows Server 2003: Domain logon failure after cloning VMs

Originally published 4 comments

By Ivan Versluis

Today I built a VMware team containing a domain controller and a file server from my Windows Server 2003 Enterprise Edition R2 master image. Both images ran sysprep.exe. I configured Active Directory and DNS on the domain controller, then joined the second guest to the domain successfully.

After restarting, I tried signing in with a domain account and then with the domain administrator account. Both produced this logon message:

The system cannot log you on due the following error:

The name or security ID (SID) of the domain specified is inconsistent with the trust information for that domain.

Please try again or consult your system administrator.

clip_image001

I signed in with the local administrator account and found the Netlogon error with event ID 5516 shown below.

clip_image002

For some reason, sysprep had not worked on my master image, and both virtual guests had the same SID.

Compare the SIDs

Download psgetsid.exe from Microsoft to check both SIDs.

http://www.microsoft.com/technet/sysinternals/utilities/psgetsid.mspx

I downloaded pstools.zip from Microsoft and ran psgetsid.exe \\fs-001-cert and psgetsid.exe \\dc-001-cert. As shown below, both SIDs match.

clip_image003

Generate a new SID

The quick way to resolve this issue is to run NewSid.exe and generate a new SID for this computer account.

Download NewSid from Microsoft.

Run the tool and generate a new SID for the guest machine.

clip_image004

Click Next.

clip_image005

Click Next.

clip_image006

Click Next and restart the machine.

Rejoin the domain

  1. Sign in with the local administrator account and join a workgroup.
  2. Restart the guest and rejoin the domain.

If these steps are not completed, domain membership connectivity will fail.

clip_image007

After restarting, I successfully signed in as my test user, "Finance Manager".

3 comments

Comments from the original WordPress site, kept read-only.

  1. Neeraj Malhotra

    It was really a fantastic solution. I got this problem during microsoft sharepoint2007 configuration on vitual 2k3 server and now it has been resolved. Really thanks.

  2. Shelly

    The problem with the SID also appeared when I restored a Snapshot of a virtual machine.
    Thank you for this solution, it really helped.

1 mention