
Short answer: Windows Server 2022 Standard and Datacenter run the same operating system. The differences are virtualization rights and a few software-defined datacenter features. Standard licenses two virtual machines (OSEs) per fully licensed server, and you can stack additional Standard licenses for more VMs. Datacenter licenses unlimited VMs on the licensed host and adds Storage Spaces Direct, Software-Defined Networking, full Storage Replica and Shielded VMs. Datacenter costs roughly five to six times as much, so it usually pays off at around ten to twelve or more VMs per host.
Picking the wrong edition is one of the most expensive Windows Server mistakes: either you overpay for Datacenter on a small server, or you under-license a virtualization host and face an audit gap. This guide explains the feature differences, how core-based licensing works, the break-even point for VMs, and support dates for Windows Server 2022.
Windows Server 2022 editions compared
| Capability | Standard | Datacenter |
|---|---|---|
| Core Windows Server features (AD DS, DNS, DHCP, file, print, IIS, Hyper-V role) | Yes | Yes |
| Virtual machines (OSEs) per licensed server | 2 | Unlimited |
| Hyper-V containers | 2 | Unlimited |
| Windows Server containers | Unlimited | Unlimited |
| Storage Spaces Direct | No | Yes |
| Software-Defined Networking (Network Controller) | No | Yes |
| Storage Replica | Limited (1 partnership, single resource group, volume up to 2 TB) | Full |
| Shielded VMs and Host Guardian Service | No | Yes |
| Secured-core server and TLS 1.3 | Yes | Yes |
| Hotpatching (reboot-less security updates) | Datacenter: Azure Edition only | Datacenter: Azure Edition only |
| Licensing model | Per core + CALs | Per core + CALs |
Microsoft documents the full matrix in its Windows Server 2022 editions comparison.
How Windows Server core licensing works
Both editions use the same licensing rules:
- License every physical core in the server.
- Minimum 8 core licenses per processor and 16 core licenses per server, even if the server has fewer cores.
- Core licenses are sold in 2-core packs (and commonly as 16-core bundles).
- Client Access Licenses (CALs) are required for each user or device that accesses the server, unless an exemption applies. Remote Desktop Services needs separate RDS CALs.
Example: a single-socket server with 12 cores
You still need 16 core licenses because of the per-server minimum. A 16-core Standard license covers it and grants two VMs.
Example: a dual-socket server with 2 x 16 cores
You need 32 core licenses: two 16-core Standard licenses or two 16-core Datacenter licenses. With Standard, licensing all 32 cores once gives two VMs; licensing them twice gives four VMs.
Standard vs Datacenter: the VM break-even point
With Standard, every additional set of two VMs requires licensing all cores of the host again. With Datacenter, licensing all cores once allows unlimited VMs.
| VMs on a 16-core host | Standard licenses needed (16-core each) | Datacenter licenses needed |
|---|---|---|
| 2 | 1 | 1 |
| 4 | 2 | 1 |
| 6 | 3 | 1 |
| 10 | 5 | 1 |
| 12 | 6 | 1 |
| 20 | 10 | 1 |
Because a Datacenter license costs roughly five to six times a Standard license at Microsoft list prices, the cross-over usually falls around 10 to 12 Windows Server VMs per host. Above that, Datacenter is cheaper; below it, Standard is.
Remember to count only Windows Server VMs. Linux VMs on the same Hyper-V or VMware host do not consume Windows Server OSE rights.
When Standard is the right choice
- A physical server running one or two roles (domain controller, file server, application server)
- A small Hyper-V host with up to about ten Windows Server VMs
- Branch office servers
- Lab servers with few VMs
Vaneyo lists Windows Server 2022 Standard and a 16-core Standard license.
When Datacenter is the right choice
- Virtualization hosts running many Windows Server VMs
- Hyper-converged clusters using Storage Spaces Direct
- Environments requiring Shielded VMs for compliance
- Hosts where VMs move frequently between cluster nodes (each node must be licensed for the VMs it may run)
See Windows Server 2022 Datacenter and the 16-core Datacenter license.
Windows Server 2022 support dates
| Milestone | Date |
|---|---|
| Release | August 2021 |
| Mainstream support ends | October 13, 2026 |
| Extended support ends | October 14, 2031 |
Windows Server 2022 moved to extended support in October 2026: security updates continue until October 14, 2031, but new features and non-security fixes are no longer delivered. Check Microsoft’s Windows Server 2022 lifecycle page. For new deployments, compare with Windows Server 2025 in our guide Windows Server 2025 Standard vs Datacenter.
Clusters and VM mobility
In a failover cluster, licensing follows the VMs. If a Standard-licensed node may host six VMs after a failover, it must be licensed for six VMs. This is why Datacenter is common on cluster nodes even when the average VM count is moderate. Planning for the worst-case failover avoids under-licensing.
Can you switch from Standard to Datacenter?
Yes. Windows Server supports an in-place edition upgrade from Standard to Datacenter using DISM:
DISM /online /Set-Edition:ServerDatacenter /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEula
The server restarts and keeps its roles and data. Downgrading from Datacenter to Standard in place is not supported. Test edition changes on a non-production server first, especially on domain controllers.
CALs: the part people forget
Every user or device accessing Windows Server needs a Windows Server CAL of the same or newer version. Choose User CALs when people use several devices, or Device CALs for shared devices such as shift-work terminals. Remote Desktop users need RDS CALs in addition. CAL requirements are the same for Standard and Datacenter.
Hyper-V vs VMware: does the hypervisor change licensing?
No. Windows Server VM rights depend on the physical host’s cores and the edition licensed, not on which hypervisor you use. A VMware ESXi or Proxmox host running six Windows Server VMs needs the same Windows Server licensing as a Hyper-V host running six VMs. The only difference with Hyper-V is that the Windows Server installation used as the host itself does not consume a VM right when it runs only the Hyper-V role and management tools.
Worked example: a three-node cluster with 40 VMs
Suppose each node has two 12-core processors (24 cores) and the cluster runs 40 Windows Server VMs that can fail over to any node.
- Core licenses per node: 24 physical cores, which is above the 16-core minimum, so 24 core licenses per licensing pass.
- With Standard: each node must be licensed for every VM it could host. For 40 VMs that means 20 passes of 24 core licenses on each node, which is impractical and very expensive.
- With Datacenter: one pass of 24 Datacenter core licenses per node covers unlimited VMs. Three nodes x 24 cores = 72 Datacenter core licenses.
This is why virtually every production Hyper-V or VMware cluster running Windows workloads uses Datacenter.
Worked example: a small office server
A single-socket 8-core server runs Active Directory, file sharing and one line-of-business application in two VMs.
- Core licenses: 16 (the per-server minimum), even though the server has 8 cores.
- Edition: Standard, which covers the two VMs.
- CALs: one Windows Server User CAL for each of the office’s employees.
Datacenter would cost several times more and bring nothing this office uses.
Before you buy: a quick checklist
- Count physical cores per host and apply the 16-core and 8-per-processor minimums.
- Count Windows Server VMs per host, including worst-case failover.
- Decide whether you need Storage Spaces Direct, SDN or Shielded VMs.
- Add Windows Server CALs, plus RDS CALs for remote desktop users.
- Keep license documentation per host for audits.
Key terms explained
- OSE (Operating System Environment): an instance of Windows Server running on physical hardware or in a virtual machine; licensing counts these.
- Core license: the unit of Windows Server licensing; every physical core must be covered, with a 16-core minimum per server.
- CAL (Client Access License): a license for a user or device to access Windows Server services.
- Storage Spaces Direct: Datacenter’s software-defined storage that pools local disks across cluster nodes.
- Shielded VM: a Datacenter feature that encrypts and protects virtual machines from compromised hosts or administrators.
Common mistakes
- Buying an 8-core license for an 8-core server. The minimum is 16 core licenses per server.
- Counting VMs per cluster instead of per host. Each host must be licensed for the VMs it can run.
- Choosing Datacenter for a single physical server with no virtualization.
- Forgetting CALs and RDS CALs.
- Assuming Linux VMs count toward Windows Server VM limits. They do not.
Final takeaway
Choose Standard for physical servers and small virtualization hosts, and Datacenter once a host runs more than about ten to twelve Windows Server VMs or needs Storage Spaces Direct, SDN or Shielded VMs. Whichever you choose, license every core with the 16-core minimum and budget for CALs.
Frequently asked questions
What is the difference between Windows Server 2022 Standard and Datacenter?
Both have the same core operating system. Standard allows two virtual machines per fully licensed server, while Datacenter allows unlimited virtual machines and adds Storage Spaces Direct, Software-Defined Networking, full Storage Replica and Shielded VMs.
How many VMs can I run with Windows Server 2022 Standard?
Two Windows Server virtual machines per server when all physical cores are licensed. You can license all cores again to add two more VMs each time.
When is Datacenter cheaper than Standard?
Datacenter usually becomes cheaper at around ten to twelve or more Windows Server VMs on the same host, because one Datacenter license covers unlimited VMs while Standard requires relicensing all cores for every two VMs.
How many core licenses do I need for Windows Server 2022?
License every physical core, with a minimum of 8 core licenses per processor and 16 per server.
When does Windows Server 2022 support end?
Mainstream support ended on October 13, 2026, and extended support with security updates continues until October 14, 2031.
