Hyper-V Ceate and Deploy Machine Templates (Without VMM)

KB ID 0001214 


Last week, myself and a few of my colleagues had to deploy a LOT of servers into Hyper-V. The client did not have System Center Virtual Machine Manager, so the process of creating and deploying a machine from a template is a little more convoluted


Here I’m deploying Windows Server 2012 Datacenter, but we repeated the process for Oracle Linux (Red Hat,) and, with the exception of sysprep, the process was the same. To start, build an ‘image machine‘ and ensure it is updated, and has on it any software you may require.

Update Windows Server

Keeping the Image For Future Updates?

If you intend to re-use this master image in the future, i.e. start it up install any outstanding updates, and then re-use it to deploy future virtual machines then BEFORE you sysprep it, take a ‘Checkpoint’. Then in future you can revert to this checkpoint and rerun sysprep again, this is because there is a three time limit on sysprep with the generalize option.

Checkpoint Windows VM

Run sys prep, it lives in;


Tick the ‘Generalise’ option, and set it to ‘Shutdown’.

Sysprep Windows Server

Create a folder to hold your template(s).

Hyper-V Templates Directory

Export your master VM into the templates directory you have just created.

Hyper-V Export VM

Hyper-V Deploying Machines From Template

Create a new virtual machine.

Hyper-V Create New VM

MAKE SURE: You select the option ‘attach a virtual disk later’, select all other options for the new VM as you require.

 Hyper-V No Disks

Within your template directory, create a copy of the hard drive and rename it so it has the same name as your newly deployed VM. 

Hyper-V Copy Disks

Then cut/paste this newly renamed drive into the folder for your new virtual machine.

Hyper-V Paste Virtual Disks

On your new VM > Settings > SCSI Controller > Hard Drive > Add.

Hyper-V Add Virtual Disk

Navigate to the hard drive file you copied and renamed > Apply > OK.

Hyper-V Import Virtual Disk

On the ‘Firmware’ tab move the new hard drive up, so it is at the top of the boot order.

Hyper-V Boot Order

You can now power on the new VM.

Related Articles, References, Credits, or External Links


Author: PeteLong

Share This Post On

Submit a Comment

Your email address will not be published. Required fields are marked *