Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I just don't know a better way to describe my issue that is driving me nuts. I am trying to establish a test domain with virtual machines on a box that has Win7 with VMwware workstation installed. The purpouse with this domain will be so that we can try and test different situations before they go into the production network.

I build a VM with WinSrv2008R2 and I am using that VM as a template to make other servers for the domain by making clones of it. Now I raise a DC with one clone and a member server with another clone - I add the server to the domain. I am following a standard procedure as always (it is not my first domain). Then I make an admin account and I am adding the admin to be a member of the Domain and Enterprise Admins group.

That admin is admin with full priviledges on the DC.. no problem there. But on the other server has ... somewhat half the privileges and I cant log in via RDP. I tryed with another account. Same issues.

For example (with half the privileges): I can't open the Even Viewer if I go via Start -> Administrative Tools -> Event Viewer. But I can open the Even Viewer via the server manager. You can notice this on the image below. I mean WTF???

enter image description here

I am going crazy, I haven't experienced anything similar in my three years of expertise. I already lost 3 days troubleshooting this. Could this be related with the cloning? Perhaps if I make fresh installs of WinSrv2008 there won't be any problems?

I've had raised test domains as VMs on other occasions before, and there weren't any problems then. This is VMware Workstation 8. I've made clones before, on Workstation 7 it didn't had any problems. Anyone has any ideas?


This is the info from the event log when I try to access via RDP:

An account failed to log on.

    Security ID:        NULL SID
    Account Name:       -
    Account Domain:     -
    Logon ID:       0x0

Logon Type:         3

Account For Which Logon Failed:
    Security ID:        NULL SID
    Account Name:       pat.coleman
    Account Domain:     lab

Failure Information:
    Failure Reason:     Domain sid inconsistent.
    Status:         0xc000006d
    Sub Status:     0xc000019b
share|improve this question
Did you run sysprep after you created the clones? – 1.618 Dec 13 '12 at 22:41
gonna try that now.. – Spirit Dec 13 '12 at 22:45
Im kinda wondered since I was doing cloning before in Workstation 7 and there was no problems there... – Spirit Dec 13 '12 at 22:51
@1.618 | You may want to add your comment into a answer and I will accept it. That worked for me, thanks buddy. :) – Spirit Dec 25 '12 at 10:52
up vote 2 down vote accepted

Run sysprep after you create the clones :)

share|improve this answer

When you promote a server to a Domain Controller and it is the first Domain Controller in the domain, the local machine SID is used in the creation of the domain SID. This is really the only time that the local machine SID matters. Since you don't seem to have run sysprep, the machine SID of the clone matches the domain SID of the domain - which causes the weird behavior that you're seeing.

Dismantle the domain and start from scratch, sysprepping each clone before dcpromoing and joining the member servers.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.