Can't Login to VM after cloning it

[russcky]

We are trying to run 3 or 4 VM's on our Mac Pro for development testing and such.

To do this we setup one VM with Win2003 Ent. Server, installed all our apps.
This VM (called Master VM) could be logged into on our domain just fine. It can see
the network and other computers on the network.

We then stopped this VM and created a 'Clone' from the Parallels menu. This new clone
starts up fine and can login to the network fine too.

What's interesting is that the original (Master VM) can't login (authenticate against our domain server) any longer. It can't authenticate even if the clone isn't running.

We have tried this process twice to make sure we were doing everything correctly and it keeps happening.

Is there something we are forgetting to do after cloning?
Why would the original stop working after a clone is made of it?

Anyone else running multiple VM's at the same time?

 

[ivel]

Isn't this a limitation of AD? You have just created 2 machines with the same SID and your authentication is confused. You should try to clone machines before adding them to a domain or run sysprep before cloning. There is lots of documentation about this regarding any type of hardware cloning such as Ghosting.