Windows Server 2012 (September 2012) and 2012 R2 (October 2013) were the last Windows Server releases licensed per processor. They introduced Storage Spaces (software-defined RAID), the new Server Manager, Hyper-V Replica, deduplication on NTFS volumes, ReFS as a new filesystem, and a major Hyper-V refresh. Both versions reached end of extended support on 10 October 2023 and are now only patched through the paid Extended Security Updates programme — free if the workload is hosted in Azure, paid through Volume Licensing for on-premises.
Datacenter (unlimited Hyper-V guests, per-processor licensing — two processors per licence), Standard (two guests per licence), Essentials (25 users, one server per domain), Foundation (15 users, OEM only). The per-processor model meant a two-socket physical host needed one Datacenter or Standard licence regardless of core count — a significant cost advantage on dense modern hardware that disappeared with the 2016 per-core transition.
Mainstream support ended 9 October 2018 (2012) / 9 October 2018 (2012 R2 — both aligned); extended support ended 10 October 2023. Extended Security Updates: years 1–3 (2023–2026) are sold through Volume Licensing; the same patches are delivered free to workloads hosted in Azure (including Azure VMware Solution and Azure Stack HCI). After ESU year 3 (October 2026), no further patches are planned outside Azure.
Direct in-place upgrade is supported one version at a time: 2012 → 2016 → 2019 → 2022 → 2025. Skip-version upgrades are not supported, but a wipe-and-replace migration with role re-installation is usually cleaner anyway for a 12-year-old operating system. Active Directory forest functional level upgrade should be planned as a separate workstream — domain controllers should not be upgraded in place if avoidable.
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.