virtualization.tv is coming...

Microsoft details Windows licensing for 3rd party virtualization platforms

Monday, June 11, 2007   |   3 Comments   |   addthis

Finally Microsoft takes a clear and official position about application of Windows licensing on virtual machines hosted on 3rd party virtualization platforms (including hardware virtualization solutions like VMware ESX Server or VMware Server and OS virtualization solutions like SWsoft Virtuozzo).

In a brand new whitepaper Microsoft covers all these scenarios, including special features like VMware VMotion and client-side licensing terms, detailing:

...

If you have assigned a single license of Windows Server Standard Edition to the server running ESX, then you may run one instance at a time of Windows Server Standard Edition. If you have assigned a single license of Windows Server Enterprise Edition to the server running ESX, then you may run up to four instances at a time of Windows Server. You may not run a fifth instance under the same Enterprise Edition license because that right requires that the fifth instance be running hardware virtualization software and software managing and servicing the OSEs on the server. However, Datacenter Edition permits unlimited running of instances in virtual OSEs.

...

VMotion, System Center Virtual Machine Manager, and Windows Server Clustering all move instances of virtual OSEs between physical servers. However, the licenses remain with the physical server to which they are assigned. When an instance is moved to a new physical server, the new server must have the appropriate licenses.

With a few exceptions, described in the box to the side regarding PUR, software licenses may only be reassigned to new hardware after 90 days. However, the dynamic movement of virtual OSEs between licensed servers is not restricted in any way. As long as the servers are licensed-and are not running more instances simultaneously-you are free to use VMotion and System Center Virtual Machine Manager to move virtualized instances between licensed servers at will...

The most interesting part anyway is a final comparison chart between VMware ESX Server, SWsoft Virtuozzo and Microsoft Virtual Server, where appears VMware ESX Server is less expensive than competitors when using Windows Server 2003 Standard Edition, and has equal costs when you adopt Enterprise or Datacenter editions (which are preferred choice for virtualization deployments):

Microsoft already exposed its licensing strategy more clearly with launch of Virtualization Calculator 2.0, few weeks ago, but customers were still missing an official document to refer to.

Highly recommended reading before starting any virtualization project. Read it at source.

3 Comments

Anonymous ray Monday, June 11, 2007 5:28:00 PM  
The costs in the table only reflect Windows Server licensing costs and discounts the cost of the virtualization software. Once you add in the cost of ESX Server (Standard - $3750) or Virtuozzo ($999), the figures look different.
Anonymous A.Hamilton Tuesday, June 12, 2007 10:11:00 AM  
Very interesting indeed. Each of these technologies is priced the same. I remember VMware complaining about licensing costs a while ago. This looks the same to me. The main complaint i have is that ESX costs as much as the server hardware. ESX for a two proc system WITHOUT HA or VMotion is $3750. To get HA (which is a must if you're doing production work) raises the price to ~6k for a 2 proc system or 12k for a 4 proc system. We've invested some serious capital in VMware, but we're now in a wait and see mode to see what M$ has coming up.
Anonymous Rob Wednesday, June 13, 2007 4:58:00 PM  
Its a small step closer to a clear view of microsoft licensing and virtualization. I'm missing the part of SPLA licensing. And specially User Access licensing for Datacenter. Again Datacenter looks the cheapest option, but when you have users logon to a Datacenter environment you still need expensive CAL's. Where Enterprise comes in an authenticated per processor SPLA license, Datacenter is only available in unauthenticated per processor SPLA license.

Add New Comment