Common SCVMM P2V Conversion Failures Explained

Published Feb 15 2019 04:19 AM 61 Views
First published on TECHNET on Nov 16, 2010

Our very own Jonathan Jordan just posted a great article describing a System Center Virtual Machine Manager 2008 support incident he worked recently where a small percentage of machines were failing during the Physical to Virtual (P2V) conversion process.  He walks through the steps he took to identify the cause and resolve the issue and shows you how you can do the same in your environment.  Whether you've had to troubleshoot the SCVMM 2008 P2V process or not, you won't want to miss this one.

Physical to Virtual (P2V) conversion is one of the most popular features of SCVMM. This said, there are a plethora of articles written to make the process easy to understand, or to resolve common problems. Last week I worked with an company that had converted around three hundred systems (nice!). Two systems were giving them a headache, so they reached out to Microsoft Support. Since they had successfully converted so many systems already, I knew the problem was almost certainly NOT with the SCVMM server or any Destination Hosts (managed Hyper-V systems) they had been using. What does this leave? The two P2V Source machine (ones to be converted). In the end this proved true…

To continue reading Jonathan's article click here .

J.C. Hornbeck | System Center Knowledge Engineer

The App-V Team blog:
The WSUS Support Team blog:
The SCMDM Support Team blog:
The ConfigMgr Support Team blog:
The SCOM 2007 Support Team blog:
The SCVMM Team blog:
The MED-V Team blog:
The DPM Team blog:
The OOB Support Team blog:
The Opalis Team blog:

Version history
Last update:
‎Mar 11 2019 08:35 AM
Updated by: