Skip to content

Windows Server 2025 editions and licensing: Standard, Datacenter and CALs

Verified 2 min read

What Standard and Datacenter actually license, how OSE counts and CALs work, and why the evaluation edition is the right lab start.

Tested onStandard / Datacenter · Build 26100.33650 · x64
E1
Build
26100.33650
Edition
Standard / Datacenter
Architecture
x64
Support
LTSC to 2034-11-14
Evidence
E1Official documentation
Verified
2026-10-27
Page type
Concept
  • Standard is for a host with light virtualization: it includes two OSEs only when the host does nothing but virtualize; if the host also runs roles such as DNS, you may run one OSE under that licence.
  • Datacenter is for dense virtualization: unlimited OSEs on the licensed host, plus Storage Spaces Direct and Storage Replica.
  • Both are licensed by core, not by processor, and CALs are separate for users/devices that access the server (with the usual exceptions).
  • For a lab: use the 180-day Evaluation. It is the legal, rebuildable path; do not use “rearm” scripts or KMS tools.
Dimension Standard Datacenter
Virtual OSEs on the licensed host 2 (host only virtualizes); 1 if the host also runs server roles Unlimited
Storage Spaces Direct No Yes
Storage Replica No Yes
Software-defined networking Limited Full
Shielded VMs / host guarding No Yes
Typical use Small office, single role, light VMs Private cloud, dense Hyper-V, S2D
Licensing basis Per core, plus CALs Per core, plus CALs
  1. Cores, not sockets. A 16-core host needs 16 cores of licence (subject to minimums and the agreement). Two 8-core CPUs are not “two licences” by themselves.
  2. OSE vs CAL. The OSE count is how many server instances the host licence covers. A CAL is how users/devices access the services. They are different meters.
  • Windows Server 2025 Evaluation is valid for 180 days.
  • It is not a production licence and cannot be “activated permanently”.
  • In the lab: install → snapshot → clone → record expiresAt → rebuild from the template before expiry.
  • If you need a longer-lived lab, use a licensed edition you actually own, or rebuild on a schedule.
  • Is the workload Standard-sized or Datacenter-sized?
  • How many cores does the host expose to the VM?
  • Will the host run other roles, or only virtualize?
  • Do you need S2D/Storage Replica, or just a file share?
  • Who accesses the server, and what CAL model applies?

Sources