Ultimate Windows Server 2016 Licensing Guide

Windows Server licensing has changed once again. With the Windows Server 2016 release date in October, 2016, Microsoft has shifted from a per processor licensing model to a per core licensing model.

This doesn’t mean Windows Server CALs (Client Access Licenses) are going away though, you’ll still need those.

It does however, mean that you’re going to have very different counts for your server licenses AND it means that Windows Server Standard and Windows Server Datacenter will once again have different features, other than virtualization rights.

If you have SA (Software Assurance) you’ll be getting a hand from Microsoft in some scenarios when making the transition to Windows Server 2016, and we’ll get into exactly what that means later on.

For now, if you’re responsible for managing a Windows Server environment, and/or managing the licensing, this Ultimate Windows Server 2016 Licensing Guide was created with you in mind..

If you can’t read through this entire guide now, you can download a pdf copy here [http://volumelicensingcourse.com/windows-server/] to keep it handy for future reference as you make changes to your Windows Server environment.

If you want just the basics, I’ve also put together a 1 page Windows Server 2016 Licensing Cheat Sheet, which you can get here:

Even if you’re not planning on running Windows Server 2016 just yet, now that it’s hits general availability, you’ll be purchasing under the 2016 licensing terms (we’ll also cover when you won’t be in this guide).

Table of Contents:

Windows Server 2016 Editions

Windows Server Standard & Datacenter 2016

System Center
Core Infrastructure Suite (CIS)

Windows Server 2016 Editions

While this guide will focus primarily on Windows Server 2016 Standard and Windows Server 2016 Datacenter, there are other editions available. We’ll briefly cover what those editions are here, along with basic licensing considerations.

Microsoft Hyper-V Server 2016

This is a free hypervisor download with no licensing considerations needed. That means there is no server OR CAL requirement.

This edition is intended to deliver enterprise-class virtualization for your data center or hybrid-cloud.

At the time of this writing it is currently in Technical Preview. You can find the free download, and more details here: https://www.microsoft.com/en-US/evalcenter/evaluate-hyper-v-server-technical-preview

Windows Storage Server 2016

This edition is available in the OEM channel only and is available in both a Standard and Workgroup edition.

For some reason Microsoft decided to leave this Windows Server edition alone in terms of licensing. It continues to be licensed by Processor and Windows Server CALs are not required for access.

Windows Server 2016 MultiPoint Premium Server

This edition of Windows Server is only available for Volume Licensing customers in the Academic space. Similar to Windows Storage Server 2016, MultiPoint Premium Server (now the only edition of MultiPoint Server offered) is licensed by Processor.

Unlike Windows Storage Server, MultiPoint Premium Server requires BOTH Windows Server CALs AND RDS (Remote Desktop Services) CALs.

Windows Server 2016 Essentials

This edition is intended for small businesses with up to 25 users and 50 devices. It is also licensed by Processor however it does not require any Windows Server CALs.

Windows Server Standard & Datacenter 2016

Now that we’ve covered the less common editions of Windows Server, let’s dive right into the main editions, Windows Server 2016 Standard and Windows Server 2016 Datacenter.

These editions are where we see the shift from a Processor based licensing model to a Core based licensing model. We also see Microsoft make the change back to different features between the 2 editions.

In Windows Server 2012 Microsoft made the decision to make these 2 editions identical in features with the exception of virtualization rights. In 2016, Microsoft moves away from that format and includes feature differences between them.

Figure 5 below comes directly from Microsoft’s Windows Server 2016 website and licensing datasheet and highlights the differences between Standard and Datacenter.

Processor to Core Migration

As mentioned above, Microsoft has made the shift with Windows Server 2016 Standard and Windows Server 2016 Datacenter to Core based licensing from the Processor based licensing introduced in 2012.

This shift includes new minimum license counts, license grants for SA (Software Assurance) customers, and keeps the Windows Server CAL requirement.

One mistake many people make when thinking about this Processor to Core migration for Windows Server 2016 is that they try to use the SQL Processor to Core migration from 2012 as a base of understanding.

Don’t do that. These are very different licensing models with different minimums and considerations altogether.

If you’re thinking about SQL Server right now it will only prove to make this more complicated.

Table 1 below highlights the basics of this licensing change from Windows Server 2012 to Windows Server 2016.

Windows Server 2012Windows Server 2016
Processors2 Processors/Server Minimum2 Processors/Server Minimum
CoresN/A8 Cores/Processor Minimum
OSEs (Operating System Environments)Standard – 2 OSE Max

Datacenter – Unlimited OSEs

Standard – 2 OSE Max

Datacenter – Unlimited OSEs

CALs (Client Access Licenses)Windows Server User/Device CALs requiredWindows Server User/Device CALs required

As highlighted in Table 1, the only licensing change from Windows Server 2012 to Windows Server 2016 is that Cores need to be counted now.

Pricing and Licensing Considerations

While Windows Server 2012 was licensed in 2 Processor packs, Windows Server 2016 is licensed in 2 Core packs.

In keeping with Windows Server 2012’s two Processor minimum and adding the new 8 Core minimum per Processor, you’re new minimum license count per server is 16 Cores, or 8 licenses.

Is your head hurting yet? If not, just wait, we haven’t even gotten to the good stuff.

If you’re Processors have no more than 8 cores each, you will see no difference in cost from 2012 to 2016. Microsoft is not raising their prices in that respect.

Where you will start to pay more is if your processors have more than 8 cores each. And since many people, maybe you included, have been buying processors with more than 8 cores over the past several years, this is where Microsoft will experience a nice jump in revenue without having to say they’ve raised prices.

An Important Note on OSEs

An OSE (Operating System Environment) is defined in Microsoft’s Licensing Brief: Licensing Microsoft Server Products for use in virtual environments as: Operating system environment (OSE) means all or part of an operating system instance, or all or part of a virtual (or otherwise emulated) operating system instance which enables separate machine identity (primary computer name or similar unique identifier) or separate administrative rights, and instances of applications, if any, configured to run on the operating system instance or parts identified above. There are two types of OSEs, physical and virtual. A physical hardware system can have one physical OSE and/or one or more virtual OSEs.

A common misconception is that a Windows Server Standard license grants you 2 virtual instances however, that’s only the case if the physical OSE is already licensed or, if the physical OSE is solely used to manage the virtual OSEs.

I’ve personally seen many organizations make this mistake only to find out about it during an audit from Microsoft. I’m sure I don’t have to tell you that having to get approval for an unbudgeted cost because of a counting error isn’t the greatest conversation.

Windows Server 2016 Licensing Scenarios

I’m more of a visual learner myself, and you may be too. Here are some visualizations, along with explanations of each to help with the new licensing.

Windows Server 2016 Standard

Figure 1: Server with two 8 Core processors and 4 VMs (Virtual Machines).

Licensing for the server in Figure 1 above with Windows Server 2016 Standard would require 24 licenses of Windows Server 2016 Standard, or 48 total cores.

Here’s why. The highlighted processors equate to a minimum license with 2 OSEs available for each. This means that the 2 physical processors, highlighted in blue (1 physical OSE), and VM 1, (1 virtual OSE) also highlighted in blue, are covered by 8 core licenses (16 total cores of the physical processors with 8 cores each).

VM 2 and VM 3, highlighted in green, make up 2 more OSEs. These VMs would require 16 more cores or 8 more Standard licenses.

Finally, we have VM 4, highlighted in peach. Because the minimum is still 16 cores per server, granting you 2 OSEs, this server is required to have another 16 cores, or 8 licenses.

So this server would require 24 licenses (48 cores) of Windows Server 2016 Standard and would have room to add 1 more VM without incurring any additional costs.

Figure 2: Server with two 12 Core processors and 4 VMs (Virtual Machines).

Very similar to Figure 1, in this scenario though, we have a server with two, 12 core processors and 4 VMs.

For the physical processors in this server we need 12 Windows Server 2016 Standard licenses (24 physical cores).

While we have more core licenses in this scenario, we still only have rights to 2 OSEs. This means we can again cover the 2 physical processors and VM 1 with those 12 licenses.

For VM 2 and VM 3, we license them with 12 core licenses (24 total cores).

For VM 4, we again license it with 12 core licenses (24 total cores), to meet the minimum requirements. This also leaves us with the ability to add 1 more OSE, on this server, without incurring any additional costs.

Regardless of the number of virtual cores assigned to the VMs, you simply “stack” the physical core licenses meaning you duplicate the physical core licenses for additional VMs/OSEs.

This is why we continued with 12 core licenses for the additional VMs.

We don’t count virtual cores at all when it comes to licensing the additional VMs for Windows Server 2016.

Now let’s talk about licensing Windows Server 2016 Standard for License Mobility or High Availability.

Figure 3: 2 servers, each with two 8 Core processors and 4 VMs (Virtual Machines).

In this scenario we have 2 servers, each with two 8 Core processors and 4 VMs. Our Windows Server Standard licenses here DO NOT have SA (Software Assurance).

These servers are setup to be able to migrate VMs from one to the other for high availability, or for instances where you may need to patch or update one of the physical servers.

This is a common scenario and often licensed incorrectly. The reason for this is because one of the purposes for virtualizing your servers is the ability to dynamically move VMs from one host to another for a variety of reasons.

Because we think of VMs as being very mobile, we often think the licenses for those VMs are just as mobile. However, that’s not necessarily the case.

A license is only transferrable from one host to another only once every 90 days. The only exception is for a hardware failure, in which case your licenses can move to another host temporarily, and then be moved back to the primary host once it’s repaired or replaced.

In any other cases, such as performing updates or patching of a physical server, the licenses can only be moved once every 90 days.

What this means for any servers licensed with Windows Server Standard is that you have to license each host for maximum virtualization.

In the scenario highlighted in Figure 3 above, that means 4 VMs could potentially move from Server 1 to Server 2, and vice versa, at any time.

Four VMs would be an additional 16 licenses (32 total cores) required for each server.

Now, our 24 core licenses for each server becomes 40 core licenses (80 total cores), because we have to license for the maximum potential.

There’s another way to license servers in this type of scenario that’s much simpler and would reduce your total license counts. We can accomplish that with Windows Server Datacenter licenses, which we’ll cover next.

Windows Server 2016 Datacenter Licensing Scenarios

As you may have noticed in the Windows Server 2016 Standard licensing scenarios above, this new licensing model can get complicated, and costly, pretty quick.

The more VMs you start to have, the more complicated this gets. And the more servers you have in a cluster, the more costly it gets and the more difficult it becomes to manage.

Generally speaking, if you need 7 or more Windows Server Standard licenses on a single server, it’s more cost effective, and easier to manage, if you move to Windows Server Datacenter.

Let’s explore exactly why that is and what it looks like.

Figure 4: 2 servers, each with two 8 Core processors and 10 VMs (Virtual Machines).

In this scenario, Server 1 and Server 2 are setup in a cluster to take advantage of High Availability.

This means that all 10 VMs (each with no more than 8 cores here) in either server could potentially move to the other.

Let’s compare this setup between Standard and Datacenter, starting with Standard.

If we licensed these servers with Standard, it would require each server to be licensed with 88 core licenses (176 total cores).

Here’s how we got to that number:

There are 11 OSEs (1 physical + 10 virtual) on each server. That means we need to license for 12 OSEs because of the 16 core minimum per 2 OSEs, which cannot be broken up.

(If our physical processors had more than 8 cores each, we would need to up this number to match the total cores as in Figure 2).


12 OSEs / 2 (for the 2 OSEs per Standard license) x 16 cores = 96 cores

96 cores / 2 (for the 2 core license packs) = 48 core licenses


Because the physical OSE will not migrate from one server to the other, we have 10 OSEs that could potentially migrate.


10 vOSEs / 2 (for the 2 OSEs per Standard license) x 16 cores = 80 cores

80 cores / 2 (for the 2 core license packs) = 40 core licenses


From here, we add the 40 core license packs to the 48 core license packs and get 88 total core license packs per server!

Because we’re talking about Standard, for every new VM you need to determine if you have an available OSE or if you need to buy 8 more core license packs before adding another one.

Now let’s look at the same scenario with Datacenter.

You may have noticed all of the OSEs in Figure 4 are highlighted in the same color.

This is because with Windows Server Datacenter, you’re only required to license all of the physical cores, granting you unlimited virtual instance rights.

Because of that, if you license each server with Windows Server 2016 Datacenter, they’re both always licensed for the potential maximum number of OSEs and you’re free to migrate VMs between servers as often as you like and the 90 day rule is not a factor.

So if we now license these servers with Windows Server 2016 Datacenter, you would only require 8 core license packs each.

Also, because the cost to license 14 OSEs of Standard is roughly equal to the cost of 2 OSEs of Datacenter (a 7:1 ratio), we also come out ahead in costs by licensing these servers, which have to be licensed for 22 OSEs each, with Windows Server 2016 Datacenter.

I hope this helps to highlight why it’s extremely important to get your license counts right the first time.

Many people are under the impression that Datacenter licenses are too expensive and unnecessary when in fact, there are many scenarios where that’s simply not the case.

As a bonus, which you may have already noticed, Datacenter licenses are much simpler to manage because you’re only required to license the physical cores rather than the physical cores and the OSEs.

Windows Server 2016 Standard

Windows Server Standard continues to be intended for physical or lightly virtualized environments.

As we saw in the licensing scenarios above Standard edition can get tricky to manage and even license correctly as we start to deploy more VMs. Fortunately, if you include SA (Software Assurance) with your licenses, Microsoft has an option to step up to Datacenter.

Stepping up is essentially the difference in price between Standard and Datacenter. Once you step up, there’s no going back.

If you have multiple Standard licenses assigned to a server and you decide to step up to Datacenter, you would only step up the licenses assigned to the physical cores and you’re then able to reassign the remaining core licenses to another server or servers, keeping in mind the 90 day license reassignment rule we discussed earlier.

With Windows Server 2012 Microsoft changed their direction in licensing Windows Server which really simplified the decision for choosing Standard vs Datacenter. With 2012 the features were identical and the only difference between these 2 editions was in their virtualization rights.

Standard allowed for up to 2 OSEs while Datacenter allowed for unlimited OSEs. Although the OSE rights remain the same with 2016, Datacenter once again includes additional features that Standard does not. (See Figure 5 above for an overview of these differences).

This means you may have a server that’s not virtualized, or that’s only lightly virtualized, but still requires Datacenter due to features only available in Datacenter edition.

Windows Server 2016 Datacenter

Last, but certainly not least, we have Windows Server 2016 Datacenter edition. Like Windows Server 2016 Standard edition, Datacenter 2016 is licensed per core and requires Users/Devices be licensed with the appropriate Windows Server CAL(s).

Datacenter edition is intended for highly virtualized datacenter and cloud environments.

If you skipped ahead to this section, I highly recommend you go back to the Windows Server 2016 Licensing Scenarios section of this guide for more details on the pricing differences between Standard and Datacenter, as well as scenarios to help you identify when Datacenter, from a purely licensing and cost perspective, makes the most sense.

As we’ve mentioned multiple times in this guide though, Windows Server 2016 Datacenter includes features that are exclusive to this edition. These features mean that a server that’s not virtualized, or that’s only lightly virtualized, may still require Datacenter edition.

Windows Server 2016 Datacenter edition exclusive features include:

As you can see, you’ll have a little more work to do in order to determine when you’ll require Standard or Datacenter edition.

Because it can be very expensive to choose incorrectly, be sure you take time to truly evaluate your specific needs across your environment before making any purchases.

Software Assurance

SA (Software Assurance) is no longer just for maintenance or upgrades. Over the years, as Microsoft was hearing from customers who wouldn’t purchase, or wouldn’t renew, SA on their licenses they continuously heard the same reason.

“We have no plans to upgrade in the next 3 years.”

Even the ability to annualize your payments over 3 years and to only pay for the SA costs after the 1st three years, bringing the costs down long-term, was not enough to persuade many folks.

Well, Microsoft got the message and started including additional benefits into SA like training vouchers, deployment planning services, and more. Over the past few years they’ve even included certain use rights as part of SA.

The whole aim of these changes has been to increase SA adoption, and it’s worked.

Below we’ll discuss some SA benefits/rights specifically for Windows Server 2016.

Nano Server

Nano Server is NOT a new edition of Windows Server. Instead, Nano Server is simply a deployment option within Windows Server Standard and Datacenter.

While this is a deployment option, it’s only an option if you’ve licensed your Windows Servers with SA (Software Assurance), making it a benefit, or right, of SA.

Microsoft does a good job in this TechNet article, Getting Started with Nano Server, describing Nano Server, so let’s use their words:

Nano Server is a remotely administered server operating system optimized for private clouds and datacenters. It is similar to Windows Server in Server Core mode, but significantly smaller, has no local logon capability, and only supports 64-bit applications, tools, and agents. It takes up far less disk space, sets up significantly faster, and requires far fewer updates and restarts than Windows Server. When it does restart, it restarts much faster. The Nano Server installation option is available for Standard and Datacenter editions of Windows Server 2016.

Nano Server is ideal for a number of scenarios:

  • As a “compute” host for Hyper-V virtual machines, either in clusters or not
  • As a storage host for Scale-Out File Server.
  • As a DNS server
  • As a web server running Internet Information Services (IIS)
  • As a host for applications that are developed using cloud application patterns and run in a container or virtual machine guest operating system

Can you think of some ways you can use Nano Server? If so, be sure you include SA when purchasing your Windows Server licenses.

Azure Hybrid Use Benefit

Microsoft is all about the cloud lately. To be more specific, Microsoft is all about their cloud and when it comes to Windows Server that means Azure.

To make it easier, and less expensive, for you to move to the cloud Microsoft has introduced the Azure Hybrid Use Benefit, which is a benefit of SA.

What this means in Microsoft’s own words:

For customers using Windows Server with Software Assurance, you can bring your on-premises Windows Server licenses to Azure and run Windows Server VMs in Azure at a reduced cost. The Azure Hybrid Use Benefit allows you to run Windows Server VMs in Azure and only get billed for the base compute rate.

For more information, including things like pre-requisites and how to verify your VM is using this benefit, be sure to review this article from Microsoft on How to deploy Windows Server using the Azure Hybrid Use Benefit

Now, here’s some fine print from Microsoft’s Windows Server & System Center 2016 Licensing FAQ:

For each Windows Server Standard and Datacenter Edition license covered with Software Assurance, customers can move or add incremental workloads into Azure across two instances, up to 8 cores each, or one instance up to 16 cores, and pay non-Windows (Linux) pricing. With Datacenter Edition, customers get lower-cost instances in Azure as well as rights to maintain existing on-premises deployments. With Standard Edition, customers still get lower-cost instances in Azure, but must assign the license to Azure and decommission the corresponding on-premises workload.

License Grants

As Microsoft makes the move from processor to core based licensing, similar to what they did when SQL made that shift, customers with SA receive what’s called a license grant, reducing the amount they’d have to spend on cores.

A license grant works by trading processor licenses for cores licenses. If your processors don’t exceed the minimum of 8 cores each, you will receive 8 core licenses (16 cores) for each 2 processor license you currently own.

In situations where your processors exceed the 8 core minimum per processor and 16 cores per server requirement, Microsoft will grant you additional core licenses to make up the difference.

Example 1: A 2 processor server, where each processor has 8 cores.
License Grant: 8 core licenses (16 total cores).

Example 2: A 2 processor server, where each processor has 12 cores.
License Grant: 12 core licenses (24 total cores).

Example 3: A 4 processor server, licensed with Standard, with more than 2 OSEs.
License Grant: 8 core licenses (16 total cores) will be provided for each 2 processor license with SA (if no inventory is done, only the minimum requirement is licensed).

It’s important to note that to receive your full license grant for each processor, you have to perform, and report, inventory to Microsoft.

This can be done with the free, MAP Toolkit (Microsoft Assessment and Planning Toolkit) or another inventory tool.

Also, a license grant only grants you the licenses, not the SA for processors with active SA. This means you’ll be responsible for paying the SA for any additional core licenses granted because, after all, the license grant is a right/benefit of SA.

System Center

Just like with Windows Server and System Center 2012 Microsoft continues to match the licensing models between Windows Server and System Center 2016.

Since this is not a guide on System Center I’m not going to go into great detail on it here. Instead, know that the same processor to core migrations we discussed for Windows Server 2016 apply to System Center 2016 as well.

If you’re a System Center user, or are considering System Center for your environment, you can use the licensing counts for Windows Server.

You can use the scenarios we talked about above to determine how many core licenses you need, what your core license grant will be, and ensure you’re compliant while not overspending.

Because Microsoft encourages System Center be included, or added to, any and all Windows Servers Microsoft hasn’t simply aligned the licensing models, they’ve created a suite, which we’ll discuss in the next section.

Core Infrastructure Suite (CIS)

Simplify and reduce costs. That’s what you get with the Core Infrastructure Suite.

If you’re purchasing Windows Server and System Center this is really a no brainer. The Core Infrastructure Suite gives you a single sku at a discount over licensing these products individually.

You can purchase CIS sku’s across multiple volume licensing agreements but the lowest possible price you’ll pay is if you license this via the Server and Cloud Enrollment (SCE).

The reason for the lower cost via an SCE is because you’ll need to commit to licensing all of your server licenses with CIS sku’s. Because you commit to license your entire environment, Microsoft gives you a break.

Another major reason for the discount, there’s a minimum of 25 servers to get into an SCE. So you have a larger minimum commitment and a requirement to license your entire environment.

Even if that doesn’t meet your needs, you can still purchase CIS sku’s on other agreements without those requirements.

Often times software suites try to sneak in products we don’t use in an attempt to get us to start using them. CIS is different because, in most cases, we’re either using both products or we’re not.

If you’re not using both Windows Server and System Center this sku will not make sense for you. I didn’t want to end this guide without talking about it though because it’s another purchasing option that many of you would benefit from taking advantage of.


Thank You

Thank you for checking out and using this Ultimate Guide to Windows Server 2016 Licensing. My goal with this guide is to help ensure more people understand the licensing and avoid getting to a non-compliant state.

In working with so many companies across the US over the past several years I’ve learned a few things.

  • Most, nearly all, organizations want to be compliant.
  • Microsoft licensing is complex and confusing.
  • Even Microsoft employees and “Software Advisors” struggle with understanding Microsoft licensing.

Knowing that the vast majority of organizations want to be compliant, and that there’s a lot of confusion and misinformation around Microsoft licensing, what’s needed is clarity.

Since Microsoft is moving away from clarity with Windows Server 2016 licensing there needs to be a single source of information you can reference with confidence.

That’s my goal with this guide, to be a single source of accurate information that you can reference to confidently make decisions on licensing your Windows Server environment.

I welcome your comments, criticisms, and questions. Tell me what you think of this guide and what else would be helpful for you to understand Microsoft licensing.

Email me directly here: http://volumelicensingcourse.com/contact/

All the best,

Pete Bebber | MCP
Volume Licensing Course

P.S. One more thing. If you haven’t already, you can enter your information below to download my Windows Server 2016 Licensing Cheat Sheet. This 1 page pdf gives you 80% of the information you need to properly license Windows Server 2016.

Windows Server Licensing Cheat Sheet

I remember back in college, having to buy all my textbooks for the semester.

It was expensive. I even sold my coveted Nintendo 64, along with all of my games once just to cover the cost of a few textbooks.

It was painful, but also removed an obstacle to getting my work done.

I also remember a big display of Cliff’s Notes in the book store.

College was mostly fun but reading textbooks was not.

So, sometimes I’d get the Cliff’s Notes so I could get the basics and have a little more time for some fun.

Because I want you to have more fun too, I put together the “Cliff’s Notes” (so to speak) for Windows Server 2016 Licensing.

Because, sometimes we don’t want to read the book.

This is a one page overview of how to license Windows Server.

Rather than a deep dive on all of the editions, it covers the 3 main editions.

  • Essentials
  • Standard
  • Datacenter

It also covers virtualization rights, SA Benefits and additional licenses.

You can download the cheat sheet by signing up below.

Top 5 SQL Server Licensing Mistakes

Top 5 SQL Server Licensing Mistakes

Microsoft licensing can be is confusing, which is probably why you’re here. SQL Server licensing mistakes are common and usually expensive.

So, I put together a quick report for you highlighting the top 5.

These are some of the mistakes I’ve seen repeated over and over again, and not just with SQL Server 2016 but earlier versions too.

Some of these we’ve talked about at Volume Licensing Course before and some we haven’t.

Avoiding these mistakes means real savings.

The report includes:

  • CALs vs Cores
  • Renewals
  • Software Assurance
  • Developers
  • Multiplexing

One client I worked with was able to take advantage of this knowledge.

They had a substantial SQL Server environment with an annual spend to match.

Avoiding just one of the mistakes you’ll read about in this report helped them save over $100,000 in a single year and repeat that feat the following year.

Another, much smaller company, actually made one of these mistakes and spent a few thousand dollars on a SQL Server license they were never able to use, because it put them in a non-compliant state.

We noticed the issue before they received an audit and came out clean in short order.

SQL Server licensing mistakes like these can be prevented and that’s part of my aim with this report.

It takes more than a single report to make sure you’re SQL environment is licensed correctly though.

A good license management process paired with staying up to date on Microsoft licensing and agreement rules make a real difference.

If you only ever look at your license deployments and entitlements every few years, you’re probably making these, and other mistakes.

Prevention is the best medicine.

Be proactive in managing your SQL Server licenses, don’t wait until an audit lands in your lap or you realize your renewal is next week.

By putting good license management processes in place you can avoid the mistakes that take up your team’s time and cost money you don’t have in your budget.

In the meantime, enjoy the free report and let me know what you think.

What is AHUB aka Azure Hybrid Use Benefit?

Azure Hybrid Use Benefit - AHUB

Microsoft has so many acronyms that it can be like speaking a completely foreign language. AHUB is the newest acronym Microsoft folks are throwing around and it stands for Azure Hybrid Use Benefit.

You’ve heard of this Azure thing Microsoft’s been talking about, right? You know, the cloud.

Well, the cloud is a pretty popular thing these days and you may not be surprised to hear this but, Microsoft is not the #1 cloud provider. AWS is the clear front runner right now and has been for some time.

Well, Microsoft is not all that happy about it.

In fact, Microsoft has done things like “seed” Enterprise Agreements with Azure, giving it away for free to get you to start using it, in an attempt to gain market share from AWS.

They learned that trick from the streets of course. Give them a free “hit” of your cloud and they’ll come crawling back for more, begging and willing to pay for it.

While that was helpful in the beginning, to a degree, the key to that strategy working is that Microsoft’s customers actually have to use it or they won’t come back.

And while Azure continues to gain acceptance and use from companies all around the world, the rate of adoption could still be much higher.

Microsoft is trying to lure more and more customers to Azure through different strategies.

Mostly, Microsoft is trying to make it easy for you to move to their cloud and the Azure Hybrid Use Benefit (AHUB) is designed to do exactly that.

What does Azure Hybrid Use Benefit actually do?

This benefit and benefit is used specifically here because it’s actually an SA (Software Assurance) Benefit of Windows Server, lets you apply your Windows Server licenses that have active SA to use Azure VMs at the base compute rate, which is equal to the Linux rate – https://azure.microsoft.com/en-us/pricing/details/virtual-machines/linux/.

This benefit allows you to run 2 instances with up to 8 cores, or one instance with up to 16 cores, at that base compute rate.

What’s so special about that?

That equates to a roughly 41% savings for a D2 instance in US East 2 Region (specific I know but that’s the example Microsoft is using).

How to take advantage of AHUB

One use case for this benefit is server consolidation.

A client with several Windows Server licenses, all on active SA, recently decided to consolidate their servers and, in that process, start using Azure for new workloads.

With 2 years of SA payments left on their Windows Server licenses, it felt like a loss to simply no longer be using them.

Enter the Azure Hybrid Use Benefit.

By repurposing their Windows Server licenses with SA for the cloud, they’ll save up to 41% on their Azure workloads.

If you’re interested in taking advantage of this benefit you’ll first need to create a Windows VM through PowerShell. You can get details on how to do that here: https://azure.microsoft.com/en-us/documentation/articles/virtual-machines-windows-ps-create/

You’ll also need to set the new license type property for each VM. You’ll get a specific notation in your bill that the benefit has been applied.

For more information on Azure Hybrid Use Benefit (AHUB) check out Microsoft’s AHUB page here: https://azure.microsoft.com/en-us/pricing/hybrid-use-benefit/#services

If you’re interested in learning more about the changes with Windows Server 2016 licensing, including Azure Hybrid Use Beneift (AHUB), you’d probably like my Ultimate Windows Server 2016 Licensing Guide. This guide is 21 pages and packed with everything you need to know when licensing your Windows Server environment now that 2016 is available.

Enter your information below to get the guide today.

Are you making this MPSA mistake?

Microsoft MPSA Mistake

I’ve been a little concerned lately with how some of my new clients have been managing their Microsoft agreements, specifically MPSA agreements.

If you’re managing your agreements like this, now is the time to change that.

Let me explain.

Multiple times over the past few months I’ve been talking with clients who are buying, mostly, under the MPSA (Microsoft Products & Services Agreement).

Note: Since Microsoft changed the minimum seat count for EAs, the number of MPSAs is rapidly increasing and this issue is becoming more common.

Now, in each of these recent cases, I’ve noticed that the person in charge of managing the Microsoft licenses, and the agreements, have been long-time EA (Enterprise Agreement) customers.

Whether they’re with a company that recently moved from an EA to an MPSA, or they came from another company with an EA, that seems to be a common thread.

Unfortunately, EAs and MPSAs have different rules for license purchases, including the True-Up process.

In fact, EAs are the only agreement types which actually allow annual True-Ups.

EA and SCE (Server and Cloud Enrollment) allow you to make an annual purchase, prior to your anniversary/annual payment date for all licenses deployed since your last anniversary/annual payment date.

That’s a True Up – you true up your licensing counts before you move into the next year of your agreement.

EAS (EA Subscription) is even handled differently than the EA and SCE.

So when I hear a client talking about True-Up dates for their MPSA, I’m concerned.

There’s definitely a compliance issue in play when that’s how you manage your non-EA or SCE agreements.

If this is how you’re managing your MPSA, be sure you change your process so that you’ve paid for every license deployed across your organization.

This would also be a good time to scan your deployments and get an inventory of deployed, and in use licenses in your environment.

Compare that inventory against what your current Microsoft entitlements are and you’ll know if you have something to worry about.

Ultimate Windows Server 2016 Licensing Guide

Windows Server 2016 Licensing Guide

If you’re a Volume Licensing Course email subscriber you can now download the complete Ultimate Windows Server 2016 Licensing Guide for FREE.

Not a subscriber? You can subscribe below and get your FREE copy of this complete resource for Windows Server 2016 licensing.

This 21-page pdf guide will help you make the RIGHT decisions to accurately license your Windows Server environment under the new, 2016 Windows Server licensing guidelines.

If you manage Microsoft licenses, or if you’re tasked with deploying and/or managing Windows Servers, this guide will be especially helpful for you. Rather than spend hours looking for the answers to your Windows Server licensing questions, you’ll have everything you need right at your fingertips, in one place.

To give you an idea of what’s included, here’s the table of contents:

  • Windows Server 2016 Editions

    • Microsoft Hyper­V Server 2016
    • Windows Storage Server 2016
    • Windows Server 2016 MultiPoint Premium Server
    • Windows Server 2016 Essentials
  • Windows Server Standard & Datacenter 2016

    • Processor to Core Migration
    • Pricing and Licensing Considerations
      • An Important Note on OSEs
    • Windows Server 2016 Licensing Scenarios
      • Windows Server 2016 Standard
      • Windows Server 2016 Datacenter Licensing Scenarios
    • Windows Server 2016 Standard
    • Windows Server 2016 Datacenter
    • Software Assurance
      • Nano Server
      • Azure Hybrid Use Benefit
      • License Grants
  • System Center

  • Core Infrastructure Suite (CIS)

  • Windows Server Licensing Resources

Even if you’re not planning to deploy Windows Server 2016 anytime soon, this is still a valuable resource because the licensing use rights for 2016 will apply to your Windows Server purchases now that it’s hit GA (General Availability).

The only exception is if you’re an EA or SCE customer with Windows Server licenses included as part of your agreement. In either of these scenarios, this guide will be a great resource for making deployment decisions to help prepare your environment for when it’s time to renew your agreement without overpaying or missing out on available license grant options from Microsoft.

If you’re not a subscriber you can still get your FREE copy by subscribing below today.

If you want to see more resources, like this guide, for other Microsoft products I want to hear from you.

You can email me directly at [email protected] and tell me what you want to see. I’ll do my best to address as many requests as possible.

In the meantime, check out the guide and learn all you need to know about licensing Windows Server today.

Top 5 Windows Server 2016 Licensing Mistakes

Windows Server 2016 Licensing Mistakes

Windows Server 2016 Licensing Mistakes Are Avoidable

Windows Server 2016 marks yet another change in Microsoft’s licensing scheme for the ever popular server OS.

Along with this change will come many mistakes, fueled by myths and assumptions about exactly how to license Windows Server 2016 Standard and Datacenter so, I’m going help you avoid those mistakes.

I’m going to run through some of the top licensing mistakes based on my nearly decade long career in software licensing and licensing changes Microsoft has made to Windows Server and other products in the past.

For much more detailed information, including exactly how to license Windows Server 2016, licensing scenarios, and other Windows Server 2016 editions, check out my Ultimate Windows Server 2016 Licensing Guide.

  1. Licensing OSEs (Operating System Environments)
  2. Minimum Core Counts
  3. Licensing for High Availability
  4. Windows Server CALs (Client Access Licenses)
  5. Software Assurance
  6. Summary

1. Licensing OSEs (Operating System Environments)

This is actually a carryover from Windows Server 2012, and with resellers and some Microsoft reps even getting this wrong, I anticipate the issues will continue to carry over.

Specifically, this relates to Windows Server Standard in which licensing the minimum number of cores (previously a 2 Processor license in 2012) will give you 2 OSEs (Operating System Environments).

This includes both physical and virtual yet is often confused as meaning 2 Virtual OSEs or Virtual Machines.

It’s true that 2 OSEs can mean 2 VMs however, you have to license the physical OSE as well. When you don’t count the physical OSE you’re not compliant. When you do that across multiple servers, your costs start to add up.

An exception is if that physical instance is only used to manage the virtual instances on that server. In that case, the physical instance does not count.

Be sure you count ALL of the OSEs on a server when licensing with Windows Server 2016 Standard, as you should have been doing with Windows Server 2012 Standard.

Counting OSEs is especially important if the VMs can move from one server to another. In that case, Windows Server Datacenter may be your best option.

Otherwise, you’ll need to license each server for the maximum number of OSEs that could be on each server at any time.

Imagine having 2 servers, each with 10 VMs, and they can all move from server 1 to server 2 and vice versa. Each server needs to be licensed for 20 OSEs, the max that can be on that server at any time.

If they’re licensed with Windows Server Standard that means double the cores for each server.

If they’re licensed with Windows Server Datacenter though, there’s no increase in core licenses necessary because Datacenter provides unlimited virtualization rights.

2. Minimum Core Counts

This is going to get a little tricky. Let’s go way back to Windows Server 2008/2008 R2 where Microsoft shifted to a per processor license. Back then, the minimum license count was 2 processors per server.

Even though that was the case, selling single processor licenses ended up being a huge issue as people were licensing their single processor servers (which are getting harder and harder to find these days), as well as individual VMs with just 1 license.

That led Microsoft to make a change with Windows Server 2012 licensing where they sold 2 processor licenses, eliminating the ability to buy a single processor.

This simplified the licensing and increased compliance.

With the change from processor based licensing to core based licensing, the minimum counts change and I expect the likelihood of falling out of compliance, due to sheer confusion from the licensing model plus the ability to buy too few cores, will shoot back up.

For your information, the new minimum is 8 cores per processor, 2 processors per server, totaling 16 cores per server minimum.

There’s far too much to cover in this article, so for more details, including licensing scenarios, check out my Ultimate Windows Server 2016 Licensing Guide.

3. Licensing for High Availability

When you’re servers are setup for High Availability you have VMs that can move from one server to another, allowing for less downtime, better management of power and cooling and ultimately lower costs in your data center.

If you license your Windows Servers incorrectly though, your costs could go up significantly with an audit.

We talked about OSEs earlier and one thing we didn’t mention is what happens when those OSEs move from one server to another.

If your servers are licensed with Windows Server 2016 Standard, you’re required to license each server for the maximum number of OSEs that could be on that server at any time.

I go into much more detail on this in my Ultimate Windows Server 2016 Licensing Guide but here’s a quick overview.

If you have 3 servers in a cluster, each with 5 VMs that could move to any of the other 2 servers, you now have to license each server for the physical OSE plus 15 VMs, not 5.

This is because if 2 servers end up failing over to 1 server, it will now have to be licensed for all 15 VMs, plus it’s physical OSE.

If all of the VMs have 8 or fewer virtual cores, and the physical server has no more than two 8 core processors, you would have to license 128 cores of Windows Server 2016 Standard.

If you add any other VMs to that cluster, you would also have to add more licenses to each server in the cluster.

This gets expensive and hard to keep track of very quickly. Fortunately, you have the option to license only the physical processors on each of these servers with Windows Server 2016 Datacenter, granting you unlimited VM rights.

And once you have 14 or more OSEs to license on a server, Datacenter edition becomes more cost effective, and easier to track, than Standard.

4. Windows Server CALs (Client Access Licenses)

I heard this question a lot when Microsoft changed Windows Server licensing from a server based model to a processor based model.

“Does this mean I don’t have to license CALs anymore, like with SQL in this model?”

The short answer: No, you still must license your users and/or devices with a Windows Server CAL.

With any server CAL, they have to match or exceed, the version of the server license. This means if you migrate a server from 2012 to 2016, any user and/or device that accesses that server, or an application on that server, must be licensed with a Windows Server 2016 CAL.

I’ve seen this mistake in the past and heard customers say, “but it’s only for this application.”

My response is, then you at least have to license any users/devices that access that application with the latest Windows Server CAL.

Disappointment follows, along with a request for an unbudgeted, and potentially significant purchase to finance.

5. Software Assurance

In the past, you might remember SA (Software Assurance) as simply maintenance. And it didn’t always make sense to include SA with your licenses.

Microsoft continues to add rights to their SA offerings.

We’ve already mentioned that Windows Server CALs are required to at least match the latest version of Windows Server those users/devices are able to access.

By licensing your Windows Server CALs with SA you don’t have to worry about purchasing new licenses simply because you deployed one server or one cluster with Windows Server 2016.

Here’s a scenario I’ve run into often, and it seems very few customers anticipate this ever happening.

The IT Director at XYZ, Inc. shares that they plan to stick with Windows Server 2012 for 5 years so SA doesn’t make sense.

2-3 years in, the company deploys a new version of SharePoint (although it could be any application) and decides to run it on Windows Server 2016 because they anticipate running that version of SharePoint for at least 5 years, maybe more.

Every employee will have access to SharePoint so now every user/device will require a new Windows Server CAL. Something that wouldn’t be in the budget for 2-3 more years.

This scenario has played out at countless companies. Sometimes it’s only caught during an audit, other times we’re able to catch it early on.

When you’re evaluating costs, make sure you consider this possibility. Also, don’t just look at 3-5 years because it’s highly unlikely that you’ll rip and replace all of your Windows Servers.

I recommend looking at costs over 6-9 years because, if you plan to be in business for a while, you’re likely to have Windows Server around for the life of your business.

This is just 1 reason I recommend you include SA. For more information on Windows Server 2016 SA Benefits check out my Ultimate Windows Server 2016 Licensing Guide.


These top 5 Windows Server 2016 licensing mistakes are easy to make. Issues with properly licensing/counting OSEs is far from new. I’ve seen it happen over and over again with earlier versions.

The same goes for High Availability scenarios, Windows Server CALs, and Software Assurance. These are all consistent scenarios that people run into issues with, and I don’t expect that to change.

The core counts are where I see a new issue, specific to Windows Server 2016. This is going to get very tricky and I anticipate even many “experts” getting this wrong for their customers.

Windows Server 2016

Windows Server 2016 Licensing Changes

In this video, I talk about the upcoming changes to Windows Server and System Center 2016.

Windows Server 2016 Moves To Per Core Licensing

Microsoft is shifting from a per processor to a per-core licensing model. Microsoft’s reason for this change is that it better aligns with the cloud and will make moving licenses between on-premises and the cloud simpler. (I’m sure it won’t hurt their revenues either)

This change impacts Windows Server, System Center, and the Core Infrastructure Server Suite (CIS), which is a bundle of the two products.

The new minimums are 8 cores per processor and 16 cores per server.
Standard and Datacenter editions will now have some different features which you can check out in more detail in the licensing datasheet linked to below.

Windows Server 2016 Nano Server

You may have heard of Nano Server. It’s not actually a separate edition, instead it’s a new headless deployment option for Windows Server, with a reduced footprint, ideal for modern apps it has lower servicing requirements and increased security.

Nano Server is also only available with Software Assurance (SA).

Microsoft continues to move more features, options, etc… into SA so be sure you’re up to date with the latest SA Benefits before buying any new licenses.

Windows Server CALs

Client Access Licenses (CALs) will still be required in 2016. If you have external users (non-employees) connecting to any of your Windows Servers you’ll still need to purchase External Connector licenses for each of those servers. If you’re running Remote Desktop Services (RDS), formerly Terminal Services, you’ll still need to purchase RDS CALs.

Core Grants

Microsoft will provide Core Grants for licenses with SA. You’ll have to inventory your server environment with a time & date stamp and be able to show the number of physical cores in use, that are licensed with SA, in order to receive the grant.

You can use your own tools for that or check out these tools from Microsoft:

If you’re running processors with more than 8 cores this will be especially important as you’ll be granted the delta of core licenses and only have to purchase SA for all cores.

Windows Server & System Center 2016 Licensing Resources:

Are your developers over licensed?

What are your developers working on?

Do they need Visual Studio Enterprise?

That’s pricey.

Maybe they could get away with Visual Studio Professional.

If so, that could save you a lot of money.

What if they just need the Dev Edition though?

That’s free. Now we’re talkin.

The funny thing about Microsoft licensing is that you can be both over buying and under licensed at the same time.

It’s one thing if you haven’t bought enough licenses.

At least then you haven’t been over paying. There’s still consequences of course, and that’s something you’d need to fix.

But over buying, buying higher editions than necessary, that’s a good way to flush money right down the drain.

And I’ve seen that with many products, Visual Studio included.

When one of your developers asks for a Visual Studio license, are you questioning what they need?

Are you asking them what they’ll be doing with that license?

And when it comes time to renew those licenses, are you making sure they’re all being used?

If you’re not, you could be leaving a lot of money on the table.

So, all you members will get a Visual Studio deep dive this week and learn more about the new licensing options.

Not a member yet?

you can learn more about membership and even sign up at http://www.volumelicensingcourse.com/group/

Here’s to savings.

How do you license your car?

Microsoft has sever licenses, device licenses, use licenses, but how do you license a car?

Microsoft has been involved with car companies like Ford and Toyota for years, but it looks like that’s just the beginning.

Microsoft and Toyota are teaming up for even more advances in car technology.


I wonder what happens if Toyota doesn’t renew they’re SA (Software Assurance).

Does your car start?

I hope the folks in the car biz have a good software advisor.

Not buying and managing Microsoft licenses for hundreds of thousands of cars?

Maybe you’re developing software for the car industry though. Our any industry.

If your are, then you probably have some Visual Studio licenses you’re working with.

Maybe you’re an MSDN subscriber too.

Are you familiar with Visual Studio 2017 licensing?

It just hit General Availability.

We’ll be covering the latest licensing model and subscription options this week.

If you’re not already a member, you can sign up at http://volumelicensingcourse.com/membership-accoun…

With Visual Studio Enterprise costing about $6,000, getting that licensing wrong is a big deal.

If you buy just one too many of those licenses, you could’ve paid for 5 years of membership in our group.

Still have questions about the group and the benefits of membership?

You can email me or head here – http://www.volumelicensingcourse.com/group/