Do I need to use Sysprep to clone VMs on my personal lab?

i’m programmer , i’m trying build personal lab. have machine hyper-v standalone server 2012 r2 installed. need create vms used testing applications, creating small virtual networks learning networking basics , other learning purpose. none of these vms gonna exist long, deleting them purpose served , i’m gonna create new ones.

so, need cloning-type feature available on vmware. i’m aware of export-import feature available on hyper-v. i'm confused sysprep tool, found articles saying tool prepare vhd used new vms, , assigns new sid, mac, guid etc new cloned vm doesn’t conflict existing ones.

i’d know –

1. what difference between using export-import , using sysprep? if use export-import feature, still need sysprep guest? sysprep does?
   
2. for scenario need use sysprep?
3. what best procedure (steps) create template vm scenario?

tim's procedure common , not hard understand once you've done few times. simplest version, follow in lab, create 1 virtual machine obvious name, "windows 8.1 template". install os want clone. then, within guest operating system, sysprep (c:\windows\system32\sysprep\sysprep.exe /oobe /shutdown /generalize /mode:vm). once that's done, typically copy vhdx file safe location , delete source virtual machine.

to use vhdx, create new virtual machine scratch without virtual hard disk. make copy of source vhdx file, rename match new virtual machine, , attach copy new vm. basic point here that, after sysprep, never ever use first vhdx virtual machine directly. use copies of it. other thing doesn't involve import/export utilities @ all. imo, more useful virtual machine portability , sharing cloning controlled image.

what tim talking injecting can mount vhdx file in windows 8 , later or windows server 2012 , later , work local hard drive. if you're using gui, it's right there on right-click context menu vhdx file. so, might create "software" folder @ root of disk , place install files in want available clones. you can run windows update against source vhdx without mounting it.

to answer initial question, biggest difference between sysprep , export/import virtual machine has absolutely no idea it's gone through export/import cycle. entire processes 100% managed hyper-v , guest operating system isn't involved. if original vm , copy brought online together, collide. syspreped operating system (with suggested switches) believes new install , potentially colliding components , settings windows aware of changed. can sysprep image, clone it, , bring both online without windows issues.

---

eric siron
altaro hyper-v blog
independent blog contributor, not altaro employee. solely responsible content of posts.

Windows Server  >  Hyper-V