Thursday, April 15, 2010

Getting around the Windows 2003 P2V Hyper-V Migration via SCVMM blue screen problem

Yeah I know that's one long winded title. Here's the scenario:
1. Used Microsoft System Center Virtual Machine Manager 2008 R2 to do a physical to virtual server conversion for one of my older Windows 2003 x64 servers.
2. Since it was an OEM OS, I had to buy another server license and do a Repair from a Win2k3 R2 CD1 since that's just about the only good way to get around that activation issue.
3. All attempts to boot the VM got me the dreaded Blue Screen with a 07B error code.

1. Don't install the integration components during the migration. On the last step of the SCVMM physical to virtual wizard it has an option to View Script.
2. Add -SkipInstallVirtualizationGuestServices to the very last New-P2V command. Then run the "Windows powershell - virtual machine manager" shortcut from the start menu and paste in the script. If you started from an OEM installation, continue to step 3, otherwise jump to step 5.
3. Then after the conversion, boot the VM off a Win2k3 R2 CD1 ISO or real CD and hit Enter for the first screen, then R to repair once it finds the OS.
4. After that's done, install Service Pack 2 for windows 2003 as it's required for the integration components. Then reboot.
5. Install the Integration services but DO NOT REBOOT yet. Check the registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Wdf01000
The Group Value should be WdfLoadGroup and NOT "Base" or else bad things will happen.
(Thanks to the guys at this thread: )

Now your virtual machine should boot up normally.


Charlie said...

Thank you for this post. I was having the same problem converting a physical OEM licensed Server 2003 R2 to a VLK licensed VM. With these instructions it worked perfectly!

Someguy said...

Thanks you very much for your post.
Works perfectly on Windows Server 2003 SP2 & VMM SP2

Anonymous said...

What script you need to past in powershell?

Gnawgnu said...

At the end of step 1, the wizard displays the powershell script that would need to be run. Just copy that text out to notepad or something.

Anonymous said...

For those of us with System Center Essentials, the bundled version of VMM does not display the script at any point. My workaround to skip the tools install was to go to the host machine and rename c:\windows\system32\vmguest.iso until the p2v conversion was done.

The p2v wizard would copy the disks and then error out before creating the virtual machine. I created a new virtual machine pointing at the .vhd files already created and was up and running.

Mark Sze said...

Thanks for posting this, I had experienced a BSOD when I tried to convert using a Windows Server 2000 R2 x64 SP2 server using P2V in SCVMM.

Following these instructions (non OEM), it worked perfectly for me!

Giovanni P said...

Great info!! I have this problem with a DELL PowerEdge 2900 with Windows Server 2003 Std x64 SP2 OEM installed.

After the 5 try, read your post and check the registry after the Integration Services installation, to find exactly what you said.

Thank you