Microsoft Licensing Primer
-
Well it's an easy checkmark on the ordering page.
-
So perhaps it would be easier for someone to present a Cliff Notes version of the server version of retail and VL. (And SA, too, since a lot of people seem to like it for servers.)
I can try, but I have a feeling I am going to get a lot wrong.
-
@BRRABill said:
Well it's an easy checkmark on the ordering page.
That's why they do it. OEM is a great example of vendors not having your interest at heart.
Technically if you have extremely predictable workloads and are using DevOps tools and move everything using containers and... no nevermind, there really is no effective way to make OEM Server not completely crazy.
-
@scottalanmiller I would just assume retail doesnt exist as well. I only consider VL licensing for servers.
-
@BRRABill said:
So perhaps it would be easier for someone to present a Cliff Notes version of the server version of retail and VL. (And SA, too, since a lot of people seem to like it for servers.)
I can try, but I have a feeling I am going to get a lot wrong.
Basically retail only exists for customers who have not gotten big enough to get a VL license which, in theory, it basically no one.
Get servers through VL and only VL. You need CALs, that gets you into the VL range. So if you need a server, you need VL and it saves you money. So while I could come up with extremely fringe use cases for retail, it's really just academic.
In the real world, desktops are OEM and servers are VL.
-
@brianlittlejohn said:
@scottalanmiller I would just assume retail doesnt exist as well. I only consider VL licensing for servers.
Yup. I'd actually put that way up in the thread. OEM for desktops, VL for servers and ignore all others. They are special cases at best.
-
Retail and OEM for servers are really pointless. Just too expensive to justify.
-
So VL is the only real way to go on the server front. Got it.
For desktops, there is only a VL UPGRADE license. For servers, there is a base license, correct? And also an upgrade license?
-
@BRRABill servers don't have upgrade licenses.
-
@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.
