Following on the theme around licensing, I thought I’d take the opportunity to explain, in detail, for anyone who doesn’t already know, how to license Windows Server Operations Systems in a Virtual Environment. Now, I’m not a licensing expert, but I’ve been through this enough times to understand it, and articulate it correctly, however, if something doesn’t make sense, add a comment! It’s important to note, that everything I discuss below, is relevant for Microsoft and non-Microsoft virtualisation environments.
So, let’s start…
Windows Server 2008 Standard
So, say we’ve bought a copy of Windows Server 2008 Standard, and we install it on the Physical box below.
If we’re not bothered about Virtualisation, this is a very simple licensing scenario indeed – all I’ve done is installed (and thus assigned) this Windows Server 2008 Standard license to this physical box. Easy peasy. From here, I could enable any of the roles of the OS, such as AD, DNS, DHCP etc, and have a great time doing it. If need be, I could downgrade this OS to a previous version of Windows Server (but I’m not going to go through this process today). There are a couple of very important things that we need to get out in the open early on here, as it’s relevant throughout this post.
- First important thing to note is, if I’ve bought this Windows Server 2008 OS on a piece of hardware, through an OEM channel, that license lives and dies with the hardware, so there’s no moving this license to another physical host.
- Second important thing to note is, if I’ve bought this license through a volume licensing program, and I want to re-assign this license to another physical host, I can do this, but, I can’t re-assign it again for another 90 days.
Now, as you know, Windows Server 2008 contains Hyper-V, so, if we enable this role, we can start running virtual machines on that particular host, but, what we do have to think about, is how we license those virtualised Windows Server guest OS’s running on that Windows Server 2008 Standard Host.
So, in this example on the left, we’ve decided to virtualise 1 guest server OS on our Windows Server 2008 Standard Host. We’ll say, for arguments sake, that this is a Windows Server guest OS. Now, with Windows Server 2008 Standard, I get 1 free running virtual instance on that particular host.
What that means is, when I assign a Windows Server 2008 Standard license to a physical box, I get the added benefit of not only being able to install the Windows Server 2008 OS on the physical hardware (and thus enable the Hyper-V Role), but I also get 1 free Windows Server guest OS, which can be Windows Server 2008 Standard or Downgraded
Read that last paragraph, then read it again to make sure you’ve got it.
I used a keyword in that paragraph. That keyword was ‘assign’. The reason I use the word ‘assign’ rather than ‘install’, is because this licensing is Virtualisation agnostic, which means I can ‘assign’ a Windows Server 2008 Standard license to a physical VMware ESX or Citrix XenServer (or A.N.Other!) host, and for free, run 1 instance of Windows Server 2008 Standard (or downgraded) in a VM on those platforms. If you want to run 2 instances of Windows Server Standard on those platforms, assign a 2nd Windows Server 2008 Standard license to that physical host, and that will give you another, and so on.
So, those bright sparks among you are going to say, well, if I not only assign the Windows Server 2008 Standard license to a physical host, but choose to install it on the physical host too (instead of A.N.Other Virtualisation platform), and then I create a Windows Server 2008 Standard (or downgraded) VM, am I not effectively getting 2 OS’s for the price of 1? Well, yes, and no.
The reason I say yes is, because you are getting 2 fully featured versions of Windows Server 2008 Standard – one for use on the actual physical host, and one for use in the VM. However, here’s the caveat. If you are using your maximum ‘free allowance’ of Windows Server VMs on a host (1 in this case), you must use the host machine to purely manage the virtual machines running on it, and nothing else.
So, in the example directly above, that physical box, with Windows Server 2008 Standard & Hyper-V running on it, can only be used to support the VM(s) above it, and not be providing other infrastructure features into the environment, such as Active Directory, Domain Controller, Web Server etc. It should be used purely for Hyper-V and managing the VMs running on it.
So, imagine this scenario:
In this scenario, we’re looking to run 3 Virtual Machines, which, for arguments sake, are Windows Server guests. To do this, using Windows Server 2008 Standard licensing, we’d assign 3 licenses to the physical box, which would not only give us the OS for the physical host, but the 3 guest OS’s we desire. If we wanted to move these VMs to another host, we’d have to reassign the Windows Server 2008 Standard licenses to the chosen host, however we wouldn’t be able to move it for another 90 days. Now, Windows Server 2008 Standard retails at about $999 I believe, so, this scenario will set us back just under $3000, and will go up by $999 for each guest Windows Server OS we want to consolidate. This pricing does not change whether you have 1 CPU, 2 CPUs or 4 CPUs in the physical box. So, a license of Windows Server 2008 Standard on a 1 CPU Dual Core System, is the same price as one on a Quad CPU Quad Core System.
If I was consolidating Linux guest’s onto this platform, perhaps open-source rather than commercial distributions, then the guest OS’s would effectively be free.
From a licensing perspective, using Windows Server 2008 Standard Edition is the least beneficial and flexible when compared with Enterprise and Datacenter editions when it comes to Virtualisation.
Windows Server 2008 Enterprise
So, hopefully you’ve got the gist from reading the bit above. Now, licensing Enterprise is very similar indeed, however, this time, instead of getting 1 free running instances, you receive 4 free running instances when you assign a Windows Server 2008 Enterprise license to a physical host.
So, in this scenario, we’ve simply assigned the Windows Server 2008 Enterprise license to the physical box, and we receive 4 free running instances of Windows Server 2008 Enterprise, or downgraded, in virtual machines. We could have 100 virtualised Windows Servers on this particular box, but the license gives you 4 free running instances at one time.
So, if you assign this license to an ESX or XenServer host – no problems, you receive 4 free running Windows Server instances. If you assign and install it, you’re getting a Hyper-V platform for free, and the 4 free running instances. Same rule as above applies – If you are using your maximum ‘free allowance’ of Windows Server VMs on a host (4 in this case), you must use the host machine to purely manage the virtual machines running on it, and nothing else.
This licensing is cumulative too, so if you want to assign 2 licenses of Windows Server 2008 Enterprise to the physical host, for 8 free running instances, just do it! Or assign 3 licenses for 12 free! It just keeps going, but remember, you can’t reassign Windows Server licenses from physical host to physical host more than once every 90 days. Another key area to be aware of is when you are using migration technologies, like Quick Migration on Hyper-V, VMotion on VMware’s platform, or XenMotion on the Citrix platform to name but a few. So, take this scenario:
In this example, we’ve assigned a Windows Server 2008 Enterprise license to both physical nodes, and we’re using our maximum 4 free running instances on both nodes. All is great :-)
We encounter a situation (Manual, DRS etc) where we need to migrate a virtual machine from one node to another. Technically, not a problem, however a move is going to put us out of compliance from a licensing perspective, because what we may find is that we’re running more than 4 guests on one of the nodes and less than 4 on the other. On the node that’s running less than it’s maximum of 4, there’s no problem. It’s just we’re incorrectly licensed on the node that’s now running more than 4.
One way to counter this, is to assign 2 Windows Server 2008 Enterprise licenses to each node, giving us a free allocation (or, breathing space) of 8 free running Windows Server VMs on each node. Whether we choose to use all 8 on each node is up to us, but if we do, we could get into a similar situation as we found before if we’re not careful. If it’s only a very temporary situation, i.e. you’ve moved all VMs onto physical host 2 for a short window whilst host 1 is patched, then you should be fine – Microsoft’s licensing is based on a trust model and understands the importance of temporary maintenance etc.
In the same way Windows Server 2008 Standard was licensed per box, so is Enterprise, so again, this pricing does not change whether you have 1 CPU, 2 CPUs or 4 CPUs in the physical box. So, a license of Windows Server 2008 Enterprise on a 1 CPU Dual Core System, is the same price as one on a Quad CPU Quad Core System. The retail price of Windows Server 2008 Enterprise is $3999, which, if you think about 4 free VMs per license, it works out at about $1000 per VM, so roughly the same price as Windows Server 2008 Standard, yet you get the Enterprise features like Clustering etc, inside the VMs.
Also remember, that any of these VMs can be downgraded to older Windows Server versions, such as 2003, or 2000. 2000 SP4 is the earliest supported version on Hyper-V, and runs great! :-)
Windows Server 2008 Datacenter
OK, so, we’re on the home straight here – just Datacenter edition to go! Stay with me!
Hopefully you understand what I’ve been talking about so far, because it’s very important when devising solutions based on Microsoft server technologies, regardless of the Virtualisation platform. I wouldn’t want to be a customer, who’s paid good money to embrace VMware’s technologies (for example), and been told incorrect information about Windows licenses running on those ESX hosts, which has resulted in the customer buying more licenses that necessary. Not good. It’s therefore critically important that both customers, and partners understand and can articulate this information.
So, what’s the deal with Datacenter edition, and is it too ‘big’ for my business? Well, let’s dip into a little history first – In previous versions of Windows Server, i.e. 2003, you could only buy Datacenter edition on hardware. There was no other channel, bar OEM, that organisations could get hold of Datacenter, so, in many cases, it would have been restricted to the larger organisations who were buying whopping hardware. That’s changed for 2008.
Update - As Mike rightly points out in the comments section "Windows Server 2003 Datacenter became available through normal channels in October 2006 - the same day these virtualization rights were introduced. You still get the rights with Windows Server 2003 and 2008 and can use the downgrade rights for earlier versions of the OS"
For the first time, Datacenter edition of Windows Server is available through regular Volume Licensing channels, so it’s instantly more mainstream and accessible for many more people, but, why would you want it? Well, if you take Windows Server 2008 Datacenter as an OS, it’s our most scalable version of the Windows Server 2008 versions, supporting the highest number of procs/cores, but feature wise, it’s pretty much the same as Enterprise. Where it changes massively, is when you bring in Virtualisation.
The Hyper-V bits themselves are identical to those in Enterprise, scaling up to 1TB RAM in the physical box, 24 cores with the latest Intel 6-core chips, 64GB RAM per VM etc etc. It’s the Virtualisation licensing that’s pretty darn different than Enterprise. Here’s the scenario:
Imagine we want to achieve a 16:1 consolidation ratio, so, 16 VMs (in this case, Windows Servers) running on 1 pretty powerful box. Seems pretty achievable I’d say, but what’s the most cost effective way of licensing it? Well, so far we have Standard edition, which gives us 1 free VM per assigned license, so we’d need 16 licenses @ $999 each, so we’re talking around $16k. We don’t have much flexibility using Standard edition, plus we can’t use any Failover Clustering, so we’re putting quite a few eggs in one basket here! What are the alternatives?
We have Enterprise edition, which, as I detailed above, provides 4 free running instances per assigned license, so, for 16 VMs, we’d need 4 Enterprise licenses assigned to this box. 4 Enterprise licenses @ $3999 per license weighs in at $16k, so pretty similar to Standard edition really, but with greater scalability and features under the hood. Final option? Datacenter Edition.
Now, first important point, Datacenter edition is licenses per physical processor, not per box, like Enterprise/Standard are. So, in our scenario, imagine the box on the left has 2 physical procs, each with quad cores.
So, in this case, we’d need to assign 2 Datacenter licenses to the box on the left, as it has 2 physical processors. Datacenter licenses go for $2999 per processor. That would mean that this scenario would cost us just under $6k. But what are we getting for our money? I haven’t mentioned any ‘free’ virtual machines yet….
Windows Server 2008 Datacenter Edition, when assigned to a host, allows an unlimited number of free running Windows Server guest OS’s on that host. So, for our scenario, where we want a 16:1 ratio, assigning 2 Datacenter licenses to that box (for a total of just under $6k) gives us what we need, and more. I could double, triple or even quadruple (and more!) the number of Windows Server Guest OS’s on that box, and still only ever pay $6k. This would only change if I upped the number of physical procs in the machine. So, $6k Datacenter, vs. $16k for Standard/Enterprise. Double the ratio to 32:1 and Datacenter is still $6k, but Enterprise & Standard are now coming in at around $32k – in fact, Standard would probably have hit it’s limit by that point, depending on how ‘big’ the VMs are (Standard edition supports 32GB RAM in the host).
The great thing to mention about Datacenter Edition (aside from the great Virtualisation licensing benefits!) is that it really eases the licensing headache around migration of virtual machines between hosts. If you have a 3 node cluster, each with Datacenter licenses assigned, it will never matter how many Windows Server VMs you’re running on each physical node. You can have 20 VMs on one, 10 on another, and 35 on another, and never have to worry about being incorrectly licensed from a Windows Server perspective. Excellent.
If these were the requirements of a project, on the top right, the first thing to note is, Standard Edition is pretty much out. It doesn’t have the clustering element to it, so it would have to be Windows Server 2008 Enterprise of Datacenter. I’m using Hyper-V as my virtualisation technology here, as I’m getting it as part of my license anyway, but if there was a requirement for a VMware or Citrix (or A.N.Other) deployment, then you’d factor those costs on top. So, Enterprise and Datacenter licensing assigned to the physical hosts will give me the features I need in terms high availability, and migration with minimal downtime.
So, do I choose Enterprise, or Datacenter for my licensing? Well, I think these results speak for themselves – I’d save $30k on these 3 nodes alone by using Datacenter. I could double my CPUs in each node too, up to 4 CPUs in each node, and it would still only come to $36k using Datacenter, so it would still be cheaper than Enterprise, and I get the added flexibility that Datacenter brings, plus, and this is a key point, future scale-up growth at no cost. I wouldn’t get this with Enterprise. For every 4 VMs I wanted to scale up, I’d be paying an extra $4k per license with Enterprise. Datacenter really is a compelling choice from a licensing, and a cost saving perspective.
Well, phew, we made it! Hopefully that’s made sense – if it hasn’t, that’s what the comment box is for on this post! Let me know! Hopefully this has given you clarity around licensing the different versions of Windows Server in virtual environments, and also some of the caveats you need to be aware of, like not being able to move OEM licenses around, or re-assigning licenses to hosts more than once every 90 days. You should also remember that the keyword is assign, not install. Microsoft would be naive to think that just because someone has bought Windows Server 2008 licenses, that they will always use Hyper-V as their virtualisation platform. Using the word ‘assign’, clears this up; simply assign a Windows Server license to a physical box, and you get the free VM rights. Whether you choose to utilise the added benefit of a free virtualisation layer in the form of Hyper-V on that system, is entirely up to you…
Just to avoid any confusion on the Datacenter licensing model: Windows Server Datacenter edition is licensed under the per processor + CAL model so you need a license per processor and a Client Access License for every user (user CAL) or device (device CAL) that has access to the server. With 1 single Windows Server Standard 2008 license you are entitled to run 1 physical instance and 1 virtual instance of Windows Server Standard. This rule does not apply to version 2003 where you have to purchase a license for every physical or virtual instance.
Correct - however you still need your CALs if you deploy Enterprise or Standard editions.
I can't thank you enough for this blog. I have to write up a positioning paper for my company on Hyper-V licensing and my head started spinning very soon after researching it. Your blog is very helpful.
I have a few questions.
1) I have two physical Hyper-V hosts, each with 2- Quad Core CPU's. At first, I plan to have 4 VM's on each host. I was going to buy one Enterprise license for each host. Do I have to buy 2 licenses for each host because I have 2 CPU's or can I just buy one Enterprise license (per host) now and then buy a second one later if I run more VM's?
2) I am also running the Windows 2008 R2 RC right now with the Clustering on both hosts. You mention that I can temporarily move VM's for patching purposes. But in the clustering environment, do I have to puchase 2 Enterprise licenses per server for failover purposes?
3) Also, I heard they were going to remove the 90 day restriction on OS's in the Windows 2008 R2 release. Is that true or just a rumor?
Thanks in advance Matt!
OK, let's tackle these Q's:
1) Nope - Enterprise is licensed per physical box, not per CPU. So, if you had 2 CPUs, and you wanted a max of 4 free running instances at a time, you could buy 1 license of 2008 R2 Enterprise (2008 R2 is now the current version!) for each of your hosts. This would give you your desired 4 free VMs per host. If you wanted to grow higher than 4:1, you could buy another Enterprise license later, but, at 5:1 or higher on a 2 CPU box, I would consider Datacenter edition. This will give you unlimited VMs per Host, and you'd need a total of 4 (Datacenter is licensed per CPU and you have 4 CPUs across the 2 hosts).
2) Microsoft licensing is based on a trust model. If one of your physical servers failed, and you had to run 8 VMs on one host, for that time, to be compliant, you could infact reassign your Enterprise license from Node 1, to Node 2, (leaving you with no licenses on the failed Node 1, and 2 licenses on the running Node 2), and then, when you had your Node 1 fixed again, assign license #2, from Node 2, to Node 1. Again, the licensing is based on a trust model - if you had an outage of a few hours, whilst you got the Node 1 fixed, it would hardly be classed as abusing your licenses, as long as it didn't stay like that for a long period of time, in which case, you can reassign your licenses as stated above.
3) 90 day restriction still stands for the OS - they removed it for things like Exchange, SQL, SharePoint etc. As far as I know, this still stands for R2. This is why Datacenter edition makes things very easy, as you're never non-compliant!
Thanks for a great article!
In a scnario where our virtual hosts are Server 2008 DC, what versions of Server 2008 can we run as "virtual clients" are we licenced to use DC eddition on the virtual hosts too?
Thanks for the comment. If you're hosts are licensed with 2008 Datacenter, your virtual clients can be Datacenter, Enterprise, Standard or Web, and even downgraded to previous versions like 2003.
Hope that helps!
If I buy Enterprise Edition, and download 2008 HYPER V Server can I somehow increase the number of VMs for free and maximize my use of 2008 server VMs vs the 2003 server licenses I currently have? What is the max scenario I can get out of 2008 Server Enterprise using the assigning method? or will I somehow always be limited to 4 VMs? i don't wan't to be in any grey areas or licensing violations.
I am trying to virtualize all my phsical servers right now. I have 4 physical boxes. Each is compliant to run Virtualization. Each has enough 64 bit hardware without running into resource issues like not enough memory, hd space and cpu power. I have spent a small fortune on new hardware and new software (crm and ERP system). My budget leaves me with enough room to buy 1 Enterprise 2008 license and I have 3 windows 2003 server std Retail Box licenses and 2 windows 2003 server enterprise licenses .
Currently I have at least 9 roles on my phsical boxes Exchange server, sql server, application server, file server, sync server, e-commerce, domain controller, teminal server, backup domain controller. They are all on 2003 server OS licenses i mentioned above.
Is there a way to go all virtual without spending more than the Enterprise license? (I don't want to use 2005 virtual edition either.)
My goal is to eventually bring all servers up to windows server 2008 and have all my machines virtualized .
Thanks for the comment.
Each Server 2008/R2 Enterprise license you assign to a piece of physical hardware, will give you the rights to run 4 instances (at any one time). Technically, there is nothing stopping you running 5, 6, 10, or 20 VMs at once, but from a licensing perspective, each Enterprise license gives you 4 running instances only.
So, if you are planning on running 4 hosts, each with Hyper-V Server 2008 R2, you could buy 1 Enterprise license for one of your hosts, and this would give you 4 Guest OS's on that host, but for the other 3 hosts, your Windows Server 2003 licenses will only give you 1 OS per licence. So, you could go 'all virtual' but to get to 2008 in the future, you'll need more than 1 2008 Enterprise license, unless you look at Datacenter Edition, which will allow you to conolidate more guest OS's on a particular host.
Hope that helps,
What I still don't get about Datacenter is "unlimited number of free running Windows Server guest OS’s on that host." Where do these free Guests come from? In other words do I just purchase I copy of Server 2008 std 32bit and use it for as many VMs as I want? What about activation?
To my knowledge, when you buy your Volume license of Datacenter Edition, you've got the rights to run unlimited guests on that host, so you build as many VMs as you like, and activate them with something like a KMS Server. You wouldn't need to purchase any other copies of Windows Server for that host - you're completely covered.
Lots of activation info here: http://technet.microsoft.com/en-us/windows/dd197314.aspx
Excellent article! congrats. I wish the rest of MS licensing would be as easy to read as this is.
One question, The 4 (virtual) for 1 (assigned licence) for Enterprise Edition is exclusive to 2008? or 2003 is also allowed to do this? If it is, can you tell us how far back can this right be used? (with regards to the W2003 Ent Ed. you have, R2 or not)
Thanks in advance!. Regards,
Question about P2V conversion of an MS server running an OEM copy. would I be legal as long as I bought a new license for that server once it is converted to virtual or do I need an Enterprise or DataCenter license to cover it?
I love how over a year later people are still using your blog post for information. Let me ask you this question just to be sure.
My company wants to use VMWare ESX. To take advantage of the extra 4 licenses in Server 2008 Enterprise we would have to run a VMWare VM of Server 2008 and inside server 2008 run 4 Hyper-V VMs? or can there be a total of 5 VMWare VMs running on the host?
Or am I just totally off base and none of this applies to a Server 2008 VMs on a VMWare ESX machine:
I know! I hope my System Center equivalent post I'm working on will be just as popular!
Key thing to remember is that the 'free instances' are available to everyone, regardless of the hypervisor you are using.
So, say you have 1 ESX host - ESX is installed on the hardware (Physical Server A). You buy a copy of Windows Server 2008 R2 (as this is the current OS on the price lists), and you literally say 'this license is going to be assigned to Physical Server A' - it's a paper-based exercise. Once complete, you then have the rights to run 4 instances of Windows Server 2008 R2 (or downgraded), in VMs, on Physical Server A. These can be the same 4 VMs 24/7, or they can be a different 4 VMs every hour of every day. Key thing to remember is you get 4 running instances at any one time. So, you would leave ESX as it is, and create your 4 VMs.
Thanks so very much. You have helped beyond what you know!