Note: This article is based on VMM 2008  and might not apply to VMM 2012 (R2)

 This topic provides guidance for troubleshooting issues with physical to virtual machine (P2V) conversions in Microsoft® System Center Virtual Machine Manager 2008 (VMM) and System Center Virtual Machine Manager 2008 R2.

Important   Microsoft strongly recommends that you use the Virtual Machine Configuration Analyzer (VMMCA) to evaluate the source computer before you try to perform a P2V conversion. This can help you to quickly identify well-known issues. To download the VMMCA for VMM 2008 and VMM 2008 R2, visit the following Web site: System Center Virtual Machine Manager 2008 and 2008 R2 Configuration Analyzer. Before you run the VMMCA, you must install the Microsoft Baseline Configuration Analyzer. There is a download link on the VMMCA download page.

Perform the following general troubleshooting steps before you troubleshoot specific symptoms.

General Troubleshooting Strategy
  1. Confirm that P2V is supported for the operating system on the source computer and that the source computer meets all other requirements that are described in the TechNet Library topic P2V: Requirements for Physical Source Computers. (Microsoft recommends that you run the VMMCA tool to evaluate the source computer. See the Important note above.)
  2. Ensure that all of the latest VMM updates are installed.
  3. Find the source of the error by opening the Jobs view, selecting a job, and then clicking the Change Tracking tab in the details pane. Find the job where the Status property changed. After you find this job, click the Summary tab of the details pane to investigate the issue.
Possible Symptoms/Causes of P2V Issues

Possible Symptoms/Cause Resolution
P2V conversion fails during the conversion of a VMware virtual machine to a Hyper-V or Virtual Server virtual machine.

This issue occurs if you did not remove VMware Tools from the source VMware virtual machine before you began the P2V conversion.
To resolve this issue, uninstall VMware Tools, and then try the P2V conversion again.

P2V fails during an offline P2V conversion. You may receive the  following  error message:

Error (3133) Virtual Machine Manager could not connect to source computer after it restarted into Windows PE (temporary computer name is computername). Automatic restart to the original operating system is scheduled to occur within 15 minutes. Recommended Action If does not restart in 15 minutes, manually restart it back into the original operating system by using the start menu.

P2V conversion will fail if the correct network or mass storage drivers for the source computer are missing from the Windows Preinstallation Environment (Windows PE).

Error 3133 occurs if the network adapter driver for the source computer is missing. Therefore, VMM cannot contact the source computer after it reboots into Windows PE.


To resolve this issue if a network driver is missing, follow the steps in KB article 970921: How to add NIC drivers for offline P2V in VMM 2008


Also, see the following blog posting from Jonathan’s Virtual Blog: Drivers Required for Offline P2V – How to Download, Extract and Stage


Important   When you download a missing driver (network or storage), ensure that the driver is for Windows Vista/Windows Server 2008 or later. You must do this because the version of Windows PE that is used is based on Windows Server 2008. If the source computer has a network adapter or an internal SCSI controller (typical in older hardware to attach the boot device) where a Windows Server 2008 driver is not available, you can try the following:
  • For the network adapter or SCSI controller, install the Windows Server 2003 version of the driver (if available), and then try the offline conversion again.
  • In the case of a network driver, you can temporarily install a newer NIC (with a Windows Server 2008 driver) in the source computer just for the P2V conversion. You can remove it after P2V conversion completes. 
If offline conversion still does not work, you can try the following workarounds:
  • Upgrade the source computer to Windows Server 2003 with SP2 and perform an online conversion. (This is not recommended for a domain controller.)
  • Build a new virtual machine and migrate applications and services from the Windows 2000 physical server.

Volume Shadow Copy Service (VSS) fails to take a snapshot of the contents of the source computer's drives.

Review the System and Application event logs on the source computer for VSS errors. If you are unable to resolve the VSS errors on the source computer, perform an offline P2V, which does not use VSS.

Installation of the VMM agent on the source computer fails.   

View the VMM*.log on the source computer to gather additional information.
  • On computers with the Windows 2000 Server, Windows XP, or Windows Server 2003 operating system, the log files are stored in C:\Documents and Settings\All Users\Application Data\VMMLogs.
  • On computers with the Windows Vista or Windows Server 2008 operating system, the log files are stored in C:\Users\All Users\VMMLogs.
The source computer for an offline P2V conversion has less than 512 MB of RAM available. Add more RAM to the source computer to equal at least 512 MB.

During a P2V conversion with a Hyper-V destination host, the conversion completes. However, you receive a 1322x warning message that indicates that the installation of Hyper-V Integration Services fails. For example:

Unable to install Virtual Guest Services on virtual machine <computername>. The Hyper-V Integration Services setup exited with error code 60001.

 This issue may occur if the operating system on the source computer is not supported on Hyper-V virtual machines.

Ensure that the operating system on the source computer is supported as a guest operating system on Hyper-V virtual machines.

See the TechNet Library article P2V: Requirements for Physical Source Computers for a list of guest operating systems that are supported on Hyper-V virtual machines.

To work around this issue, you can try to install virtual guest services manually.
The firewall on the source computer does not allow an exception for the Remote Administration service. Use the Group Policy Editor console (gpedit.msc) to add an exception for the IP address of the VMM host, for open ports, and for authorized applications.

To open the console, in the Run box, type gpedit.msc. To open the Windows Firewall settings, in the Group Policy Editor console, expand Computer Configuration, expand Administrative Templates, expand Network, expand Network Connections, and then click Windows Firewall.

During a P2V conversion using VMM 2008, the Background Intelligent Transfer Service (BITS) transfer fails with the error ERROR_NO_TRACKING_SERVICE. You may see receive the following error message:

Error (3154)
An internal error has occurred trying to contact an agent on the servername server.
(Internal error code: 0x8099319E)
The following issues might cause this BITS error:
  • The HTTP Single Sockets Layer (SSL) service is down.
  • On the source machine, an application or service (for example a Web site that uses an SSL certificate) is registered on port 443, the default port that VMM 2008 uses for P2V. (In VMM 2008 R2, the default port for P2V was changed to 40443.)

Possible resolutions include the following:
  • Ensure that the HTTP SSL service is running on the source computer, and then try the operation again.
  • If an application or service is registered on port 443, update the registry on the VMM server to change the default port that VMM uses for the P2V conversions. To do this, create a new registry entry named P2VBITSTcpPort, and assign any port that is not in use on the destination host. For detailed resolution steps, including the registry subkey to modify, see the following blog posting from the SCVMM team:
    P2V using System Center Virtual Machine Manager 2008 may fail with error 3154 (0x8099319E)
A Windows Vista-based source computer does not have an Advanced Configuration and Power Interface (ACPI) BIOS. Or, ACPI is turned off in the BIOS.    On the source computer, ensure that the source computer has an ACPI BIOS, and that ACPI is turned on in the BIOS.
The source virtual machine is on a perimeter network.

VMM cannot perform a P2V conversion if the source virtual machine is on a perimeter network. (A perimeter network, which is also known as a screened subnet, is a collection of devices and subnets placed between an intranet and the Internet to help protect the intranet from unauthorized Internet users.)

Connect the source computer to any other network topology in which the VMM server can connect to the source machine to temporarily install an agent and can make Windows Management Instrumentation (WMI) calls to the source computer.
A P2V conversion to a clustered host with VMM 2008 fails with the following error message:

Error 2927

A Hardware Management error has occurred trying to contact server %servername.

(Unknown error (0x8033801A))

This issue can occur if the clustered storage where the resulting virtual machine from the P2V conversion is placed has an invalid character such as a "\".

See KB article 970925 for more information and the suggested resolution:
SCVMM 2008 P2V conversion fails with Error 2927


A P2V conversion fails during the conversion of a computer that is running Windows 2000 Service Pack 4 (SP4) with the following error message:

ID: 3128
Details (Unknown error 0x80041001)

This issue may occur if the source computer is missing certain hotfixes.
See Mike Briggs’ blog posting for the list of hotfixes:

SCVMM Solution: P2V conversion may fail with error ID 3101 and "Unknown error 0x80041001"


Offline P2V conversion is slow.

This issue may occur when the network has 100 Mb full duplex enabled on the switch end.

See Michael Michael’s blog posting for a possible resolution:

How to fix slow offline P2V times in VMM because of duplex switches

 Ntbackup on Windows Server 2003 may fail with the following error after the system is converted using P2V  See blog posting:

Ntbackup on Windows Server 2003 may fail with the following error after the system is converted using P2V: "Error: The device reported an error to the request to write data to media

Other References
•    Troubleshooting and Data Collection During Offline P2V (from Jonathan’s Virtual Blog - 12/2008)
•    P2V: Converting Physical Computers to Virtual Machines in VMM(from the TechNet Library)
•    Description of the System Center Virtual Machine Manager 2008 update to address physical to virtual (P2V) issues (KB article 959596 – applies to VMM 2008)