Windows Server 2016 moved Standard and Datacenter Edition from processors to physical cores, with two-core packs and per-server minimums. Ten years on, that model still governs how Microsoft server licensing is counted — and it is still counted wrong.
Windows Server 2016 was the release where Microsoft stopped licensing servers by processor and started licensing them by core. That change is now a decade old and thoroughly bedded in — which is precisely why it is worth understanding properly. It is no longer news, so nobody re-reads the rules, and the counting errors it produces have had ten years to accumulate.
Alongside a new release of Windows Server and System Center, Microsoft used the 2016 wave to change how both were packaged and licensed. Datacenter Edition also picked up software-defined datacentre capabilities aimed at heavily virtualised private and hybrid environments, widening the gap between the editions beyond the virtualisation rights that had previously distinguished them.
The licensing change itself was the more consequential part. Standard and Datacenter Edition moved from a processor-based model to one based on physical cores. The stated rationale was consistency: cores are the currency of public cloud, so licensing on cores aligns private and public deployments and makes multi-cloud comparisons possible without a conversion step.
The mechanics are specific, and this is where organisations get it wrong.
The two floors are the part that catches people. A single-processor, four-core server does not need four cores licensed. It needs sixteen. Conversely, a dual-socket machine with high core counts needs every physical core licensed before Standard Edition’s two-OSE right applies at all — licensing “enough” cores to cover the workload does not get you there.
Both editions still require Windows Server CALs for every user or device accessing the server. Core licences cover the server; they do not cover access to it.
Some functionality additionally requires an additive CAL — a CAL you need in addition to the Windows Server CAL to use a particular capability. Remote Desktop Services and Active Directory Rights Management Services are the common examples. These are routinely missed, because the underlying server is correctly licensed and the deficiency only exists one layer up.
The transition Microsoft announced in 2016 is long finished. Core-based licensing carried straight through the 2019, 2022 and 2025 releases, and the counting rules above are now simply how Microsoft server licensing works rather than a change anyone is adapting to.
Windows Server 2016 itself is at the end of its life. Mainstream support has been over for years and extended support finishes in January 2027 under Microsoft’s lifecycle policy. If you are still running it, the licensing question and the migration question have become the same question — and the core counts on whatever you move to will be decided by hardware you are about to choose.
Correct core licensing depends on facts about physical hardware that most software inventories do not hold properly: how many physical processors are in the machine, how many physical cores each one has, whether the workload is virtualised, and which host it can move to.
That last point is the expensive one. In a cluster, licensing follows the hosts a virtual machine can run on, not the host it happens to be running on this afternoon. An unrestricted VM in an eight-node cluster is a very different licensing position from the same VM pinned to two nodes, and nothing about the guest operating system tells you which you have.
CerteroX SAM licenses Windows Server and SQL Server on cores and processors with cluster and virtualisation awareness, alongside device CALs, user CALs, named user and external connectors. Assignment types cover per device, per processor and per core, and entitlement is captured through Microsoft Licence Statement import and volume, retail, OEM and full packaged product transactions. Underneath it, CerteroX ITAM inventories the physical hosts and the virtualisation layer — VMware, Hyper-V, Citrix XenServer, Nutanix and the rest — so the core counts come from measurement rather than from a spreadsheet someone maintained in 2019.
The hard part of Microsoft licensing has never been the desktop. It is the server room, and specifically it is the relationship between guests, hosts and clusters. Understand the rules above, then make sure something is checking them against what you actually run.
To see Windows Server and SQL Server licensing calculated with cluster and virtualisation awareness rather than from a spreadsheet, book a demo.
Other posts covering the same ground.
An Oracle Unlimited Licence Agreement is only unlimited within its clauses. What certification actually asks of you, where toxic consumption creeps in, and why the measurement work has to start at the beginning of the term rather than the last six months.
Microsoft's August 2025 Product Terms changes: Extended Term standardised across programmes, Exchange and Skype for Business Server Subscription Editions, the Exchange and Windows 10 ESU programmes, and the Dynamics 365 F&O enforcement dates.
Renew, rescope or exit — an Oracle ULA gives you three routes and a narrow window to choose between them. The questions to settle first, and a six-point health check to see how ready you actually are.
Everything argued above is checkable. Name the publisher, the billing account or the platform you would argue with, and the session is built around it — the reasoning attached, not a summary slide.
No gated download at the end of it.