Solved

MS Server's OEM licensing will mess up P2V while virtualizing the servers ?

Posted on 2014-02-03
1
884 Views
Last Modified: 2014-04-02
We have some Win 2003 and 2008 servers with OEM licensing. We were told that the OEM will make P2V not workable, and was asked to re-build those OEM servers in virtualization. Think about it that rebuilding servers would be a big job. I want to know if that really is the case. Is there a workaround for the OEM licensing not to be hindrance while on P2V process??
Please help.
0
Comment
Question by:Castlewood
1 Comment
 
LVL 119

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 500 total points
ID: 39830948
Depending upon which Country you reside the following is true:-

Original Equipment Manufacturers (OEM) versions

Note: Physical-to-virtual hard drive migration of a Windows installation is a valid function for customers with Software Assurance and full retail copies of Windows XP, Windows Vista, and Windows 7. Software Assurance provides users valuable benefits—please contact Microsoft Corporation for further information. Windows XP, Windows Vista and Windows 7 installed by Original Equipment Manufacturers (OEM) using OEM versions of these products may not be transferred to a virtual hard drive in accordance with Microsoft licensing terms.

Source
http://technet.microsoft.com/en-us/sysinternals/ee656415

http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Windows/XP/A_3721-Can-I-transfer-my-OEM-version-of-Windows-to-another-PC.html

Please also see my EE Article and P2V FAQ

HOW TO: FAQ VMware P2V Troubleshooting

In response to your question:-

Is there a workaround for the OEM licensing not to be hindrance while on P2V process??

The P2V process will complete, however OEM licenses are "locked" to the hardware it was purchased with. When you move this OS and License, Activation will break, it's unlikely you will be able activate on the virtual machine.

Microsoft would state, that you cannot move OEM licenses and are in breach if Licensing, but this depends on which country you reside.

Options available.....

1. Apply a Retail License Key to the VM after P2V.

or

2. Apply a Volume License Key to the VM after P2V.

or

3. Apply the OEM Product Key again it may work!

I would refer you to Microsoft Licensing, in your Country of Origin, for the Legal Aspects of Transferring your OEM license.

Many Experts were involved in a Question Previously on EE which I answered here

http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Windows/XP/Q_28339090.html#a39782336
0

Featured Post

Courses: Start Training Online With Pros, Today

Brush up on the basics or master the advanced techniques required to earn essential industry certifications, with Courses. Enroll in a course and start learning today. Training topics range from Android App Dev to the Xen Virtualization Platform.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Is your company's data protection keeping pace with virtualization? Here are 7 dynamic ways to adapt to rapid breakthroughs in technology.
Teach the user how to edit .vmx files to add advanced configuration options Open vSphere Web Client: Edit Settings for a VM: Choose VM Options -> Advanced: Add Configuration Parameters:
Teach the user how to use vSphere Update Manager to update the VMware Tools and virtual machine hardware version Open vSphere Client: Review manual processes for updating VMware Tools and virtual hardware versions: Create a new baseline group in vSp…

785 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question