You are now ready to perform the P2V migration.
Steps covered in this section:
Convert the physical server 65
You can now perform a physical-to-virtual (P2V) migration of the server that represents your production workload.
Run the virtual machine 78
In this section, you start the virtual machine and load VM Additions from an ISO file.

Convert the physical server
1. On DC_SRV, open the Virtual Machine Manager Console.
2. Click Convert Physical Server from the Actions pane on the right side.
3. In the Select Source page, type the computer name and administrative account information, and then click Next. To follow along in this test scenario, type member_srv1 for the computer name and contoso\administrator for the account name. You will need to enter and confirm the password you created when you installed the operating system on member_srv1.

Figure 57 Select Source page
4. On the Virtual Machine Identity page, leave the default virtual machine name, in this case member_srv1, and the default owner, in this case CONTOSO\Administrator. Click Next.

Figure 58 Virtual Machine Identity page
5. On the Gather Information page, click Gather System Information. In order to perform the P2V conversion, SCVMM installs software on the source machine, the server that will be converted, in order to gather necessary information. In this test scenario, the source machine is member_srv1. The software is removed when the conversion is complete.

Figure 59 Gather Information page
6. Once the wizard has gathered the necessary system information, click Next. The system information gathered will be shown in the System Information tile.

Figure 60 Gather System Information results

7. On the Conversion Information page, review the list of files required for the P2V conversion of the server. The files listed will depend on how recently the server has been patched. The files indicated must be copied, and the Convert Physical Server Wizard must then be run again. Click Cancel, and the click Yes when asked for confirmation to exit the wizard.
Note: Even if you have recently updated your servers with the required patches, you will need to go through the following steps.

Figure 61 Conversion Information page
8. If you are performing a Windows Server 2003 conversion, you can copy the required .cab files into the Driver Cache folder. This will only need to be done the first time you are performing a P2V migration. Perform the following steps on the DC_SRV server:
a. To copy the necessary files, click Start > Run, and then type \\member_srv1\c$ and click OK. Note that administrative share access must be enabled.
b. Open the Windows folder on member_srv1, open the Driver Cache folder, and then open the i386 folder. This is where the required files are located.
c. Select the files driver.cab, sp1.cab, and sp2.cab, and the press Ctrl+C.
d. On the local host, in this case, DC_SRV, browse to C:\Program Files\Microsoft System Center Virtual Machine Manager 2007\P2V Patch Import, and then press Ctrl+V. This pastes the files in the appropriate folder.
9. If you are performing a Windows 2000 Server SP4 conversion, you can copy the required files into the P2V Patch Import folder. Download the required packages indicated on the Conversion Information page from the Microsoft Web site. The packages will need to be renamed, and possibly extracted:
a. On physical server DC_SRV, right-click and rename the packages so that SCVMM can recognize them. For example, Windows2000-KB935839-x86-ENU.EXE becomes KB935839.EXE. Copy the renamed packages into the folder C:\Program Files\Microsoft System Center Virtual Machine Manager 2007\P2V Patch Import.
b. If SCVMM still reports that the package is missing, on server DC_SRV, extract the files using Windows2000-KB935839-x86-ENU.EXE/extract. You will be prompted to browse to a folder in which to place the updated files. On the local host, in this case DC_SRV, create a new folder in the P2V Patch Import folder and name it based on the KB number of the package. For the example above, name the folder C:\program files\Microsoft System Center Virtual Machine Manager\P2V Patch Import\KB935839\. Extract the required files into this folder on DC_SRV, and continue.
Note: For a Windows 2000 Server P2V conversion, you must install the Windows Automated Installation Kit (Windows AIK) on the physical server representing the workload (in this case, DC_SRV). Windows AIK can be downloaded from: www.microsoft.com/downloads/details.aspx?familyid=C7D4BC6D-15F3-4284-9123-679830D629F2&displaylang=en. Installation instructions are provided in the download center. Windows AIK allows the SCVMM Server to boot the server running Windows 2000 Server into a pre-installation environment so that it can copy the hard drive and proceed with the P2V migration. No configuration is necessary. Though not prompted to do so, you will need to restart the computer after the installation completes.
10. Return to the Virtual Machine Manager Console on physical server DC_SRV. We will now run the Convert Physical Server Wizard again.
11. Click Convert Physical Server from the Actions pane on the right side.
12. Enter the computer name and administrative account information in the source window, and then click Next. Again, type member_srv1 for the computer name and contoso\administrator for the account name in order to follow along in this test scenario.
13. Leave the default virtual machine name and default owner. Again, the virtual machine name in this case is member_srv1 and the default owner is CONTOSO\Administrator. Click Next.
14. Click Gather System Information.
15. Once the wizard has gathered the system information, click Next.
16. Click Next on the Conversion Information page; this time there should be no issues to resolve.

