Windows Server Core Licensing Explained Without the Spreadsheet Headache

Fix it now

License every physical core in the server, subject to two published minimums: 8 core licences per physical processor and 16 per server. Count physical cores, not logical processors and not virtual CPUs. Then remember the licences are sold in 2-packs and 16-packs, and that CALs are a separate line entirely.

1. Count the physical cores on the host, not inside a guest. Run Get-CimInstance Win32_Processor and read NumberOfCores per socket; NumberOfLogicalProcessors is higher wherever hyperthreading is on and is irrelevant to this calculation.
2. Apply the per-processor minimum: treat any processor with fewer than 8 cores as 8.
3. Apply the per-server minimum: if the total comes to fewer than 16, license 16.
4. Multiply for stacked instances on Standard. Microsoft’s Product Terms permit Standard in two OSEs on the licensed server, so four Windows virtual machines on a 16-core host is 32 core licences, not 16.
5. Compare against Datacenter before ordering if the virtual machine count is climbing, since Datacenter permits any number of OSEs on the licensed server for the same core count.
6. Add the CALs. Core licences cover the software on the hardware and grant nobody the right to connect; a server quote without CALs on it is not a server quote.

If you cannot license the host – someone else’s hardware – Microsoft’s per-virtual-machine option applies instead, with a minimum of 8 core licences per virtual machine, and a virtual core mapped to a hardware thread for licensing purposes.

If the count is settled and the CALs are on the quote, stop here. Below is the arithmetic worked through, the three mistakes that cost real money, and where Essentials removes the question entirely.

Why it happens

Windows Server is licensed by physical core, and the model is simpler than its reputation. Microsoft’s Product Terms state it in one sentence: the number of licences required equals the number of physical cores on the licensed server, subject to a minimum of 8 licences per physical processor and a minimum of 16 licences per server. The spreadsheet only appears because people count the wrong thing – logical processors instead of cores, or virtual CPUs instead of the hardware underneath them.

So the rule, stated properly and once: take the number of physical cores in the server; if any processor has fewer than 8 cores, treat it as 8; add the results together; and if the total is under 16, license 16. That number, and not the number of cores you plan to use, is what you buy. Licences are sold in 2-packs and 16-packs, so the total will always be even.

Nothing in this depends on the edition. Standard and Datacenter are licensed by the same core count with the same minimums; what differs is what the resulting licence entitles you to run. Microsoft’s Product Terms give Standard use of the server software in two OSEs on the licensed server and Datacenter any number of OSEs, with any number of Windows Server containers without Hyper-V isolation permitted on either. That is a decision made after the core count is settled, not instead of it.

One more rule to know before anything moves: Microsoft’s Product Terms state that a licence may be reassigned to another device or user, but not less than 90 days since the last reassignment of that same licence, with an exception for permanent hardware failure or loss. A planned migration to a replacement server is normally fine. Shuttling licences around a cluster week by week is not.

Full reference

Counting the cores on a machine you already have

PowerShell gives the authoritative answer, and it has to be run on the physical host rather than inside a virtual machine, because a guest sees only the virtual CPUs it was given. Microsoft documents NumberOfCores as the number of cores for the processor instance – a core being a physical processor on the integrated circuit – and NumberOfLogicalProcessors as the number of logical processors, which for hyperthreading-capable processors includes only the processors that have hyperthreading enabled. Microsoft also documents the comparison itself: if NumberOfCores is less than NumberOfLogicalProcessors, hyperthreading is enabled.

Get-CimInstance -ClassName Win32_Processor |
  Select-Object Name, NumberOfCores, NumberOfLogicalProcessors

(Get-CimInstance Win32_Processor | Measure-Object -Property NumberOfCores -Sum).Sum

Task Manager’s Performance tab shows the same thing for a quick look, with a cores figure and a higher logical processors figure below it on any machine with hyperthreading enabled. Use the command for anything you are going to put on an order. If the hardware does not exist yet, take the core count from the processor’s own specification sheet rather than from a configurator, which sometimes quotes threads.

Worked examples, including the ones that surprise people

Where the minimums come from, and why they will not be argued away

Without them, a single four-core box would be licensed at a quarter of the price of a sixteen-core one for software that behaves identically on both. The floor is deliberate, and its practical effect is that on any small server the first sixteen cores are the entry price and cores beyond that are incremental. It also means that the requirement is based on the physical cores present in the server rather than on how many are switched on – disabling cores in firmware does not reduce what you owe, though it is sometimes done for other software licensed by active core, which is where the idea comes from.

When you cannot license the host

Licensing by virtual machine is the exception rather than the default and exists mainly for hardware you do not control. Microsoft publishes a minimum of 8 core licences per virtual machine, and states that for licensing purposes a virtual core maps to a hardware thread – which is the one place in this model where threads matter at all. Count the virtual cores allocated to the machine, apply the minimum, and expect the per-unit result to be less favourable than licensing the host, because it is a fallback rather than a preference.

Where the question disappears entirely

For a small site, check Windows Server 2025 Essentials before doing any of this arithmetic. Microsoft publishes it as OEM only, for up to 25 users and 50 devices, covering up to 10 cores and 1 VM on single-socket servers, with access rights built in rather than requiring separate CALs. The Product Terms express the same limits as up to 25 user accounts, with the Connector software installed on no more than 50 devices, and use of the server software in the physical OSE and one virtual OSE.

Essentials being OEM only is the constraint that most often rules it out. It is bought with hardware rather than as a licence you can apply to a server you already own, so it is a decision to make at the point of buying the machine.

How to size an order, by situation

• A single small server for file, print and directory work: 16 core licences, whatever the processor turns out to be, plus CALs.
• A modest host running two Windows virtual machines on Standard: still 16 core licences if the box has 16 cores or fewer, plus CALs.
• A host running four or more Windows virtual machines: multiply for Standard, then compare the total against Datacenter at the same core count before ordering.
• A dual-socket machine with modest processors: check the per-processor minimum first, because eight per processor may be higher than the physical count.
• A very small business buying new hardware: check Windows Server 2025 Essentials at the point of ordering the machine, since it is OEM only and includes access rights.

The three mistakes that cost real money

1. Licensing virtual CPUs when the host is licensed. The count is the host’s physical cores and adding vCPUs to a guest changes nothing.
2. Forgetting the stacking arithmetic on Standard. Two OSEs per full set of core licences, so four instances is two sets.
3. Treating core licences as the whole purchase. They cover the software on the hardware and grant nobody the right to connect; CALs are a separate line and RDS CALs are additional again.

Questions people ask about this