vsmt

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:.xml ,

this will check for hardware compatibilities. You may get something like this after running

the hwvalidate:

Warning: A required patch file is missing. Refer

to thedocumentation for more info on how to

provide this file.File ntoskrnl.exeVersion 5.00.2195.7133

Language 1033Potential source of this

file is KB931784.

Look at each KB article that is listed and download the hotfix

for each one listed.

/x extract the hotfix to a directory with the same

name as the KB article so you can keep them in order.

C:\Program Files\Microsoft VSMT>vmpatch /s:"c:\program files\microsoft vsmt\patches\931784"

And repeat that for each KB article listed from the hwvalidate output

Once you finish running vmpatch for all the KB's then move onto the next step

Step 8: Execute the command:

vmscript /hwGenerateP2V /hwInfoFile:.xml /name: /vmConfigPath:\vmconfig /virtualDiskPath:d:\vmdisk /hwDestVS: /virtualDiskDynamic /vmMemory:256

Here is the command that I ran:

C:\Program Files\Microsoft VSMT>vmscript /P2V /hwInfoFile:"C:\Program Files\Microsoft VSMT\test.xml" /name:testvm /vmConfigPath:"C:\Program Files\Microsoft VSMT\vmconfig" /virtualDiskPath:"E:\Virtual Machines\testvm" /hwDestVS:vmh01 /virtualDiskDynamic /vmMemory:256

The source and destination settings in this command need to be the same, so if you are converting test the destination has to be test not testvmOtherwise it writes the scripts and see's the target to try to convert as testvm which is actually the destination Target and destination have to be the same.

Here is the corrected command line

C:\Program Files\Microsoft VSMT>vmscript /P2V /hwInfoFile:"C:\Program Files\Microsoft VSMT\test.xml" /name:test /vmConfigPath:"C:\Program Files\Microsoft VSMT\vmconfig" /virtualDiskPath:"E:\Virtual Machines\test" /hwDestVS:vmh01 /virtualDiskDynamic /vmMemory:256

You may have to create the vmconfig directory under the microsoft vsmt directory because its not there by default

After running the command the vmconfig directory is empty but it did dump all the files into the Writing output to: C:\Program Files\Microsoft VSMT\P2V\ directory (????)

Step 9: At this point all scripts were 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:\\p2v\\_Capture.cmd Reboot your guest machine using PXE.

Here is the correct file pathC:\Program Files\Microsoft VSMT\p2v\test\test_capture.cmd

After running the capture cmd file I get this outputC:\Program Files\Microsoft VSMT\p2v\test>test_capture.cmdCheck for existing images

'adsimage' is not recognized as an internal or external command,operable program or batch file.

After getting this error message I copied the C:\Program Files\Microsoft ADS\tools directory directly into the C:\Program Files\Microsoft VSMT\p2v\test directory and the command started working

Had to do a few things to get PXE to work

-added the "option 60" to DHCP options on the DHCP server Using this command 'netsh dhcp server add optiondef 60 "Class ID" STRING' Then went into the option and added PXEClient as the string within the DHCP console Tried to get the target machine on the same subnet but still would not PXE boot

Went back into the OS and checked connectivity and it was OK Moved the cable to a different NIC NIC#2(??) and rebooted in PXE

It failed on the first nic then the second one picked up and it booted in PXE and got an IP address

Now when I reboot the server in PXE boot it gives this error "Windows could not start due to an error while booting from a RAMDISK"

Need to prepopulate the C:\Program Files\Microsoft ADS\nbs\repository\User\PreSystemDirectory with the Network and Mass Storage controller drivers located on systemstart CD

Downloaded the drivers for the correct NIC and for the array controllerTried the SNAP again and it failed

Installing hotfixes

Changed INF file for the NIC cardDropped the INF into the presystem folder

When ADS finish the capture process, the server will shutdown guest machine.

It worked!

Step 10: This step will create configuration file in Virtual Server 2005 machine. C:\\p2v\\_CreateVM.cmd

