Windows Server Licensing in 2026: Core Licensing Explained Simply

Windows Server licensing moved to a core-based model back with Server 2016, and it still catches people out because the old “per processor” mental model doesn’t map cleanly onto it. Here’s the plain-English version without the marketing language. The core-based licensing basics Every physical server needs licenses covering all physical cores, with a minimum of […]

Windows Server Licensing in 2026: Core Licensing Explained Simply

Windows Server licensing moved to a core-based model back with Server 2016, and it still catches people out because the old “per processor” mental model doesn’t map cleanly onto it. Here’s the plain-English version without the marketing language.

The core-based licensing basics

Every physical server needs licenses covering all physical cores, with a minimum of 8 core licenses per physical processor and 16 core licenses per server, regardless of actual core count if it’s lower. Core licenses are sold in packs of 2, so a typical dual-processor server with 8 cores each needs 8 packs (16 core licenses) at minimum, even if you’d technically only need fewer based on actual usage.

Standard vs Datacenter. The real difference isn’t features

Both editions have essentially the same feature set for most purposes (Datacenter adds Storage Spaces Direct, Shielded VMs, and a few other enterprise features). The real practical difference is virtualization rights: Standard licensing covers up to 2 virtual machines (or Hyper-V containers) per licensed server; Datacenter covers unlimited VMs on that same physical hardware. If you’re running more than 2 VMs per host, Datacenter often works out cheaper than buying multiple Standard licenses to cover the same host.

Client Access Licenses (CALs) are separate and easy to forget

Core licenses cover the server itself; every user or device connecting to services on that server (file shares, print services, remote desktop, etc.) also needs a CAL, licensed either per-user or per-device. This is the part most commonly missed in licensing audits. Buying enough core licenses for the server doesn’t automatically cover the clients accessing it.

When to actually get advice

This covers the fundamentals, but licensing rules change and have edge cases (Software Assurance benefits, Azure Hybrid Benefit, specific rules for service providers). For anything beyond a straightforward single-site deployment, or before a significant purchase, get a quote and clarification from a licensed Microsoft reseller rather than relying solely on general guides like this one. Licensing terms are exactly the kind of thing that changes between agreement types and reseller-specific programs.

For official guidance, see Microsoft’s Windows Server documentation.

🛠️

Gear We Recommend

Testing configs is easier with a dedicated admin machine set up right. Here’s the kit we use.

Browse our Windows Admin Toolkit picks on Amazon

As an Amazon Associate, TechyGeeksHome earns from qualifying purchases.


Discover more from TechyGeeksHome

Subscribe to get the latest posts sent to your email.

Andrew Armstrong

Andrew Armstrong is a UK-based IT professional with 26+ years of hands-on experience in Windows, Windows Server, SCCM/ConfigMgr, Intune, Active Directory, PowerShell and enterprise infrastructure.

He founded TechyGeeksHome in 2010 and has published 770+ practical guides to real-world IT problems. He also builds free Windows utilities, including Ultimate Settings Panel, which has been downloaded over 850,000 times.