I commonly encounter partners that buy and then resell Microsoft OEM licensing, especially Windows Server and the Windows Client. The typical reason for this is usually price, but the ease of purchase also comes into play. There certainly is a measure of convenience in obtaining a server for instance with a copy of Windows Server 2012 preinstalled, or “with” the server as included media. As an employee of Microsoft I am always happy when a server is sold with a Windows operating system, but I sometimes cringe when I hear that the version of Windows purchased is not up to the task at hand.
What do I mean by that? …well as with everything else you what what you pay for. If all you want is a copy of the current Windows Server operating system installed on the server and you never intend to do anything beyond have that one physical server do its particular job and do not intend to engage in any complex scenarios (and today rather common ones) than more power to you. Be warned however that when you or your customer venture into the realm of virtualization, backup, deploying a standardized image, support, and many other areas, the OEM Windows Server License may not be the best value, nor the best price. Let’s take a closer look.
If we take Windows Server 2012 Standard edition as an example, you can find it on the internet from varying suppliers for the approximate prices listed below:
Windows Server 2012 Standard Edition (OEM Version): $778.00
Windows Server 2012 Standard Edition (Open Business Version): $879.00
Basically there is $100 dollars difference in price. If we are speaking quantities of product that really can up too, right? Sure, If your customer needs four server licenses you may save $400 on the front end, but upon a closer examination you may be better served with other licensing options such as with the slightly more expensive open license versions for a number of reasons that I alluded to above.
To be specific OEM licensing has many limitations:
There are other limitations, some for applications such as Microsoft Office prohibit RDS (Terminal Services installation). I encourage you to look at the OEM Software Licensing: Rules and Restrictions document that can be found here as it answers the most common questions.
If any of the above limitations are a concern for the customer I would encourage you to look at our volume licensing options. Another way to combat these limitations and to add additional capability is to attach Software Assurance directly to the OEM purchase. The customer has 90 days from the purchase date to add Software Assurance. As a type of Volume License, Software Assurance confers even more benefits that may be useful while addressing the limitations inherent to the OEM license. This option is more expensive however.
As an aside, it may be useful to know that when you purchase Microsoft OEM or volume licensing, in order to receive revenue credit with Microsoft (and therefore be eligible for rebates and recognition), your purchases must be made through an authorized distributor. A list of authorized distributors can be found here.
I'm currently putting a proposal together for a client who want to use virtuaisation and am trying to clarify the licensing.
From what I gather, 2012 Standard can be used in vrtualisation but when you want to move a VM from one physical server to another, thats fine. But when you want to move it back, strickly this should be done for 90 days otheriwse you breech Microsoft licensing terms.
With Datacentre edition, there are no restrictions.
Does this apply to earlier versions of Windows Server such as 2008 R2?
Same thing here in New Zealand. Server 2012 Std OEM goes for $949 while 2012 Std Open License is $1,600.
With such a difference it is hard to find value in the open license.
No it does not apply on previous versions of Server
what is the ROK ?
and what the difference between ROK and OEM?
Your calculations left out the costs associated with Microsoft audits. Microsoft volume license agreements include a section that obligates the licensee to perform software audits at Microsoft's request. These audits are very time consuming and require
the attention of technical staff, accounting staff and management. The labor costs associated with these audits dwarfs any of the numbers you have given here.