Physical to Virtual (P2V) conversion is one of the most popular features of SCVMM. And, there are many 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.
When there is not already a great track record (if at all) of successful P2V jobs for SCVMM, then you need to look at SCVMM and the Hosts. That is what follows.
Identify and Resolve
Information below may resolve your problem based on whether the symptoms match up with yours. The most important thing to check is the job itself that failed in SCVMM. What step was being performed on the ‘Details’ tab when it failed? What DID work prior to this step? Compare this to the full P2V process as it is laid out in TechNet… with pictures!
P2V: Converting Physical Computers to Virtual Machines in VMM
The ‘Summary’ tab is also useful, but I can’t place enough emphasis on the ‘Details’ tab. What was logically going on? Think it through.
Questions to Ask Yourself
First, do you have all updates installed on the SCVMM Server and Hosts? Difficult to know… Follow this link to a simple solution… then proceed. http://tiny.cc/vmmupdate (It’s safe, I wrote it.)
>>> Identify your scenario from the section to follow! <<<
Possible Quick Fix
Pick which scenario matches your environment, and then follow the two test steps. I need to know what step, if any, below fails. Pick your scenario as it matches the illustrations above.
Did this complete successfully? If not, exactly what failed?
Possible Reasons for the failure
Depending on results from the above tests, one of these may be applicable.
Possible Resolution #1
If any of the test scenarios above fail…
In this event, follow the steps in the article below to remove the Destination Host from SCVMM, clean up certificates on both machines, then add the Host back and verify certificates. Explanatory article on removing a Host provided.
> Article to follow:
P2V fails with Error 2912 0x80072F0C with System Center Virtual Machine Manager 2008 or System Center Virtual Machine Manager 2008 R2
> Shameless plug… Article with same steps as above, but more detail.
P2V fails with Error 2912 0x80072F0C
> If you need help removing a Host:
How to Remove a Host
Possible Resolution #2
If none of the test scenarios above failed…
NOTE: If you interfere with the P2V process in the Hyper-V window whatsoever and the job fails it is because something you modified affected what SCVMM expected.
Nice article! I have always found Jonathan's blog to be extremely useful :-)
your link to vmmdate is broken, can we get an update?