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: http://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: http://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 : http://www.microsoft.com/windowsserversystem/virtualserver/evaluation/vsmt.mspx
Install Microsoft Virtual Server 2005.
Install Automated Deployment Services in the same or different machine then Virtual Server 2005.
Install Virtual Server Migration Toolkit.
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.
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.
Execute the command:
vmscript /hwGenerateP2V /hwInfoFile:<GuestMachine>.xml /name:<VirtualMachineName> /vmConfigPath:<Your VSMT Directory>\vmconfig
/virtualDiskPath:d:\vmdisk /hwDestVS:<YourVSMcahine> /virtualDiskDynamic /vmMemory:256
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:
Reboot your guest machine using PXE.
When ADS finish the capture process, the server will shutdown guest machine.
This step will create configuration file in Virtual Server 2005 machine.
This step will power on the virtual machine, connect to ADS and deploy the image created in step 9.
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.
WHITE PAPER VSMT