IT Core Blog

Never stop questioning. Curiosity has its own reason for existing…

How to P2V with Virtual Machine Manager 2008 and 2008 R2 Part 2

with one comment

If you miss part 1 of this series, please check it here.

Now that we already know the minimum requirements to run P2V conversions, let’s check what additional steps we need to perform in order to get our physical computer converted to virtual.

I recommend that you run the VMMCA (Virtual Machine Manager 2008 and 2008 R2 Configuration Analyzer) before starting the process, this diagnostic tool will determine important pre-installation or post-installation configuration settings for computers that either might serve or are serving Virtual Machine Manager (VMM) roles or other VMM functions. You should use this version of the VMMCA with VMM 2008 and VMM 2008 R2 only. All steps performed by VMMCA are described in detail here.

After you run the scan, the output should be similar to:

Now that we run the VMMCA and the output report shows “No configuration issues found” is time to open the Virtual Machine Manager Administrator Console, in the Actions pane in any view, click Convert physical server to open the Convert Physical Server Wizard.

On the following screen enter the computer name or IP address, an Account with local Administrator rights in the source computer. If the computer account that you’re using is a local account, then change the “Domain or computer name” to the machine’s name and click Next.

On the next screen enter the Virtual Machine Name and the proper owner, additionally you may enter some words for description for the new VM, then click Next.

On the next screen “System Information“, click “Scan System”  and the P2V agent is installed on the remote physical system with the credentials provided before and gathers the source computer’s hardware and software configuration (You can consult detailed information for this process here). After that, hit the Next button.

The Volume Configuration page will allow you to define the disk size (cannot be smaller than the existing one), the VHD type (Dynamic or Fixed), the controller channel and type (IDE or SCSI). Under conversion options you can choose between Online and Offline conversions, you can also decide either to shutdown or not the source computer after finishing the P2V process. In this scenario I’ll choose the Offline Conversion type. Make your required modifications and then click Next.

On the Offline Conversion Options page (assuming that you choose Offline Conversion), You’ll have to decide if you want to use DHCP or a Fixed IP Address. If using DHCP, make sure that the SCVMM can solve the DNS name of the source computer to the correct IP provided by the DHCP server. Make your required modifications and then click Next.

On the next screen “Virtual Machine Configuration” you can modify the settings for vCPU and Memoryto be configured in the final VM. For a Windows 2000 server, remember that only a single processor configuration is supported. Make your required modifications and then click Next.

On the Select Host page, select between the available hosts which are ranked based on performance and available capacity for this virtual machine. The hosts are ranked using a star ranking with the recommended host at the top of the list. Select the Hyper-V host or the Virtual Server where you want to place the new virtual machine and then click Next.

On the Select Path page, select an available drive with sufficient space to allocate the new VHD, also consider future snapshots and additional growth for additional VHD files if required. The host that I selected is a Hyper-V R2 node member of a Hyper-V R2 cluster with CSV enabled, in this scenario I’ll need to select the mount point that is created under C:\ClusterStorage\Volume(x). Select your drive and then click Next.

On the Select Networks page, select an available VSwitch that was previously created in the Hyper-V or Virtual Server Host Server. If you’re converting a Domain Controller you may want to check Not Connected in order to prevent unwanted network communications until you have verified everything is working correctly. Make your required modifications and then click Next.

On the Additional Properties page, select the Automatic Stop and Start actions you prefer and then click Next.

On the Conversion Information page, Confirm that the message No issues detected appears. If any issues are reported by the wizard those must be address before the conversion can continue. Each issue in the list explains how to resolve the issue. After resolving all issues, click Check Again to check for additional issues. When no issues are detected, click Next to continue.

On the Summary page, review the configuration settings. To change settings, click Previous. Optionally, click View Script to view (and copy) the Windows PowerShell script that runs this wizard and performs the conversion. All administrative tasks in VMM can be scripted or performed at the command line. For more information, see Scripting. Optionally, select the Start the virtual machine after deploying it on the host check box. Click Create to create the virtual machine.

The end Result should be similar to this:

Great job 🙂



Written by IT Core

December 20, 2009 at 7:23 PM

One Response

Subscribe to comments with RSS.

  1. […] Machine Manager « HP Sizer for Microsoft Hyper-V 2008 R2 available for download How to P2V with Virtual Machine Manager 2008 and 2008 R2 Part 2 […]

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: