• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Hyper-V: How to "clone" a VM?

Master_Pain

Master_Pain

Supreme [H]ardness
Joined
Apr 13, 2007
Messages
4,958
Extremely new to Hyper-V and I have to clone a VM in the morning.

Here is what I have (Windows VMs):
VM to be cloned (2 VHDs)
VM to be overwritten

Here's how I understand the cloning process:
1. Shut down both VMs.
2. Export both of the VHDs from the first VM.
3. Go into the second's settings and point the two drives to the exported VHDs.
4. Start both VMs back up, test.

Does that process seem correct?

Sidenote, I know snapshots and the VMs being on a domain would mess with this, but neither apply in this situation.
 
If you're running Hyper-V 2012 R2 you should be able to export the VM even while it's running. You can also use the Export-VM commandlet in Powershell to do this.
 
You don't need a VM to be overwritten. You can export the VM, then start it back up. Then import that image as a new VM with a new machine config ID (this will be one of the options during import).

You really should sysprep the machine first though, but since it's not in a domain, duplicate SIDs shouldn't be a problem.
 
We do a P2V even when cloning other Virtuals in our 2008 environment. It works well when updating our Dev environment for the purpose of testing SharePoint stuff.
 
You must log in or register to reply here.
Back
Top