Windows Server 2025 Standard for a small office
Windows Server 2025 Standard is licensed per physical core, with at least 16 core licences per server, and licensing every core covers two virtual machines. Each user or device that connects to it also needs a Client Access Licence. Microsoft positions Standard “for customers with low density or non-virtualized environments”, which describes most small office servers, the ones running file shares, Active Directory, printing and one or two VMs.
Windows Server 2025 was released on 1 November 2024. Mainstream support runs until 13 November 2029, and security updates continue until 14 November 2034.
How core licensing works
Microsoft’s licensing guidance says “all physical cores on the server must be licensed”, with a minimum of 8 core licences per physical processor and 16 per server. Core licences are sold in packs of 2 and 16.
| Server hardware | Core licences needed |
|---|---|
| One 8-core processor | 16 |
| One 16-core processor | 16 |
| One 24-core processor | 24 |
| Two 6-core processors | 16 |
| Two 12-core processors | 24 |
The two 6-core processors need 16 because each processor counts as at least 8. Logical processors and hyper-threading don’t change the count, which is based on physical cores.
How many virtual machines Standard covers
With every core licensed, “Standard has rights to use two OSEs or two Windows Server containers with Hyper-V isolation”. An OSE, or operating system environment, is Microsoft’s licensing term for an installation of Windows Server, physical or virtual. The physical installation on the host doesn’t use up one of the two, as long as it only runs Hyper-V and manages the VMs.
For two more VMs, license all the cores again with the same number of core licences. The practice is usually called stacking. A 16-core host licensed twice covers four VMs, three times covers six, and so on.
When Datacenter costs less
Datacenter covers unlimited VMs on the licensed server. Microsoft’s US list prices for 16 cores are $1,176 for Standard and $6,771 for Datacenter.
On a 16-core host, five Standard licences cover ten VMs for $5,880. An eleventh or twelfth VM needs a sixth licence, which takes the total to $7,056, more than one Datacenter licence. From eleven VMs on a 16-core host, Datacenter is the cheaper edition. Below that, Standard costs less, and a small office running one or two VMs is nowhere near the crossover.
Client Access Licences
Microsoft’s rule is “Each user or device that accesses licensed servers requires a Windows Server CAL (Base CAL).” A user CAL covers one person on any number of devices. A device CAL covers one device, whoever uses it. Where people outnumber devices, device CALs usually cost less, and the other way round. CALs have to be for Windows Server 2025 or a later version.
Running desktops or applications for users through Remote Desktop Services needs an RDS CAL for each of them as well, on top of the base CAL. Two administrators can connect at the same time for management without RDS CALs.
A product key only activates the server. The number of cores, VMs and users you’re entitled to comes from the licences you hold, so file the invoices with the server’s documentation.
Standard and Datacenter compared
| Standard | Datacenter | |
|---|---|---|
| Virtual machines per fully licensed server | 2 | Unlimited |
| Containers with Hyper-V isolation | 2 | Unlimited |
| Storage Spaces Direct | No | Yes |
| Storage Replica | 1 partnership and 1 resource group, single volume up to 2 TB | Unlimited |
| Network Controller | No | Yes |
| Host Guardian Hyper-V Support | No | Yes |
| Hotpatching through Azure Arc | Yes | Yes |
| SMB over QUIC | Yes | Yes |
| GPU partitioning | Standalone servers | Standalone and clustered servers |
| Microsoft US list price for 16 cores | $1,176 | $6,771 |
On GPU partitioning, Microsoft’s comparison limits Standard to standalone servers. If you need clustering to cover unplanned downtime, that takes Datacenter.
What’s new in Windows Server 2025 for a small office
Hotpatching
Hotpatching installs security updates without a restart. Microsoft’s summary is “You can use Hotpatch to apply OS security updates without restarting your machine.” A full update that does need a restart arrives in the baseline months of January, April, July and October, and the two months after each baseline are hotpatch months. That’s up to eight months a year without a security reboot.
It works on Standard and Datacenter, on build 26100.1742 or later, in both Server Core and Desktop Experience installations. The server has to be connected to Azure Arc, which needs an Azure subscription, and it has to meet the requirements for virtualisation-based security, which at minimum means UEFI with Secure Boot enabled. When hotpatching for Arc-connected servers launched in July 2025 it cost $1.50 per core per month. The charge stopped on 15 May 2026, and Microsoft’s documentation now says “Azure Arc-enabled Hotpatch for Windows Server 2025 is now available at no extra cost.”
SMB over QUIC in Standard
SMB over QUIC gives staff secure access to file shares over the internet without a VPN. Microsoft’s release notes say the server feature “which was only available in Windows Server Azure Edition, is now available in both Windows Server Standard and Windows Server Datacenter versions.”
SMB signing on by default
SMB signing is now required by default on every outbound SMB connection, the connections the server makes to other machines. An older NAS that can’t sign SMB traffic may refuse them, so if the server copies backups to a NAS, test those jobs after the upgrade.
OpenSSH, Wi-Fi and Bluetooth
The OpenSSH server is installed by default, and Server Manager has a Remote SSH Access switch to turn it on. The Wireless LAN Service is installed too, with its startup set to manual, so start it when you need Wi-Fi.
net start wlansvcBluetooth also works now. Microsoft lists mice, keyboards, headsets and audio devices.
Security defaults
Credential Guard is now enabled by default on hardware that meets its requirements. New Active Directory deployments require LDAP signing by default, and domain controllers no longer issue Kerberos ticket-granting tickets with RC4 encryption.
In-place upgrades
Servers on Windows Server 2012 R2 or later can be upgraded in place directly to 2025, up to four versions at once. A 2016 or 2019 server goes straight to 2025 with no version in between.
Larger limits for Hyper-V and Active Directory
Generation 2 VMs can have up to 2,048 virtual processors and 240 TB of memory, and GPU partitioning lets several VMs share one physical graphics card. Active Directory also gains an optional 32k database page size and can now use processors beyond the first 64 cores.
Activating a retail installation
Open Command Prompt or PowerShell as administrator and install and activate your key.
slmgr /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
slmgr /atoThen run slmgr /dlv to confirm the edition, the licence channel and the activation status.
Converting an evaluation to Standard
Microsoft’s evaluation of Windows Server 2025 runs for 180 days, and the Evaluation Center warns that “Evaluation versions of Windows Server must be activated over the internet in the first 10 days to avoid automatic shutdown.” A server built on the evaluation can be converted in place and keeps everything installed on it.
Open Command Prompt as administrator and check the current edition. An evaluation shows as ServerStandardEval or ServerDatacenterEval.
DISM /online /Get-CurrentEditionList the editions it can become.
DISM /online /Get-TargetEditionsConvert it with your product key.
DISM /online /Set-Edition:ServerStandard /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEulaDISM asks to restart the server to complete the change. Afterwards, slmgr /dlv should show Standard with no mention of an evaluation.
Microsoft lists several limits on conversion.
- “You can’t convert an Active Directory domain controller from an evaluation to a retail version.” Convert the evaluation before you install Active Directory Domain Services on it.
- An evaluation of Datacenter can only become retail Datacenter, never Standard.
- A Desktop Experience evaluation can’t be converted to a Server Core installation.
- If the edition you want isn’t listed by Get-TargetEditions, the only route is a fresh installation of that edition.
Changing edition or key later
Standard can be converted to Datacenter at any time with the same Set-Edition command, using ServerDatacenter and a Datacenter key. Running setup.exe from the installation media doesn’t change the edition. In Microsoft’s words, “the result is the same edition you started with.”
Switching between retail, volume and OEM keys of the same edition only needs slmgr /ipk with the new key, and the edition stays as it is.
Windows Server 2025 Standard is listed with our other Windows Server licences.
Questions about Windows Server 2025 Standard
How many virtual machines can Windows Server 2025 Standard run?
Two for each time every physical core is licensed. A 16-core server licensed once covers two VMs, and licensed twice it covers four.
Do I need CALs for a file server?
Yes. Every user or device that accesses the server needs a Windows Server CAL, whatever roles the server runs.
Does Windows Server 2025 Standard need Azure?
No. Hotpatching is the only feature here that needs the server connected to Azure Arc.
Are 16 core licences enough for a 24-core server?
No. Every physical core has to be licensed, so a server with 24 cores needs 24 core licences.
Can I use Windows Server 2022 CALs with Windows Server 2025?
No. The CALs have to be for Windows Server 2025 or a later version.
Sources
- Windows Server 2025 Licensing Guidance, Microsoft Licensing
- Comparison of Windows Server editions, Microsoft Learn
- What’s new in Windows Server 2025, Microsoft Learn
- Convert Windows Server editions and license types, Microsoft Learn
- Windows Server 2025 lifecycle, Microsoft Learn
- Windows Server 2025 evaluation, Microsoft Evaluation Center
- Windows Server pricing, Microsoft
- Enable Hotpatch for Azure Arc-enabled servers, Microsoft Learn
- Hotpatching for Windows Server 2025, Licensing School