Core-based licensing for deliberate infrastructure
Microsoft Windows Server 2022 Standard CPU Core Edition
A dependable LTSC server platform for physical servers and lightly virtualised environments—combining core infrastructure roles, Hyper-V, modern transport security, file services, containers and hybrid management pathways.
Choose the core quantity only after counting every physical core and applying Microsoft’s minimums. Then size Windows Server CALs, RDS CALs and any cloud services separately.
Read before choosing a quantity
“CPU Core” is a licence measure—not an installation mode
Three similarly named concepts solve different problems. Keeping them separate prevents the most expensive purchasing errors.
CPU-core licensing
Determines how many Windows Server core licences must be assigned to the physical server. Core packs are building blocks toward that total.
Server Core installation
A minimal installation option without the traditional desktop shell. It does not reduce the number of core licences or eliminate access CALs.
Client Access Licences
License users or devices to access Windows Server services in scenarios where CALs are required. They complement the server’s core licences.
Important purchasing boundary
A 2-core or 4-core selection is normally an add-on building block, not enough by itself to license a new physical server. Microsoft’s current per-core terms require all physical cores to be licensed, with minimums of eight core licences per physical processor and sixteen per server.
Count the hardware first
Turn a processor inventory into the correct core total
- Count physical processors in the server.
- Count physical cores in each processor; do not use threads or logical processors.
- Apply the eight-core minimum to every physical processor.
- Apply the sixteen-core minimum to the server.
- Acquire enough core licences to cover the resulting total.
- If Standard needs more than two OSEs, license the complete physical-core total again for each additional pair.
| Physical server | Installed physical cores | Minimum licensed total | Reason |
|---|---|---|---|
| 1 processor × 8 cores | 8 | 16 core licences | The sixteen-core minimum per server overrides the installed count. |
| 1 processor × 20 cores | 20 | 20 core licences | Every physical core is covered and both minimums are exceeded. |
| 2 processors × 6 cores | 12 | 16 core licences | Each processor is treated as at least eight cores. |
| 2 processors × 24 cores | 48 | 48 core licences | All installed physical cores must be covered. |
Illustrative, not a licence determination: confirm the acquisition channel, product terms and hardware inventory before ordering. Processor hot-add, failover rights, clusters and virtual-OSE licensing can introduce additional considerations.
Use the selector intelligently
Choose the pack combination that reaches the required total
The retailer currently offers 2, 4, 8, 16, 24, 32 and 64-core selections. Treat the selector as a way to assemble coverage—not as seven different Windows Server editions.
Starting a new server
Begin at sixteen cores even if the server contains fewer physical cores.
Adding coverage
Use smaller packs to cover cores above the base quantity or complete a server-wide re-licensing layer.
Adding VM rights
For two more Standard OSEs, assign another complete set covering every physical core—not merely two more core licences.
Preserve evidence
Keep the invoice, licence terms, product identifier, core calculation and activation records together.
Virtualisation rights
Standard is engineered for light virtualisation
It can be economical when the host needs only a small number of Windows Server OSEs. As density grows, compare the cost of repeatedly licensing every physical core with Datacenter’s unlimited OSE rights.
Hyper-V included
Deploy supported Windows and Linux virtual machines, virtual switches, checkpoints and familiar Hyper-V management workflows.
Two OSEs per full layer
One fully licensed server permits two Standard OSEs. A physical instance may run in addition only when used solely to host and manage the virtual OSEs.
Container distinction
Standard permits unlimited Windows Server containers without Hyper-V isolation, but Hyper-V-isolated containers count within the two-OSE limit.
Activation is not the same as licensing
Automatic Virtual Machine Activation is a Datacenter-host capability. Product keys, KMS, MAK and AVMA are activation mechanisms; none increases the number of OSEs licensed on a Standard host.
Choose at installation
Server Core or Desktop Experience
The edition and licence calculation remain the same, but the operational model changes. Microsoft does not support converting between these installation options after setup; changing later requires a clean installation.
Server Core
Smaller footprint and reduced attack surface, managed with PowerShell, SConfig and remote tools. Some roles and graphical components are unavailable.
Desktop Experience
Includes the familiar graphical shell and broader local application compatibility, with a larger footprint and more installed components.
Windows Admin Center
Manage servers, roles, certificates, storage, updates and Hyper-V through a modern browser-based administration surface.
PowerShell automation
Script repeatable configuration, inventory, deployment and operational tasks across local and remote servers.
Infrastructure platform
Build the roles organisations still depend on
Windows Server 2022 Standard is strongest as a disciplined foundation: identity, name and address services, file and print, web hosting, Hyper-V, containers, remote administration and hybrid connection points.
Availability of a role does not mean every deployment is automatically licensed or supported. Validate application, hardware, CAL and edition dependencies before rollout.
Identity and policy
Active Directory Domain Services and Group Policy for central authentication, resource discovery and configuration control.
Network services
DNS, DHCP, IPAM, routing and remote-access roles for controlled address, name and connectivity services.
File and storage
SMB shares, DFS, quotas, Data Deduplication, ReFS options, iSCSI and Storage Migration Service in supported configurations.
Hybrid pathways
Connect eligible servers to Azure Arc and separately provision Azure management, backup, monitoring or migration services where appropriate.
Layered protection
Security that starts before the operating system
Windows Server 2022 introduced stronger boot, transport and file-protocol protections, but the most advanced secured-core controls depend on compatible certified hardware and deliberate configuration.
Secured-core server
Hardware-backed root of trust, firmware defence, VBS and HVCI on compatible systems.
Trusted boot chain
TPM 2.0, Secure Boot, DRTM and DMA protection underpin stronger secured-core configurations.
TLS 1.3
Enabled in the protocol layer by default; applications and services must also support and negotiate it.
SMB AES-256
AES-256-GCM and AES-256-CCM are available for SMB 3.1.1 when peers and policy support them.
SMB compression
Compress supported file transfers in transit to reduce network payload on slower or congested links.
Storage Replica—limited in Standard
One partnership, one resource group and a single volume up to 2 TB; Datacenter removes those Standard limits.
Defender distinction
Microsoft Defender Antivirus is included. Do not assume a paid Microsoft Defender for Endpoint plan is included with this licence.
Edition decision
Windows Server 2022 Standard vs Datacenter
Most core infrastructure roles overlap. The decisive differences are virtualisation density and software-defined datacentre capabilities.
| Decision factor | Standard | Datacenter |
|---|---|---|
| Core licensing minimum | All physical cores; 8 per processor and 16 per server minimum | Same physical-core minimum |
| Virtual OSE rights | Two per complete server-wide licensing layer | Unlimited on the fully licensed server |
| Hyper-V-isolated containers | Two | Unlimited |
| Windows containers without Hyper-V isolation | Unlimited | Unlimited |
| Storage Replica | One partnership and resource group; one volume up to 2 TB | Unlimited |
| Storage Spaces Direct | Not included | Included |
| Network Controller role | Not included | Included |
| Host Guardian Hyper-V support | Not included | Included |
| Typical fit | Physical roles and lightly virtualised infrastructure | Dense virtualisation and software-defined datacentre |
Not Standard 2022 features: SMB over QUIC and hotpatching belong to Windows Server 2022 Datacenter: Azure Edition scenarios, not this Standard offer.
Generation decision
Windows Server 2022 Standard vs Windows Server 2025 Standard
Choose 2022 for a validated 21H2-era application estate or an established compatibility baseline. Choose 2025 for a new deployment that benefits from the newer platform and the longer published lifecycle.
| Decision area | Windows Server 2022 Standard | Windows Server 2025 Standard |
|---|---|---|
| Lifecycle start | 18 August 2021 | 1 November 2024 |
| Mainstream support ends | 13 October 2026 | 13 November 2029 |
| Extended support ends | 14 October 2031 | 14 November 2034 |
| Best reason to choose | Application, vendor or operational standardisation already proven on 2022 | Longer planning horizon and newer server-platform capabilities |
| Migration requirement | Validate application support, drivers, firmware, backup, security tooling, clustering and licensing before deciding. | |
Access licensing
The server licence, base CALs and RDS CALs solve different layers
1. Server core licences
License the physical processing capacity and establish the Standard edition OSE rights.
2. Windows Server CALs
Normally required for users or devices accessing server software, subject to Product Terms exceptions such as qualifying web workloads.
3. Additive RDS CALs
Required in addition to base Windows Server CALs for users or devices connecting to an RDS Session Host for desktops or applications.
Do not infer included CAL quantities
The current retailer CPU-core page does not clearly establish an included bundle of Windows Server or RDS CALs. Confirm any included access rights in writing before purchase.
Deployment planning
Minimum hardware is an installation floor—not a capacity plan
Server roles, virtual machines, storage, backup, security agents and recovery objectives determine the real design.
| Component | Microsoft baseline | Planning guidance |
|---|---|---|
| Processor | 1.4 GHz 64-bit x64; NX/DEP, CMPXCHG16b, LAHF/SAHF, PrefetchW, SLAT, SSE4.2 and POPCNT | Confirm CPU generation, firmware, virtualisation extensions and vendor support. |
| Memory | Microsoft’s consolidated documentation lists release-specific minimums; allocate at least 2 GB and more for Desktop Experience | Size for roles and VMs; use ECC or similar protection on physical hosts. |
| System storage | 32 GB absolute minimum | Provide substantially more for updates, paging, dumps, logs, roles and recovery. |
| Network | PCIe-compatible Ethernet capable of at least 1 Gbps | Design redundancy and throughput for storage, backup, VM and application traffic. |
| Secured-core hardware | IOMMU, Kernel DMA Protection, DRTM, TPM 2.0, Secure Boot and VBS support | Use certified hardware and verify every required feature is enabled. |
| Installation option | Server Core or Server with Desktop Experience | Choose before installation; switching requires a clean install. |
Fixed Lifecycle
Plan the transition to Extended Support now
Mainstream support ends on 13 October 2026. Extended support runs through 14 October 2031 and focuses on security updates rather than design changes, new features and normal non-security updates.
Keep Windows Server fully updated, monitor Microsoft’s release-health guidance and establish the next migration checkpoint before application or hardware support becomes the limiting factor.
Lifecycle checkpoint
- Start: 18 August 2021
- Mainstream end: 13 October 2026
- Extended end: 14 October 2031
- Container images follow the Windows Server 2022 lifecycle.
Order workflow
Move from server inventory to a defensible purchase
Inventory
Record processors, physical cores, planned OSEs, cluster nodes, users, devices and RDS users.
Calculate
Apply processor and server minimums, then add full licensing layers for extra OSE pairs.
Confirm
Verify licence channel, CALs, activation, transfer rights, media, language and region in writing.
Deploy
Test applications and recovery, choose the installation option, update fully and preserve records.
Software Mart Australia
Digital fulfilment with support context
The retailer advertises electronic delivery and remote installation assistance. Confirm the exact delivery time, activation method, licensing documentation and support scope for the selected core option before checkout.
Electronic delivery
Prepare the Microsoft account, deployment window, backup plan and server inventory before the order arrives.
Remote assistance
Clarify whether support covers download, installation and activation only or also role configuration, migration and troubleshooting.
Licence verification
Confirm the actual offer—not only the product name
Request written confirmation of these points
- The precise Microsoft product identifier, licence channel and proof of entitlement.
- Whether the chosen quantity is a complete base licence or an add-on core pack.
- Perpetual or subscription term, assignment, reassignment, transfer and downgrade rights.
- Activation method, download media, language, region restrictions and replacement process.
- Any included Windows Server CALs, RDS CALs, Software Assurance, Azure benefits or support incidents.
- Whether the licence can be used for the intended physical server, virtualisation host or cloud scenario.
Identifier warning: the retailer currently displays UPC 889842425611, a number publicly associated with Windows Server 2019 Standard 16 Core. Verify it before using the identifier in feeds, invoices or structured data.
Frequently asked questions
Windows Server 2022 Standard CPU Core: 30 practical answers
1. What does CPU Core Edition mean?
It means the server licence quantity is measured against physical processor cores. It is not a separate technical edition and does not force a Server Core installation.
2. Is a 2-core selection enough for a new server?
No. Microsoft applies a minimum of sixteen core licences per server and eight per physical processor. A 2-core pack is generally a building block.
3. Do I count logical processors or threads?
No. Under the physical-core model, count physical cores in each physical processor, then apply Microsoft’s minimums.
4. How many cores must a single 8-core CPU server license?
Sixteen, because the sixteen-core server minimum is higher than the installed physical-core count.
5. How many cores for two 6-core processors?
Sixteen. Each processor is treated as at least eight cores, producing a sixteen-core licensed total.
6. Does Standard include two virtual machines?
A complete licensing layer permits two operating system environments. The physical instance may run additionally only when used solely to host and manage the virtual OSEs.
7. How do I license four Windows Server VMs?
For Standard, assign another complete set of core licences covering every physical core to gain rights for two additional OSEs.
8. When is Datacenter more economical?
When VM density or software-defined datacentre features make repeated Standard licensing layers less practical than Datacenter’s unlimited OSE rights.
9. Does Standard include Hyper-V?
Yes. Hyper-V is available, subject to compatible hardware, role configuration and the applicable licensing rights.
10. Are Windows containers unlimited?
Containers without Hyper-V isolation are unlimited. Standard allows up to two Hyper-V-isolated containers within its OSE limit per licensing layer.
11. Does the core licence include Windows Server CALs?
Do not assume so. Base User or Device CALs are normally separate and should be confirmed for the offer.
12. Do I also need RDS CALs?
Yes for users or devices connecting to an RDS Session Host for desktops or applications. RDS CALs are additive to base Windows Server CALs.
13. What is a User CAL?
It licenses one assigned user to access the corresponding server version or earlier versions from their devices, subject to the applicable terms.
14. What is a Device CAL?
It licenses one assigned device to access the corresponding server version or earlier versions by its users, useful for shared workstations.
15. Is Server Core required?
No. Standard offers Server Core and Server with Desktop Experience installation choices.
16. Can I switch from Server Core to Desktop Experience later?
No in-place conversion is supported. Changing the installation option requires a clean installation.
17. Does it include Active Directory?
Yes. Active Directory Domain Services, Group Policy and related identity roles are available.
18. Does it include file and print services?
Yes, including SMB file services, DFS capabilities, quotas, print roles and Storage Migration Service in supported configurations.
19. Is Data Deduplication available in Standard?
Yes. Microsoft’s edition comparison lists Data Deduplication for both Standard and Datacenter.
20. Does Standard include Storage Spaces Direct?
No. Storage Spaces Direct is a Datacenter capability in Windows Server 2022.
21. What is the Standard Storage Replica limit?
One partnership and one resource group with a single volume up to 2 TB.
22. Does it support TLS 1.3?
Yes. TLS 1.3 is enabled in the protocol layer by default, but applications and services must also support it.
23. Does it support SMB AES-256 encryption?
Yes, with AES-256-GCM and AES-256-CCM when compatible peers and policy negotiate or require those ciphers.
24. Is SMB over QUIC included?
Not in Windows Server 2022 Standard. In the 2022 generation it is associated with Datacenter: Azure Edition.
25. Is hotpatching included?
Not as a Windows Server 2022 Standard feature. Microsoft documents 2022 hotpatching for Datacenter: Azure Edition scenarios.
26. Is Microsoft Defender for Endpoint included?
Do not assume so. Microsoft Defender Antivirus is included; Defender for Endpoint is a separate service entitlement.
27. Can I connect it to Azure Arc?
Yes in supported scenarios. Azure subscriptions, paid services, network access and organisation policy remain separate considerations.
28. What is the support lifecycle?
Mainstream support ends 13 October 2026 and extended support ends 14 October 2031.
29. Should a new deployment choose Server 2025 instead?
Compare application certification, hardware, migration risk and lifecycle. Server 2025 has a longer published support horizon; Server 2022 may fit a validated existing estate.
30. What records should I keep?
Retain the invoice, product identifier, licence terms, hardware inventory, core calculation, CAL inventory, activation records and seller confirmation together.
License the hardware. Clarify access. Deploy with evidence.
Build a Windows Server 2022 Standard purchase you can defend
Count the physical cores, determine the OSE requirement, size base and RDS CALs separately, confirm the licence channel and preserve the calculation.
