?
Solved

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

Posted on 2011-02-16
8
Medium Priority
?
840 Views
Last Modified: 2012-06-27
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.
0
Comment
Question by:-Juddy-
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
  • 2
  • +1
8 Comments
 
LVL 122

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 668 total points
ID: 34905447
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.
0
 
LVL 122
ID: 34905451
The best way to do this is to use System Center Virtual Machine Manager.

Are you using this?
0
 
LVL 2

Expert Comment

by:storkyIV
ID: 34905456
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!
0
Use Case: Protecting a Hybrid Cloud Infrastructure

Microsoft Azure is rapidly becoming the norm in dynamic IT environments. This document describes the challenges that organizations face when protecting data in a hybrid cloud IT environment and presents a use case to demonstrate how Acronis Backup protects all data.

 
LVL 3

Author Comment

by:-Juddy-
ID: 34905458
I am not.  Is this part of MS System Centre Manager?
0
 
LVL 122
ID: 34905471
Yes. In that case, continue as you are but don't forget to Sysprep.
0
 
LVL 3

Author Comment

by:-Juddy-
ID: 34905483
So the best, safest way is to create a new VM every time from scratch or is Sysprep as good as doing this?
0
 
LVL 2

Assisted Solution

by:storkyIV
storkyIV earned 668 total points
ID: 34905485
Windows deployment services maybe another option:

http://technet.microsoft.com/en-us/library/cc771670%28WS.10%29.aspx
0
 
LVL 42

Assisted Solution

by:kevinhsieh
kevinhsieh earned 664 total points
ID: 34912062
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.

http://blogs.technet.com/b/markrussinovich/archive/2009/11/03/3291024.aspx

"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."
0

Featured Post

Veeam Task Manager for Hyper-V

Task Manager for Hyper-V provides critical information that allows you to monitor Hyper-V performance by displaying real-time views of CPU and memory at the individual VM-level, so you can quickly identify which VMs are using host resources.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

If your vDisk VHD file gets deleted from the image store accidentally or on purpose, you won't be able to remove the vDisk from the PVS console. There is a known workaround that is solid.
A look into Log Analysis and Effective Critical Alerting.
This tutorial will show how to push an installation of Backup Exec to an additional server in both 2012 and 2014 versions of the software. Click on the Backup Exec button in the upper left corner. From here, select Installation and Licensing, then I…
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
Suggested Courses

777 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question