Windows Servers licensing is not an easy concept to wrap your head around. Next to SQL Servers, it is one of the most complicated licensing models Microsoft has to offer, perhaps one of the most complicated licensing models period. It might be as entertaining as watching mud dry and as complicated as today’s political climate, it can be mastered with the right tools at your disposal.
At MetrixData 360, we specialize in the toughest licensing that software vendors can offer, even software as complicated as Windows Server. So, we thought we would go over some of the basics you will need to know when ensuring compliance with your Windows Server licensing.
What is Microsoft Windows Server?
Windows Server is an enterprise-class server operating system, with the purpose of sharing services with multiple users and providing administrative control over storage, applications, and corporate networks. Since its release in the early 2000s, Windows Server has served as a critical element in the software infrastructure of many organizations to this day. Among the current Windows Server editions, each has its own slightly different licensing metric. Due to the nature of these servers, it can often be quite difficult to license them and to ensure one is properly licensed.
Types of Windows Servers
Windows Server Essential
Ideal for anyone anticipating eventual mobility into the cloud, this server has built-in integration with Office 365 hosted services.
Windows Server Essential follows a Speciality Server licensing model, meaning it is licensed per server. The upfront cost for Windows Server Essential, which is significantly lower than the other models, is the majority of what you will have to pay for the server. It’s priced as such because Windows Server Essential is unique in that there is no need to buy additional users or device Client Access Licenses (CALs) after the initial purchase. Instead, the server has a cap limit on the number of users and devices that can access it.
Customers can choose between using up to 25 named user accounts or installing Windows Server Essential on no more than 50 devices. For this reason, it is best suited for smaller companies that have minimal anticipated growth over the next two to five years.
Windows Server Standard Edition
Proving the happy medium between Essential and Datacenter, Standard Edition offers a solution that is similar in function to Datacenter but is closer to the cost of Essential, making it suitable for a medium-sized company.
It offers the ability to run two virtual machines, along with fully integrated services and direct access for users. It follows a core-based licensing model and requires CALs. Due to this fact, purchasing a Standard edition is a little tricky, since you must purchase 16 cores per server and you will also require additional purchases if the number of cores per server is greater than 16. If a business requires more virtual machines than the two offered by the Standard edition, then the Datacenter edition should be considered.
Windows Server Datacenter Edition
The most advanced and expensive of the Windows Servers, the Datacenter Edition offers the ability to run an unlimited number of virtual machines and can effectively meet the demands of large enterprises with larger IT infrastructures. Just like the Standard Edition, the Datacenter Edition follows a core-based licensing model. The greatest drawback of the Datacenter Edition is its cost, which is roughly eight times the original price of the Standard Server.
What is a Core-Based Licensing Model?
If you have Windows Server Standard or Windows Server Datacenter editions, then you will have a core-based licensing model. A core-based licensing model means that the number of licenses that you need is determined by the number of server cores inside the number of processors.
This type of model was introduced in 2016 with Windows Servers, and this was done in order to provide a more consistent licensing metric across Cloud platforms and to allow for easier cloud mobility.
The three basic rules that you must adhere to with the core-based licensing model are as follows:
- Every processor must be licensed to cover a minimum of 8 cores
- Every server must be licensed to cover a minimum of 16 cores
- All physical cores in a server must be licensed
When adhering to the core-base licensing model, you will need to first have a base license that covers 16 cores. if your server has more than 16 cores, any additional cores will require additional licenses. All additional licenses come in increments of 2, 4, and 16 cores. Additional licenses are also required when using more than two virtual machines (VMs) on a Windows Server Standard edition.
No additional licenses are required for VM’s that are run on Windows Servers 2019 Datacenter. Should you be running an application on the Windows Server such as a SQL Server or an Exchange Server, then the general licensing rules for the server application must be applied.
Client Access Licenses (CAL) and Remote Desktop Service (RDS)
After you have your cores figured out, you will need additional Client Access Licenses (CALs) to cover every user or device which connects to the server. CALs are distributed based on unique persons, described as users, or devices. It should be noted that depending on whether you choose to license per user or per device can greatly influence the overall cost of your licenses.
CALs can be considered keys, in that every person or device will need their own separate key to access the server, which will require its own license in the same way that a door requires a key for its lock.
CALs come in packs of 1, 5, 10, or 50. Once a user or device is given a CAL, they will have access to any Windows Server of the same edition or lower, so long as the server software is running on Customer’s Licensed Servers.
For example, a user with a Windows Server CAL 2012 may access a Windows Server 2008 edition or a 2012 edition, however, they could not access a Windows Server 2016 edition. Mixing and matching Window Servers and CALs can become quite confusing and you should consult a licensing expert before configuring your licenses in such a manner.
Remote Desktop Service (RDS) CALs, previously known as Terminal Services, will also be needed for users or devices who wish to access programs or full desktops remotely. Both a CAL and an RDS will be required for remote desktops, with the only exception to this rule being if two users or devices are accessing a server software but only for administrative purposes in which case there is no need for either a CAL or RDS. An RDS will allow the remote access of applications for a wide range of devices and network connections.
Windows Servers in Azure
Microsoft’s cloud platform, Azure, has adopted the ability to license Windows Servers in its own complicated manner. There are many different ways to license your Windows Servers in Azure including but not limited to:
- Building Windows Servers directly into Azure through the use of Azure virtual machines: this can often be an easy solution to implement, but an expensive one, as the cost of Azure virtual machines will simply be added to your overall cloud spending, which can certainly accumulate without proper regulation to limit rampant spending.
- Hybrid Benefits: considered the new way to license, although, you will need to use your own activation method such as a KMS Server or a MAK key.
- A License in Windows Server Cannot Move within a 90-day Period: it is important to note that license mobility and SA benefits do not apply to Windows Servers.
Virtual Machines and Windows Server
Simply because a server is only virtual, it does not remove the need for a license, as virtual instances of Windows Server must be licensed under its host, and the host license must account for virtual machines.
In the scenario where clusters of virtual machines are free to move between hosts, all potential hosts must be licensed as if they were the current host. There is no need to count the host operating system or provide it with a license as long as the operating system is used only as the hypervisor to run the virtual instances.
The exception for this scenario, of course, is Windows Server Datacenter editions, where each host only needs to be covered with 16 licenses, this will give them the right to unlimited virtualization.
Stacking licenses is the practice of using multiple Windows Server Licenses, either Standard or Enterprise, in order to properly license multiple virtual machines over multiple hosts.
It can be quite difficult to figure out the correct number of licenses to fully cover a virtual server, however, when this limit is reached the licensed host is considered licensed for capacity; the same is applied to a host or cluster which is described as licensed for capacity when it has a finite number of virtual servers allotted to it.
Need Help With Your Windows Server Licensing?
Windows Servers are critical elements to your software environment; however, their usefulness shouldn’t be tempered by the difficulty surrounding their licensing. Having a strong understanding of what you need to buy and how best to buy it will give you the confidence you need when confronted by Microsoft’s sales reps.
At MetrixData 360, we specialize in difficult licensing structures, the likes of which would leave most people’s head spinning. Our licensing experts thrive in the most challenging of scenarios, and our SAM Tool is equipped to quickly handle the most complicated of Windows Server licensing scenarios.
If you would like to learn more about our services and how well we can help you license your servers in a way that can save you money while keeping you in compliance, you can check out our tool page using the link below.
