Partager via

Virtual Server Migration Toolkit (VSMT)

  • Article

For those interested in Virtual Server, the VSMT is a very useful free tool that allows you to Virtualise a Physical box. Here is an edited version of the QB article: https://support.microsoft.com/?kbid=555306&SD=tech by Guilherme Whitaker Carnevale MVP on the use of the VSMT.

For use Virtual Server Migration Toolkit, you need install the following components:

   - Virtual Server 2005
   - Automated Deployment Services - note this requires Windows Server 2003 Enterprise! and make sure you configure your IP addresses before installing ADS. If not follow the Article: https://support.microsoft.com/default.aspx?scid=kb;en-us;825039
   - DHCP Service configured - make sure you configure your DHCP server before you install ADS to allow for PXEBoot Extensions to be added to the server.
    
   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 : https://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
https://www.microsoft.com/windowsserversystem/virtualserver/overview/vsmtwhitepaper.mspx
 
VSMT FAQ
https://www.microsoft.com/windowsserversystem/virtualserver/evaluation/vsmtfaq.mspx

Comments

  • Anonymous
    January 01, 2003
    If you're using virtual server, or plan to use virtual server, and have physical machines you want to...

  • Anonymous
    January 01, 2003
    What you need
    Before you start get a copy of Windows 2003 Enterprise Edition&amp;nbsp;and the following...

  • Anonymous
    January 01, 2003
    If you're using virtual server, or plan to use virtual server, and have physical machines you want to...

  • Anonymous
    January 01, 2003
    I've had quite a few questions this morning on where to get my VSMT Console&amp;nbsp;tool, and how to build...

  • Anonymous
    January 01, 2003
    What you need
    Before you start get a copy of Windows 2003 Enterprise Edition&amp;nbsp;and the following...

  • Anonymous
    January 01, 2003
    I've had quite a few uestions this morning on where to get my VSMT Console&amp;nbsp;tool, and how to build...

  • Anonymous
    January 01, 2003
    PingBack from http://massimodn.wordpress.com/2007/04/17/consolidamento-server/

  • Anonymous
    January 01, 2003
    What you need
    Before you start get a copy of Windows 2003 Enterprise Edition&amp;nbsp;and the following...

  • Anonymous
    July 05, 2005
    I usually work the other way around, make a virtual server to proove that it works and then try to build it in real hardware. However I haven't heard of a tool yet to 'help' me do this gracefully.

  • Anonymous
    July 22, 2005
    ...and Bruce, how can you possibly forget my blogcast series demonstrating the whole sequence from start to end. I was shocked & stunned :-)

    Link is here http://blogs.technet.com/jhoward/archive/2005/01/04/346147.aspx

    Cheers,
    John.