Windows Server and virtualisation licensing basics
Server hardware is the easy part; the licensing that runs on it trips up more buyers than any component ever does. This is a plain-English primer on how Windows Server is licensed and how the main hypervisors compare. It is educational only — it deliberately contains no prices. Licences are quoted against current Microsoft and vendor price lists, so always confirm figures with a live quote before you commit.
Windows Server: core licences plus CALs
Since Windows Server 2016, Microsoft has licensed the operating system by physical core, and you also need Client Access Licences (CALs) for the people or devices that connect to it. They are two separate purchases.
Core licensing rules (Windows Server 2022 / 2025):
- You must license every physical core in the server.
- There is a floor: a minimum of 8 core licences per processor and 16 core licences per physical server — even a single-socket, low-core machine needs 16.
- Core licences are sold in packs of two and packs of 16; above the minimum you add cores in increments of two.
CALs. Both Standard and Datacenter require Windows Server CALs for every user or device accessing the server. You choose either User CALs (one per named person, any number of devices) or Device CALs (one per device, any number of users), and use a Windows Server External Connector for external/anonymous users. Specialised access such as Remote Desktop Services needs its own additional RDS CALs on top. CALs are entirely separate from the core licences that cover the server itself (Microsoft — Windows Server licensing).
Standard vs Datacenter: it comes down to virtualisation
Standard and Datacenter share the same core feature set. The decision is almost always about how many virtual machines you will run, plus a few software-defined datacentre features.
| Windows Server Standard | Windows Server Datacenter | |
|---|---|---|
| Virtualisation rights | Rights to run Windows Server in two OSEs (VMs) on a fully-licensed host | Unlimited Windows Server OSEs/VMs on a fully-licensed host |
| Scaling up | "Stack" a second full set of core licences for two more VMs, and so on | No stacking needed — unlimited |
| Storage Spaces Direct, Software-Defined Networking, Shielded VMs | Not included | Included |
| Best fit | Low-density or non-virtualised servers | Dense virtualisation, software-defined datacentre |
The mechanics: with Standard, once every physical core is licensed you may run the OS in up to two virtual machines (plus a host instance used only to manage Hyper-V). Need four VMs? Apply a second full set of core licences to the same server. With Datacenter, a fully-licensed host runs an unlimited number of Windows Server VMs — which is why densely-virtualised hosts standardise on it (Microsoft — Windows Server virtualisation rights). A useful rule of thumb: past roughly a dozen Windows VMs per host, Datacenter is usually the simpler and more economical route, but run the numbers for your exact core count.
One trap worth flagging: the guest OS is licensed regardless of the hypervisor. Running Windows Server VMs on VMware or Proxmox does not avoid Windows Server licensing — you still license the host's cores for the Windows guests (Datacenter for unlimited). The hypervisor licence and the Windows guest licence are two separate decisions.
The hypervisors at a glance
| Hypervisor | Licensing model | Notes |
|---|---|---|
| Microsoft Hyper-V | A role built into Windows Server — no separate product or price | Licensing is Windows Server licensing (Standard = 2 VMs, Datacenter = unlimited). The old standalone free "Hyper-V Server" product has been discontinued. |
| VMware vSphere (Broadcom) | Per-core subscription | Minimum 16 cores per CPU, and Broadcom set a 72-core minimum per subscription (from 2025). Sold as bundles (vSphere Standard/Foundation, VMware Cloud Foundation). |
| Proxmox VE | Open-source (AGPLv3), free to use — including commercially | An optional paid support subscription, priced per CPU socket, adds the stable "enterprise" update repository and vendor support. No feature-locked editions; every feature is in the free build. |
The VMware per-core minimums are Broadcom's (Broadcom — counting cores for VMware Cloud Foundation); Proxmox VE's open-source terms and per-socket support subscription are on the Proxmox site (Proxmox VE — open source).
How to think about it
- Size the OS by VM density. Two Windows VMs on a box → Standard. A dense virtualisation host → Datacenter.
- Remember CALs are separate from cores, and are per user or per device — plus extra CALs for services like Remote Desktop.
- License all physical cores, respecting the 8-per-processor / 16-per-server floor.
- Treat the hypervisor and the guest OS as two decisions. A free hypervisor (Proxmox, or Hyper-V bundled in Windows Server) still leaves your Windows guests to be licensed.
- Confirm current terms and pricing with a live vendor quote — licensing rules and minimums change, and this guide is educational, not a price list.
Server Hub can spec the server and the licensing together — see the servers and components in our catalogue.
The Server Hub briefing
South African IT hardware news, once a week.
What’s new, what it costs in rand, and what it means for the kit you run — servers and storage, networking, backup power, surveillance and print. Every claim checked against a named source.