Wednesday, September 9, 2015

How to prepare a VM with Sysprep before converting it to Template

During VM deployment I saw it many times where people don't run VM customization wizard during deployment and later faces duplicate SID issues.

To ensure not to face duplicate SID issue, its better to prepare the OS using Sysprep before converting it to Template.

Prior to converting a VM to Template, just remember to use Sysprep as follows,
  • Run Sysprep, C:\Windows\System32\Sysprep\Sysprep.exe
  • Ensure ‘System Out-of-Box Experience (OOBE)’ is selected  and Tick the ‘Generalize’ option and Select ‘Shutdown’ from the Shutdown Options. 

(You can do the same in one go using this command "C:\Windows\System32\sysprep\sysprep /oobe /generalize /shutdown")
Once the machine has shutdown, convert it to Template/Image or Clone and you are good to go!

This will trigger sysprep procces inside newly deployed VM after its first Power On.

Note: Yes during VM deployment, Sysprep will come to the picture right at the VM deployment phase where you have 3 options: 

  • Do not customize
  • Customize using the Customization Wizard 
  • Customize using an existing customization specification 
If you had already prepared the template VM with Sysprep the you can choose Do not customize  here.

You may take a look here for related post : how-to-fix-issue-of-duplicate-sid

That's it.... :)


  1. Running sysprep is very much required why building new VM. Its basically a first step. I'm surprising why its not been following as a practice.

    1. yes i agree, btw I have seen when customization wizard was failing to successfully apply Sysprep to Windows 2008/2012 its better to prepare the VM with Sysprep in way, it would be the first thing that will automatically run when you first time power on a newly deployed VM.