VMM 2012 Technical Documentation, including Step-by Step Guides
VMM 2012 Official Cmdlet Reference
VMM 2012 TechNet Launchpad
VMM 2012 PowerShell Cheat Sheet
VMM 2008 PowerShell Cheat Sheet
2008 R2 Guides and Reference Downloads!
VMM 2008 Interactive Decision Flow
Jonathan's Virtual Blog
Virtual Machine Manager - Orchestrator - Solutions and Guidance
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.
We know that SCVMM can convert physical machines into virtual machines with all work necessary to make this transitioned machine still boot and function correctly. This is a great feature that customers use daily. This work is done usually while the server is still running as an Online P2V. If you have ever stopped to think about how the P2V process works (or read the TechNet article explaining) then you know that the first part of the process is simply a volume shadow service (VSS) snapshot made of disks. This is the same technology used by Windows backup and most third party storage software.
The trick is to capture a state in time while the machine is running. For most systems this is a great solution. For some, this poses questions. SQL, Exchange and Domain Controllers write to databases at a high rate. By the time the snapshot is made quite a bit may have changed in the database. Also, as good as the technology is, this is pushing the limits of functionality. SQL and Exchange systems benefit from acquiescing the SQL or Exchange service prior to P2V (or any backup). This reduces disk writes and ensures database integrity.
Domain Controllers are another matter. If there is more than one in the domain there is replication between them. If the state of one is captured while it is processing Active Directory transactions, then brought online as a VM later, the VM and physical versions of this DC may be different. Additionally, there is the concern of USN journal wrapping during the snapshot process. Then again, online P2V of DC’s works well on a daily basis for many people. The alternative is to perform the conversion offline, an Offline P2V. What is the right choice?
Do you want the new VM created from the DC to function correctly and have no issues with the rest of your Active Directory domain? Yes? Good choice. Perform the P2V Offline. Now I refer you to an article written by Sander Berkouwer. This covers the entire process better than I have seen put together before. Nice pictures too. The article describes online and offline conversions, and the implications of Online P2V of Domain Controllers. Then it walks you through the process while addressing four very solid recommendations. Enjoy the article. Keep it as reference.
Thanks to Sander for allowing me to link to his work!
Active Directory in Hyper-V environments, Part 6 http://blogs.dirteam.com/blogs/sanderberkouwer/archive/2009/10/27/active-directory-in-hyper-v-environments-part-6.aspx
TechNet article referenced…
TechNet - P2V: Converting Physical Computers to Virtual Machines in VMM http://technet.microsoft.com/en-us/library/cc764232.aspx