Solved

SBS 2008 Hyper-V OEM Licensing

Posted on 2013-11-18
4
1,110 Views
Last Modified: 2014-11-12
If I P2V a old sbs 2008 server onto my new hyper-v server and destroy the existing hardware, does the previous OEM license cover the new hyper-v client or does a new license need to be obtained?

The server is being "migrated" not rebuilt with the existing license.

Or do I need to buy an OEM license for the Hyper-V client and then that would cover me to P2V an existing OEM server to this hyper-v server.
0
Comment
Question by:tegenius
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
4 Comments
 
LVL 4

Expert Comment

by:reredok
ID: 39656261
I'm not sure but Windows 2008 Std Server (???) have 2 small printed KEY an physical Key and an virtual Key.

In a conversation with a guy from Microsoft Staff he accented that there is difference between that keys. A physical Key can't install in a VM and vice versa. He pointed that this is a [...of violation of this License Term...].

I'm not sure if a P2V convert bypass that fact.  I could'nt remember if SBS have two Keys?
0
 
LVL 120

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 250 total points
ID: 39656289
The SBS licenses is with the hardware, and is not transferable, if you destroy the hardware, the license is lost as well! You can only purchase OEM licenses with hardware.

Technically, you can P2V an OEM version of the OS. But Re-Activation is likely, requiring you to purchase a new Retail key for that installation.

I would contact Microsoft Licensing in your country, to check OEM licensing details. As OEM is different per country!

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
0
 
LVL 96

Assisted Solution

by:Lee W, MVP
Lee W, MVP earned 250 total points
ID: 39657250
You should look into migrating to a new server/Windows setup.  The OEM license is locked to the hardware and cannot be moved,  Virtualized yes (on the same hardware) but not moved.  However, you've waited too long.  You can no longer get a retail license (OR OEM) through any supported channels.  You MIGHT be able to find a copy on ebay or through another QUESTIONABLE source, but Microsoft ceased selling SBS 2011 through retail and volume channels in June and the OEM version (which is legally only sold preinstalled on new hardware) will not be available after December 31, 2013.
0
 
LVL 96

Expert Comment

by:Lee W, MVP
ID: 39660247
Just to clarify, I mistyped - I meant to say "You can no longer get a retail license (OR VOLUME LICENSE) through any supported channels. "  As noted subsequently, OEM editions are available with new hardware until the end of the year, but that's it.
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Question has a verified solution.

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

Suggested Solutions

A safe way to clean winsxs folder from your windows server 2008 R2 editions
When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
This tutorial will walk an individual through configuring a drive on a Windows Server 2008 to perform shadow copies in order to quickly recover deleted files and folders. Click on Start and then select Computer to view the available drives on the se…
This Micro Tutorial steps you through the configuration steps to configure your ESXi host Management Network settings and test the management network, ensure the host is recognized by the DNS Server, configure a new password, and the troubleshooting…

738 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