Frosty555
asked on
Affixing multiple OEM stickers to a single machine
I'm building a server for a client of mine which is going to run Microsoft Windows Server 2012 R2 + Hyper-V Role.
The client wants to have these virtual machines:
2x Windows Server 2012 R2 VMs (for various things, DC, Fileserver, Webserver)
2x Windows Server 2012 VM (for Exchange 2010, and some future task maybe VPN)
Normally I would purchase and affix an OEM sticker to the server to license it, but because this server is going to be a virtual machine host, I need to license more than one copy of the operating system.
Can I purchase and affix TWO OEM stickers? One of them will be a Server 2012 R2 OEM sticker and the other will be a Server 2012 OEM sticker. Each of the stickers entitles the customer to install 2x VMs of that OS each, and consider them properly licensed?
The client wants to have these virtual machines:
2x Windows Server 2012 R2 VMs (for various things, DC, Fileserver, Webserver)
2x Windows Server 2012 VM (for Exchange 2010, and some future task maybe VPN)
Normally I would purchase and affix an OEM sticker to the server to license it, but because this server is going to be a virtual machine host, I need to license more than one copy of the operating system.
Can I purchase and affix TWO OEM stickers? One of them will be a Server 2012 R2 OEM sticker and the other will be a Server 2012 OEM sticker. Each of the stickers entitles the customer to install 2x VMs of that OS each, and consider them properly licensed?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
As Cliff suggested, OEM licensing restricts you to that one physical host.
So if you ever want to add a second virtual host, you cannot fail over or migrate your current VMs without violating the OEM licensing. I always avoid OEM licensing in virtual setups.
So if you ever want to add a second virtual host, you cannot fail over or migrate your current VMs without violating the OEM licensing. I always avoid OEM licensing in virtual setups.
I third Cliff's comments. You can't use OEM to get the additional HyperV Guests
Official Microsoft document, look at Q14:
http://download.microsoft.com/download/4/D/B/4DB352D1-C610-466A-9AAF-EEF4F4CFFF27/WS2012_Licensing-Pricing_FAQ.pdf
This document states only license, not mentioning open volume licensing or OEM. (OEM is mentioned once in a non-related question). Therefore I can only conclude that any license, be it Volume or OEM, is meant with license.
http://download.microsoft.com/download/4/D/B/4DB352D1-C610-466A-9AAF-EEF4F4CFFF27/WS2012_Licensing-Pricing_FAQ.pdf
This document states only license, not mentioning open volume licensing or OEM. (OEM is mentioned once in a non-related question). Therefore I can only conclude that any license, be it Volume or OEM, is meant with license.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
From the licensing data sheet, your assumption would be correct. Two standard licenses should allow you to do (4) virtual machines. You would still only have one host of course.
http://download.microsoft.com/download/F/3/9/F39124F7-0177-463C-8A08-582463F96C9D/Windows_Server_2012_R2_Licensing_Datasheet.pdf
"Determining the number of licenses for Datacenter and Standard editions
Each license covers up to two physical processors on a single server. The minimum number of licenses required for each server is determined by the number of physical processors. For Standard edition you can add more virtual instances by assigning
additional licenses to the server (two incremental virtual instances are added per license)."
http://www.zdnet.com/microsoft-ups-price-on-windows-server-2012-r2-datacenter-by-28-percent-7000019168/
"Customers can also choose to assign multiple Standard Editions licenses to a single server, in order to increase VM density on that server"