C:\Program Files\Microsoft VSMT\p2v\test>test_createvm.cmdCreate Virtual Machine: test on vmh01Executing VMClient on remote machine: vmh01===>Remote job output:47VSMT Installed on: "C:\Program Files\Microsoft VSMT\"executing: "C:\Program Files\Microsoft VSMT\"vmclient.exe -nologo:True -nodebug:True -name:"test" -vmCreate:True -vmConfigPath:"C:\Program Files\Microsoft VSMT\vmconfig" -vmMemory:"256"CreateVirtualMachine:test with memory:256MBName: testStatus: SavedGUID: {748B53BA-4CA8-4BD5-8168-7A4E6DF65383}Memory: 256 MBMAC[0]: 00-03-FF-DE-14-FFVMClient.exe returned 0

<===Remote job outputRemove all NICs so as to start with no nicsExecuting VMClient on remote machine: vmh01===>Remote job output:48VSMT Installed on: "C:\Program Files\Microsoft VSMT\"executing: "C:\Program Files\Microsoft VSMT\"vmclient.exe -nologo:True -nodebug:True -name:"test" -removeVirtualNic:True -mac:"00-00-00-00-00-00"Removing Nic from testRemoving NIC 000000000000VMClient.exe returned 0

<===Remote job outputAdding Network Card with MAC:00080225364F. Corresponding source device MAC:00080225364FExecuting VMClient on remote machine: vmh01===>Remote job output:49VSMT Installed on: "C:\Program Files\Microsoft VSMT\"executing: "C:\Program Files\Microsoft VSMT\"vmclient.exe -nologo:True -nodebug:True -name:"test" -addVirtualNic:True -mac:"00080225364F" -hostNetwork:"VM0"Adding Nic to testAdding NIC 00-08-02-25-36-4FVMClient.exe returned 0

<===Remote job outputinsert Ris floppyExecuting VMClient on remote machine: vmh01===>Remote job output:50VSMT Installed on: "C:\Program Files\Microsoft VSMT\"executing: "C:\Program Files\Microsoft VSMT\"vmclient.exe -nologo:True -nodebug:True -name:"test" -floppy:True -floppyImage:"ris2003.vfd"Set floppy for VM test to ris2003.vfdAttaching floppy ris2003.vfdVMClient.exe returned 0

<===Remote job outputAdd SCSI controller 1/1Executing VMClient on remote machine: vmh01===>Remote job output:51VSMT Installed on: "C:\Program Files\Microsoft VSMT\"executing: "C:\Program Files\Microsoft VSMT\"vmclient.exe -nologo:True -nodebug:True -name:"test" -addSCSI:TrueAdding SCSI to testVMClient.exe returned 0

<===Remote job outputCreate disk:0 with size:34760MBCreating Virtual Disk E:\Virtual Machines\test\test_disk_1.vhd:34760MBsNote: This operation may take a couple of minutes depending on thesize of the virtual disk being created. ===>Remote job output:52VSMT Installed on: "C:\Program Files\Microsoft VSMT\"executing: "C:\Program Files\Microsoft VSMT\"vmclient.exe -CreateVirtualDisk -VirtualDiskSize:34760 -VirtualDiskPath:"E:\Virtual Machines\test\test_disk_1.vhd" -virtualDiskDynamicMicrosoft (R) Virtual Server Migration Toolkit - VmClient Tool ver.5.2.5149.0Copyright (C) 2004 Microsoft Corporation. All rights reserved.

Creating Virtual Disk E:\Virtual Machines\test\test_disk_1.vhd:34760MBsNote: This operation may take a couple of minutes depending on thesize of the virtual disk being created.

Error: Directory does not exist E:\Virtual Machines\testError: Result Code: 2VMClient.exe returned 2

<===Remote job outputError: Result Code: 8Error occured, Cleaning up.:(8)release control of device testADSDevice: Warning: Device test did not match any devicesADSDevice: Error: The device does not exist.remove device testADSDevice: Warning: Device test did not match any devicesADSDevice: Error: The device does not exist.Delete Virtual Machine:test on vmh01 Created directory test on e:\virtual machines\ That worked!The target directory has to be there in order for it to create the VM's Step 11: This step will power on the virtual machine, connect to ADS and deploy the image created in step 9. C:\\p2v\\_DeployVM.cmd

In the job detail within ADS it looks like the job stalls at "deploy image" but it really just doesn't refresh. If you look at the file size of the VHD that its deploying to its actually growing so it is deploying.

Also there is nothing on the screen of the VM that indicates its actually doing anything, but just be patient.

Got errors trying to deploy the image to the VM