Windows Server 2016 shipped in October 2016 as a foundational release: Microsoft switched the entire server line from per-processor to per-core licensing, introduced Storage Spaces Direct (hyper-converged storage out of local disks), shielded VMs (Hyper-V guarded fabric), native Docker-compatible Windows containers, Nano Server (the headless deployment option, later refocused to containers only), and Linux Integration Services that brought Linux guests to parity on Hyper-V. Mainstream support ended 11 January 2022; extended support runs to 12 January 2027.
Windows Server 2016 was the first release where every host needed a per-core licence count: minimum 16 cores per server, minimum 8 per processor. Organisations migrating from Server 2012 R2 (per-processor) needed to recount their estate carefully — a two-socket box with two 12-core processors went from two Datacenter licences to a 24-core licence stack, which sometimes raised the price meaningfully on dense hardware.
S2D in 2016 supported 2 to 16 nodes per cluster, mirror and parity resiliency, NVMe + SSD + HDD tiered storage, and ReFS for the storage volume. Hyper-V added rolling cluster upgrades (mix Server 2012 R2 and 2016 nodes during migration), nested virtualisation (a VM that runs VMs), production checkpoints, and shielded VMs that resist host-level admin tampering.
Standard, Datacenter, Essentials, Hyper-V Server. End of mainstream January 2022, end of extended January 2027. Extended Security Updates are available beyond that on a paid basis. Upgrade path: in-place upgrade to Server 2019 supported; to Server 2022 supported as a skip-version upgrade introduced in 2022.
Relative fit of each licensing channel for typical buyers of this product. Calibrate against your own scale and renewal strategy.
Server licensing is per-core with strict minimums, and almost every workload also needs Client Access Licences. Get the core math wrong and you either fail an audit or buy twice the licences you actually need.
The small set of decisions that determine whether you overpay, fail an audit, or land in the right place.
Three reference deployments — find the closest match and adapt rather than starting from zero.
None of these are tricks — they are the same levers Microsoft's own licensing specialists pull on every renewal.
These four signals show up in every counterfeit-licence case we have seen. If any of them is present, walk away — no discount makes it worthwhile.
OEM keys are distributed only pre-installed on hardware and stay bound to that device for life. A separately sold OEM key is almost certainly leaked, harvested from scrapped hardware, or fully counterfeit.
Microsoft entitlement always leaves a paper trail — a Volume Licensing Service Center record, a CSP invoice, a sealed Retail box with a COA, or a Microsoft Store order. No proof = no defence in an audit.
Classic symptom of a MAK key that has exceeded its activation pool, or a KMS key being abused outside its volume programme. Microsoft revokes these centrally; the activation grace period is short.
Legitimate CSPs and LARs transfer the licence into your Microsoft 365 / Azure / VLSC tenant under your domain. If the seller insists on activating 'for you' on their account, you do not own anything.
Quick definitions — the full glossary lives at /en/glossary if you need to dig deeper.