Buying guide

Windows Server licensing — the plain-English guide

Cores, CALs, Standard vs Datacenter, virtualization rights — Windows Server licensing demystified with real-world examples.

Two pieces: the server + the CALs

Windows Server is licensed in two parts. First you license the server itself — by physical cores, in 16-core minimum packs. Then you license every user or device that connects to it with a Client Access License (CAL).

Without both pieces, you're out of compliance even if everything technically works. Microsoft's licensing audits do happen.

Step 1 — License the server cores

Count physical cores across all CPU sockets. Minimum 8 cores per socket, minimum 16 cores per server. Round up. Then pick the edition.

  • · Standard — 2 virtual instances (OSEs) per license. Stack licenses to add more VMs.
  • · Datacenter — unlimited OSEs on the licensed hardware. Adds Shielded VMs, SDN, Storage Spaces Direct.
  • · Essentials — single-server, max 25 users / 50 devices, no CALs required.

Step 2 — License the users (or devices)

Pick User CALs (per named user, any device) or Device CALs (per shared device, any user). Pick whichever model produces the lower count.

Rule of thumb: knowledge workers with multiple devices → User CALs. Shift workers sharing a workstation → Device CALs.

Step 3 — Add RDS CALs if you run Remote Desktop

Remote Desktop Services (formerly Terminal Services) requires an additional RDS CAL on top of the standard CAL for every connecting user or device.

You cannot share standard CALs and RDS CALs across the User and Device models — pick one model per CAL type.

A worked example

Small business with 1 Hyper-V host (16 cores, 2 CPUs), running 4 VMs. 20 employees, each with a laptop. 5 of them connect via Remote Desktop.

  • · 2 × Windows Server 2022 Standard (16-core packs) → 4 OSEs covered.
  • · 20 × Server User CALs.
  • · 5 × RDS User CALs for the RDS users.

Recommended licenses

More guides