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

With VMWare server 1.x.x on a Linux host, whenever I move a particular Windows 2003 Server VM, I always have to remove it from the Domain, reboot, rejoin to the domain, reboot.

When I used to move it, I was always asked if I want to keep the ID, but it doesn't ask that anymore. My first guess is that this is the problem, because someone might have clicked 'always create new'. Does anyone know where that setting is kept? Or if this isn't the problem, what the problem might be?

share|improve this question
What kind of errors happen in the Windows Server member when you move it around? David Spillett is correct-- the VM ID doesn't affect anything re: the Windows domain. You're only moving the VM and not rolling-back to an older snapshot-- correct? – Evan Anderson Jul 24 '09 at 14:29
I just get the generic 'Can not log into the domain because it is not available error.' Sorry, don't have the exact error anymore. – Kyle Brandt Jul 24 '09 at 14:43
Oh crap, actually in this case I am rolling back, because I was bring up an older copy. – Kyle Brandt Jul 24 '09 at 14:44
up vote 1 down vote accepted

That's a very common problem with VMs that time travel (roll back a snapshot), I have a GPO object that fixes this that I drop into each OU where there are VMs present.

This MS KB article explains what's going on: Effects of machine account replication on a domain

Here's a link to how to create the GPO object I mentioned and here's another with some extra options for you to think about...

share|improve this answer

The only difference that the ID should make that Windows might notice, as far as I remember, is that it is used in generating the network adaptor's MAC address. I don't think this information is used when identifying machines in Windows domains.

I've not moved around any VMWare VMs on our current AD domain, but I had a lot of similar problems when rolling-back-to-snapshot VMs that were on our old NT based domain. If they stopped being able to authenticate with the domain after the rollback (it didn't always happen) I usually had to manually remove the server entry on the domain controller (this wasn't removed when dropping the VM off the domain from the machine itself) before being able to rejoin the machine.

share|improve this answer
Your problem w/ your NT domain and "rolling back" was probably the result of the regular domain member trust password rotation. That can be disabled in Active Directory domains. – Evan Anderson Jul 24 '09 at 14:26
Evan, sounds like it, can explain that a little more? – Kyle Brandt Jul 24 '09 at 15:09

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.