VM Question

[Chiefcrowe]

Is there a way to do this, is it even possible? I would like to be able to make a copy of a web server and convert it to a VM in hyperV, and then use it for development work.

 

[IndyColtsFan]

Definitely possible with VMWare using vConverter and I would be completely and totally shocked if HyperV didn't have a cheap/free tool as well. Just Google P2V and HyperV.

EDIT: Here are a few links:

http://technet.microsoft.com/en-us/library/cc764232.aspx

http://technet.microsoft.com/en-us/library/cc917882.aspx

http://technet.microsoft.com/en-us/sysinternals/ee656415.aspx

http://williamfaulkner.co.uk/2009/01/easy-physical-to-virtual-p2v-for-hyper-v/

 

[classy]

Definitely possible with VMWare using vConverter and I would be completely and totally shocked if HyperV didn't have a cheap/free tool as well. Just Google P2V and HyperV.

EDIT: Here are a few links:

http://technet.microsoft.com/en-us/library/cc764232.aspx

http://technet.microsoft.com/en-us/library/cc917882.aspx

http://technet.microsoft.com/en-us/sysinternals/ee656415.aspx

http://williamfaulkner.co.uk/2009/01/easy-physical-to-virtual-p2v-for-hyper-v/

Yea thats pretty easy. The convertor will do all the work. Just remember once you start the vm take the physical machine off the network.

 

[yinan]

Another issue that could complicate this for you is that if the VM requires access to domain services you will have to clone those VMs as well because you cannot have 2 servers with the same name, ip etc on the network at once so you will need clones of those other servers as well.

 

[quikah]

Another issue that could complicate this for you is that if the VM requires access to domain services you will have to clone those VMs as well because you cannot have 2 servers with the same name, ip etc on the network at once so you will need clones of those other servers as well.

You can change the IP and name of the VM...

 

[IndyColtsFan]

You can change the IP and name of the VM...

If it is a member of a Windows domain, that isn't enough. The SIDs would be the same as other systems in the domain and that could cause lots of problems. You could try sysprepping it prior to placing it on the production network, but that might cause some IIS issues and therefore, would affect his app.

 

[dawks]

If it is a member of a Windows domain, that isn't enough. The SIDs would be the same as other systems in the domain and that could cause lots of problems. You could try sysprepping it prior to placing it on the production network, but that might cause some IIS issues and therefore, would affect his app.

Assuming its actually a Windows OS AND on a domain, yea. Actually you're best bet would be to remove it from the domain, do the conversion, start up the converted VM, change the name and IP, then start up the original, and add it back to the domain. Well, might be a big issue with permissions and such then. Not an easy call if its a domain server I guess.

Do permissions get all screwed up if a server is removed from the domain and added back?

If you try to remove the new VM server from the domain, or rename it, that would screw up the original servers domain account and really BORK things.

 

[stash]

The SIDs would be the same as other systems in the domain and that could cause lots of problems

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