P2V Survival Guide
At customer events a few years ago, we started handing out one-page "Survival Guides" (printed both sides and laminated) with links to important resources. The wiki versions of the Survival Guides are meant to do the same things without killing trees or using laminating machines. Please add useful resources you know about to this list - it is the wiki way!
Tips:
Check your licensing. Avoid VM activation and legal issues. For example, when you do a P2V of Windows Server 2003, ensure that it is licensed with Volume Licensing (if you use it) and not OEM install.
Ensure that your physical machines are patched up to current requirements before conversion to a VM.
Run the VMM Configuration Analyzer (VMMCA) and target the following servers, prior to starting any conversion:
- VNM server
- Destination host
- Source computer
Resources:
- How to convert physical machines to virtual - Disk2VHD
- VMM: Troubleshooting P2V Conversion Issues
- P2V: Converting Physical Computers to Virtual Machines in VMM
- How to add NIC drivers for offline P2V in SCVMM 2008
- How to fix slow offline P2V times in VMM b/c of duplex switches
- Frequently Asked Questions: P2V and V2V Conversions in VMM
- Consider a Virtual SBS 2003 to SBS 2008 Migration
- List of Microsoft Support Knowledge Base Articles related to Microsoft Virtualization Technologies for 2010
- SCVMM V2V failed with Error (protocol error : too many authentication failures for root)
- Virtual Machine Manager Error Codes (13000-13499)
- Hyper-V: How to Shrink a VHD File
- List of Virtual Machine Manager (VMM) Updates
- Managing Hyper-V Virtual Machines in VMM (TechNet Wiki)
- Hyper-V: Tools
- The VMMCA and why it's important in troubleshooting SCVMM issues
- Fixing an incomplete VM that’s stuck in the Creating state in SCVMM 2008
- Managing a VMware Infrastructure or VMware vSphere in System Center Virtual Machine Manager (SC VMM)
- Virtual Machine Manager Error Codes (11000-11499)