DetailPage-MSS-KB

Microsoft small business knowledge base

Article ID: 555306 - Last Review: April 29, 2005 - Revision: 1.0

Author: Guilherme Whitaker Carnevale MVP
 

SUMMARY

This article have the steps for use of Virtual Server Migration toolkit. This will help you migrate your "real systems" to virtual machines, using Microsoft Virtual Server 2005.

MORE INFORMATION

For use Virtual Server Migration Toolkit, you need install the following components:
   - Automated Deployment Services 
   - DHCP Service configured
   
   Supported Guest OS :
   • Windows NT 4.0 Server with Service Pack (SP) 6a, Standard and Enterprise Editions
   • Windows 2000 Server SP 4 or later
   • Windows 2000 Advanced Server SP 4 or later
   • Windows Server 2003, Standard Edition and Enterprise Edition
  
  You can get the Virtual Server Migration toolkit at : http://www.microsoft.com/windowsserversystem/virtualserver/evaluation/vsmt.mspx
 
Step1 :
       Install Microsoft Virtual Server 2005.
 
Step2 :
       Install Automated Deployment Services in the same or different machine then Virtual Server 2005.
 
Step3 :
       Install Virtual Server Migration Toolkit.
 
Step4 :
       If you install the ADS on the same machine of DHCP Server you need configure ADS with this command:
           C:\Program Files\Microsoft ADS\bin\ADSdhcpconfig.wsf /add
 
Step 5 :
      On samples directory of you VSMT installation, execute the script CreateVirtualNetwork.vbs, to create VM0 network definition in your Virtual Server 2005.
 
All the executables below are in your VSMT installation directory:
Step 6 :
      Execute the command:  gatherhw.exe  on the machine that you will migrate, this command will generate one XML that will be used by VSMT; send the file to VSMT directory.
 
Step 7:
     Execute the command:  VMScript.exe /hwvalidate /hwinfofile:<Guest Server>.xml  , this will check for hardware compatibilities.
 
     If some incompatibility was found at this point, unfortunately you cannot continue.
 
Step 8:
     Execute the command:                 
    vmscript /hwGenerateP2V /hwInfoFile:<GuestMachine>.xml /name:<VirtualMachineName> /vmConfigPath:<Your VSMT Directory>\vmconfig
   /virtualDiskPath:d:\vmdisk /hwDestVS:<YourVSMcahine> /virtualDiskDynamic /vmMemory:256
 
Step 9:
    At this point all scripts was generated and we can start the migration process. You need check if your guest machine have support for PXE boot on the network card, if not, you can generate one RIS disk to try the boot.
    On VSMT server, start the command:
    C:\<VMST Directory>\p2v\<GuestMachine>\<GuestMachine>_Capture.cmd 
    Reboot your guest machine using PXE.
 
    When ADS finish the capture process, the server will shutdown guest machine.

Step 10:
    This step will create configuration file in Virtual Server 2005 machine.
    C:\<VSMT Directory>\p2v\<GuestMachinet>\<GuestMachine>_CreateVM.cmd
 
Step 11:
    This step will power on the virtual machine, connect to ADS and deploy the image created in step 9.
    C:\<VSMT Directory>\p2v\<GuestMachine>\<GuestMachine>_DeployVM.cmd
 
    After this step the migration is finished, you will have your "real machine" virtualized.
 
If some errors occur, is recommended restart the migration process using the command:
    C:\<VSMT Directory>\p2v\<GuestMachine>\<GuestMachine>_cleanupVM.cmd , run this command and back to step 9.
 
Additional References:
 
WHITE PAPER VSMT
http://www.microsoft.com/windowsserversystem/virtualserver/overview/vsmtwhitepaper.mspx
 
VSMT FAQ
http://www.microsoft.com/windowsserversystem/virtualserver/evaluation/vsmtfaq.mspx
 
 

APPLIES TO
  • Microsoft Virtual PC 2004
Keywords: 
kbpubmvp kbpubtypecca kbhowto KB555306
Community Solutions ContentCOMMUNITY SOLUTIONS CONTENT DISCLAIMER
MICROSOFT CORPORATION AND/OR ITS RESPECTIVE SUPPLIERS MAKE NO REPRESENTATIONS ABOUT THE SUITABILITY, RELIABILITY, OR ACCURACY OF THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN. ALL SUCH INFORMATION AND RELATED GRAPHICS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT AND/OR ITS RESPECTIVE SUPPLIERS HEREBY DISCLAIM ALL WARRANTIES AND CONDITIONS WITH REGARD TO THIS INFORMATION AND RELATED GRAPHICS, INCLUDING ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, WORKMANLIKE EFFORT, TITLE AND NON-INFRINGEMENT. YOU SPECIFICALLY AGREE THAT IN NO EVENT SHALL MICROSOFT AND/OR ITS SUPPLIERS BE LIABLE FOR ANY DIRECT, INDIRECT, PUNITIVE, INCIDENTAL, SPECIAL, CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF USE, DATA OR PROFITS, ARISING OUT OF OR IN ANY WAY CONNECTED WITH THE USE OF OR INABILITY TO USE THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN, WHETHER BASED ON CONTRACT, TORT, NEGLIGENCE, STRICT LIABILITY OR OTHERWISE, EVEN IF MICROSOFT OR ANY OF ITS SUPPLIERS HAS BEEN ADVISED OF THE POSSIBILITY OF DAMAGES.
Share
Additional support options
Ask The Microsoft Small Business Support Community
Contact Microsoft Small Business Support
Find Microsoft Small Business Support Certified Partner
Find a Microsoft Store For In-Person Small Business Support