Microsoft Licensing Primer
-
@brianlittlejohn said:
@BRRABill servers don't have upgrade licenses.
So to go from 2008 to 2012 you need to totall y repurchase a license for 2012?
-
@BRRABill Yes, and CALs
-
@BRRABill said:
@brianlittlejohn said:
@BRRABill servers don't have upgrade licenses.
So to go from 2008 to 2012 you need to totall y repurchase a license for 2012?
Unless you have SA for it. SA provides an upgrade path.
-
@brianlittlejohn said:
@BRRABill Yes, and CALs
Well that makes it pretty darn simple.
Are there any company wide VL rights you get on the server level? Assuming you can move licenses around? (But only every 90 days, or if that something else?) Restore an image to another machine?
-
@scottalanmiller That is true... SA does. I've done the math for my org, and it isnt worth it.
-
@BRRABill said:
Are there any company wide VL rights you get on the server level? Assuming you can move licenses around? (But only every 90 days, or if that something else?) Restore an image to another machine?
Company wide licensing would normally be an Enterprise Agreement. Otherwise you are buying licenses for what you need.
Licensing the servers themselves you would need EA to move around, I believe. But to move workloads around you get DC licensing per machine and then the workloads can move to year heart's content.
-
What is DC again?
-
-
I think I read either here (or elsewhere like in the below link) you can legally move the VL around once every 90 days.
So say I only have 1 license and my server dies, I can BMR to new hardware and move the license.
-
@BRRABill said:
I think I read either here (or elsewhere like in the below link) you can legally move the VL around once every 90 days.
So say I only have 1 license and my server dies, I can BMR to new hardware and move the license.
Well you can move it once every 90 days, but you also have to have enough licenses on the target host.
For DR, this is not an issue. since you are replacing what you had. But when people move for load balancing, you have to make sure you have enough licenses one each host.
-
Right. Like that link says if you run it for a second on another machine you need a license.
-
@BRRABill said:
Right. Like that link says if you run it for a second on another machine you need a license.
Yup. Basically - don't move licensing around willy nilly. If you have to failover whole systems, you can do so (once every 90 days.) And if you want to have flexibility to do what you want, you buy DC licensing for each physical host and you are covered.
-
@scottalanmiller said:
@BRRABill said:
Right. Like that link says if you run it for a second on another machine you need a license.
Yup. Basically - don't move licensing around willy nilly. If you have to failover whole systems, you can do so (once every 90 days.) And if you want to have flexibility to do what you want, you buy DC licensing for each physical host and you are covered.
That kinda depends on how many VMs he is running... DC certainly simpler, but you can do it buying multiple Standard Server Licenses as well.
-
@brianlittlejohn said:
That kinda depends on how many VMs he is running... DC certainly simpler, but you can do it buying multiple Standard Server Licenses as well.
Not at any size where you want to move hardware around willy nilly.
-
@brianlittlejohn said:
@scottalanmiller said:
@BRRABill said:
Right. Like that link says if you run it for a second on another machine you need a license.
Yup. Basically - don't move licensing around willy nilly. If you have to failover whole systems, you can do so (once every 90 days.) And if you want to have flexibility to do what you want, you buy DC licensing for each physical host and you are covered.
That kinda depends on how many VMs he is running... DC certainly simpler, but you can do it buying multiple Standard Server Licenses as well.
Yeah the math is pretty basic to work out. I have not quoted DC lately (was $5.5k last time i checked), but I know I just got a quote with Server 2012 R2 at $800. So if you have 4 VMs spread as 2 on 2 hosts, that means you only need 2 licenses totaling $1600. But if you want to move them around whenever you desire, then you need 4 licenses totaling $3200. Still much cheaper than DC x 2 coming in at $11000.
-
I think that he wants to move the hardware that the license is tied to regularly. That's where it gets tough.
-
My org, right now, the most I will ever run on each server is 8 (including all Disaster scenarios), so Standard Licensing still worked out cheaper, next time around I will most likely purchase DC so I can break things out more on my VMs.
-
@brianlittlejohn said:
My org, right now, the most I will ever run on each server is 8 (including all Disaster scenarios), so Standard Licensing still worked out cheaper, next time around I will most likely purchase DC so I can break things out more on my VMs.
At eight it is still cheaper? I thought that the tipping point was seven, is it nine?
-
@scottalanmiller You just have to do more planning out to make sure you are covered in every DR/Maintenance scenario.
-
The ability to add more VMs whenever you want is big. When you get that close it is pretty common that you start being stingy with separating workloads to keep within your licensing. Get a DC license and often you suddenly jump from eight to a dozen VMs
