You can copy the files and start it up on a 2nd host machine, however if the
original instance is running you'll run into duplicate hostnames and ip
address issues initially. You can obviously change those once you start the
machine up and everything will appear to be working okay. The hidden issue
however is the VM's SIDS, those unique ids that differentiate the machine
from all the other machines in the domain. You can change the SIDS using
NewSID from SysInternals. I'd still recommend taking the VM out of the
domain and readding it after running NewSID.
A better solution in my opinion is to sysprep the original VM and then the
copies will change the SIDs when they start the first time, and join the
domain as well. I use "master" machines all the time to create new one, the
masters are syspreped and never get turned back on.
"sid" <sidwelle@xxxxxx> wrote in message
> If I join a domain from a virtual XP system, is the system portable ?
> Can I just copy the virt PC to another system with virtual PC running
> and create a new PC and point it to the copied files ? Does the
> virtual PC tie its self back to the host system some how ?