IT Team
The Catapult IT team is responsible for providing end-user and network/server infrastructure support across Catapult’s six offices. Their blog contains insights and lessons learned from supporting the IT needs of a world-class consulting company.

P2V Lesson Learned – Check the License First   

Tags: Joe Stocker
Technorati Tags:

What should have been a straight forward P2V (Physical to Virtual Conversion) using System Center Virtual Machine Manager 2008 of a Windows 2003 system to a Hyper-V host turned about to be a lot more difficult because the operating system was installed with OEM media & product key.

This was a problem because after the P2V finished, I was greeted with an Windows Activation. And, it would not allow me to change the product key to a volume license key, and it would not accept the customer’s original OEM key.

clip_image002

According to MSFT Support, “If the original Windows installation was done using OEM media, then you’ll be unable to activate the P2V conversation. This is because  OEMs have the ability to lock a product key to a particular system using a method called SLP (System Locked Pre-installation) preventing it from being  installed on any other hardware. This can be done in the BIOS and if the  (SLP) is unable to verify the OEM installation after a change such as replacing motherboard, update BIOS etc, you may be prompted to activate the installation.

You can always contact the OEM vendor to see what assistance they might be able to provide, but other than that the other two options are:

*doing a fresh install of the OS using a Volume License key

*run an in-place upgrade on the system using a VL media and when prompted for the product key,  use a Volume License key”

At first glance, an in-place upgrade appears not to be an option, but after clarifying with MSFT support, the Repair option performs the same function as an in-place upgrade. Hmm. ok.

image

We were hesitant to perform this repair because it was a domain controller, but the operation went smooth and the server allowed us to enter a volume license key and boot up successfully as a VM.

Other tips that made this a successful P2V:

1. For very large file servers, ex: where the D:\ drive is > 1TB, you can skip those drives during the P2V process and only convert the C:\ drive. The trick is to create a placeholder VHD on another Virtual Machine and then xcopy/robocopy the contents. Then when the P2V finishes, you swing the VHD over to the new VM. That way, you eliminate the chance that the P2V fails during the BITS transfer. It also reduces the downtime of the P2V itself, because you can xcopy the contents over several days while the server is online, going back each time with the /D switch to just get the changes only.

So, how can you tell whether or not you are running an OEM version of Windows before you attempt a P2V?

To find your current PID:

1. Right-click My Computer, and then click Properties.

2. On the General tab, the PID appears in the Registered to box.

Standard Edition 32 bit retail

69712-000

Standard Edition 32 bit volume licensing

69712-640

Standard Edition R2, 32 bit volume licensing

69712-650

Standard Edition 32 bit  OEM

69712-OEM

Enterprise Edition 32 bit retail

69713-000

Enterprise Edition 32 bit volume licensing

69713-640

Enterprise Edition R2, 32 bit volume licensing

69713-650

Enterprise Edition 32 bit OEM

69713-OEM

http://msmvps.com/blogs/clustering/archive/2006/09/18/How-to-change-your-Volume-License-_2800_VL_2900_-key-with-Windows-Server-2003-or-R2.aspx

 
Posted by  Joe Stocker  on  8/6/2009
0  Comments  |  Trackback Url  | 0  Links to this post | Bookmark this post with:        
 

Links to this post




Pingback from  365 SSO / ADFS Guides | The-IT-Blog  on  3/30/2012  7:52 AM

Pingback from  Lync Recording Options « rubartsunifiedcommunications  on  3/30/2012  11:32 AM

Pingback from  Windows Server Backup VHD to Virtual Machine, possible?  on  4/10/2012  3:07 PM

Pingback from  XenServer to Hyper-V Conversion via WSB  on  11/2/2012  6:58 PM

Pingback from  WSB not recovering  on  11/25/2012  1:07 PM



Pingback from  KB2813630 – Backing up VMs on Server 2012 Failover Clusters  on  2/16/2013  4:13 PM

Pingback from  VM from baremetal backup  on  3/29/2013  2:54 PM


Pingback from  Exchange 2010, Windows Server Backup (bare metal) restore?  on  11/3/2013  11:58 PM


Pingback from  Knowledge is the Key! | Exchange 2007: Export mailboxes to PST  on  2/1/2014  8:23 AM



Pingback from  IT in 2014: One Big Cloud | News In Marketing  on  3/13/2014  3:54 PM








Comments

Name *:
URL:
Email:
Comment:


CAPTCHA Image Validation