Figure 62 Conversion Information page
17. On the Volume Configuration page, select Primary channel (0) from the Channel drop down menu, and then click Next.
Note: The Data Size is the size of the partition that you set up for your Windows installation. The VHD Size is the size, or maximum capacity, of the entire hard disk drive. Your values may be different than those shown below. Because you are converting the physical drive to a VHD, the VHD must be just like the physical drive. The maximum VHD size will be the same as the size of the physical drive. The actual .VHD file will be as large as the amount of data that is on the hard drive; it will grow dynamically as more data is put on the VHD.

Figure 63 Volume Configuration page
Note: If your Data Size exceeds 16 GB, you will need to select a SCSI channel from the drop-down menu. By using SCSI channels, Virtual Server allows VHD files larger than 16 GB to be used. In the test case, the Data Size is only 6 GB, so a SCSI channel is not needed.
18. On the Select Virtual Machine Host page, select the available virtual machine host, in this case DC_SRV, and then click Next. The star rating shows how appropriate a choice the host is. For more information, click What do these ratings mean? at the bottom of the page.
Note: Typically, physical servers have more memory than an operating system may really need. When performing a P2V conversion, SCVMM automatically sets the amount of virtual machine RAM (Random Access Memory) to the amount that the physical server had. This may be too much for the Virtual Server host. For this reason, in this test scenario we specify that DC_SRV should have 2 GB of RAM and MEMBER_SRV1 should have only 512 MB of RAM. In a production environment, you may need to reallocate the amount of RAM for the virtual machine before starting it; instructions for this are in Appendix B.

Figure 64 Select Virtual Machine Host page
19. On the Select Path page, accept the default Save path, in this case C:\Documents and Settings\All Users\Documents\Shared Virtual Machines, and then click Next.

Figure 65 Select Path page
20. On the Additional Properties page, accept the default additional properties, and then click Next. In the test scenario, the only additional property will be the action when Virtual Server stops; this will be Save State.

Figure 66 Additional Properties page
21. Before you convert the physical server member_srv1 to a virtual machine, review the settings you have chosen on the Summary page. Leave the check box checked for Display the Job Status window when the wizard closes to view the progress of this operation. Click Create.
Note: If you are performing a Windows 2000 Server SP4 conversion, the Windows 2000 Server SP4 (the target) computer will reboot into a PXE-like environment while the disk is captured. This is an automated procedure and completes without any user interaction. You do not need to adjust the boot priority in the computer’s BIOS.

Figure 67 Summary page
22. Review the Job Status Tracking page to view the progress. As the conversion progresses, the job status will change from Running to Completed.

Figure 68 Job Status Tracking page
23. Once the physical-to-virtual conversion job is completed, close the Job Status Tracking page.
24. Shut down the physical server member_srv1.


Run the virtual machine
You can now start the virtual machine. VMAdditions.iso was added to the library in a previous section; now it will be loaded onto the virtual machine. Virtual Machine Additions improve mouse cursor tracking and control in the virtual machine. You will need to load them from an ISO file.
1. Return to the Virtual Machine Manager console.
2. Select Virtual Machines from the Virtual menu in the left pane.
3. Review the information for the new virtual machine, member_srv1. The status of member_srv1 will be stopped.

Figure 69 SCVMM console
4. Right-click member_srv1, and then click Virtual Machine Properties. You will now mount the VMAdditions.iso file on the virtual machine.
5. On the Configure Hardware page, under Bus Configuration, select Virtual DVD Drive.

Figure 70 Configure Hardware page
6. Under Capture Mode, select Known Image File and check the box next to Use ISO from library instead of copying. Leave all other default settings, and then click Browse.
7. Select VMAdditions from the library files, and then click OK.

Figure 71 Select ISOs page
8. Click OK to close the Properties of the member_srv1 page.
9. With member_srv1 selected, click Start from the Actions pane.

Figure 72 Actions pane of Virtual Machine Manager console
10. Once the status has changed to Running, right-click member_srv1, and then click Connect to Virtual Machine.

Figure 73 Connect to virtual machine
11. Click Yes to when warned about unencrypted connections.

Figure 74 Unencrypted Connection page
12. Log onto member_srv1 by pressing Right-Alt and Delete, and then enter your administrator credentials.

Figure 75 member_srv1
13. If you are performing a Windows Server 2003 conversion, enter p2v for the unplanned shut down, and then click OK. This prompt will not appear if you are performing a Windows 2000 Server conversion.
14. Click Start, and then click My Computer. (Double-click My Computer from the desktop in Windows 2000.)
15. Right-click CD Drive (VMADDITIONS), and then click AutoPlay.
16. On the Welcome page of the Virtual Machine Additions Wizard, click Next.

Figure 76 Virtual Machine Additions Welcome page
17. A pop-up window will tell you when the installation is complete. Click Finish.

Figure 77 Setup Completed pop-up window
18. When asked to restart your system, click Yes.

Figure 78 Restart the system
19. Log onto member_srv1.

Figure 79
20. Adjust the resolution to fit your monitor.