Microsoft Hyper-V, creating new VM's based on exisiting 'template' images.

I have just started using Hyper-V, so need some pointers guys.  I have created two VM's one based on Windows Server 2003 (X86) and the other Server 2008 (X64).  I'd like to keep them as 'templates' to create new Server OS's from, can I do that rather than setting them up from scratch every time using DVD's / ISO's etc?  Will I run into a problem with SID's etc as they will be based on these template images?  Thanks in advance.
Who is Participating?
Andrew Hancock (VMware vExpert / EE MVE^2)Connect With a Mentor VMware and Virtualization ConsultantCommented:
The machine names and SIDs will be the same. Microsoft's official solution to dealing with this problem is sysprep. Using sysprep you can both rename a machine and provide it a unique SID.

Generally a master image that is used to generate mulitple unique copies of itself works just fine. But there are certain applications that do not tolerate a machine rename.

So the answer is to sysprep.
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
The best way to do this is to use System Center Virtual Machine Manager.

Are you using this?
The only way really is to create a sysprep image and deploy from ghost or WDS.
Maybe me being picky but I always prefer installing a server from scratch using the DVD - less margin for error!
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

-Juddy-Author Commented:
I am not.  Is this part of MS System Centre Manager?
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Yes. In that case, continue as you are but don't forget to Sysprep.
-Juddy-Author Commented:
So the best, safest way is to create a new VM every time from scratch or is Sysprep as good as doing this?
storkyIVConnect With a Mentor Commented:
Windows deployment services maybe another option:
kevinhsiehConnect With a Mentor Commented:
Duplicate SIDs actually isn't a problem and Microsoft has pulled NewSID. Sysprep is still "required". The except below is from a post by Mark Russinovich who knows more about the internal workings of Windows than basically anybody, including the developers.

"I realize that the news that it’s okay to have duplicate machine SIDs comes as a surprise to many, especially since changing SIDs on imaged systems has been a fundamental principle of image deployment since Windows NT’s inception. This blog post debunks the myth with facts by first describing the machine SID, explaining how Windows uses SIDs, and then showing that - with one exception - Windows never exposes a machine SID outside its computer, proving that it’s okay to have systems with the same machine SID. Note that Sysprep resets other machine-specific state that, if duplicated, can cause problems for certain applications like Windows Server Update Services (WSUS), so Microsoft's support policy will still require cloned systems to be made unique with Sysprep."
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.