Virtual-to-physical migrations with Microsoft Virtual Server

Virtual-to-physical migrations with Microsoft Virtual Server

I am trying to find a step by step process to copy and use a virtual machine onto another machine. The copy will not be used concurrently with the original machine. The intent is to copy the virtual machine to a different server. I think I can skip the SID changes. I am new to Microsoft Virtual Server and am under a tight time line. I don't understand the exact procedure. What needs to be installed on the machine that receives the copy of the VHD? What else needs to be done?

    Requires Free Membership to View

    Login

    When you register, my team of editors will also send you the latest expert resources covering all areas of server virtualization, such as platforms, architectures and strategies, server hardware, managing virtual environments, application issues and more.

    Margie Semilof, Editorial Director

    By submitting your registration information to SearchServerVirtualization.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchServerVirtualization.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

When you're copying a virtual machine to another computer, you generally just need to move the virtual hard disk (.VHD) file. The other computer will need to be running Microsoft Virtual Server, of course, but you can usually recreate the virtual machine's settings on the new installation of Virtual Server without too much difficulty.

Other than that, you need to make sure that the virtual machine being copied has been shut down completely before you attempt to copy its .VHD file(s), or the copy will be in an inconsistent state when it's started up.

If the two copies are not running at the same time, and never will be, then SID issues should not be a problem.

This was first published in October 2007

Back to top