Before you start
- A 64-bit physical machine or VM with at least 2 GB of memory (4 GB recommended with the graphical interface) and at least 32 GB of disk
- The Windows Server 2025 ISO image (evaluation or licensed)
- A fixed IP address planned for the server (see IP address, subnet mask and gateway)
In plain words
Windows Server is Windows built to run services for others: the company's account directory (Active Directory), file sharing, printing, virtual machines (Hyper-V), Remote Desktop. It looks like Windows 11, but it's mostly managed remotely, it has to be installed carefully (name, fixed address, updates) and it's licensed differently. This page covers the foundation: choosing, installing, making the first settings. The roles (Active Directory, DNS, DHCP, files) have their own pages, starting with Creating an Active Directory domain.
Information checked on 20 October 2026 against Microsoft's documentation.
1. Which version, and until when?
| Version | Released | End of mainstream support | End of extended support (end of security patches) |
|---|---|---|---|
| Windows Server 2025 | November 2024 | 13 November 2029 | 14 November 2034 |
| Windows Server 2022 | August 2021 | Ended (13 October 2026) | 14 October 2031 |
| Windows Server 2019 | November 2018 | Ended | 9 January 2029 |
| Windows Server 2016 | August 2016 | Ended | 12 January 2027 |
Windows Server 2016: less than three months of patches left
After 12 January 2027, Windows Server 2016 will no longer receive any security patches. A 2016 server still in production must be migrated now. Windows Server 2022 has just left mainstream support: it now only receives security patches.
For a new installation, choose Windows Server 2025.
2. Which edition?
| Standard | Datacenter | Datacenter: Azure Edition | |
|---|---|---|---|
| For whom | Physical server, or few VMs | Virtualisation host with many VMs | Servers in Azure or on Azure Local |
| Windows Server VMs covered by the licence | 2 per fully licensed server (stackable) | Unlimited | Depends on the hosting |
| Storage Spaces Direct (hyperconverged storage) | No | Yes | Yes |
| Network Controller (SDN), shielded VMs (Host Guardian) | No | Yes | Yes |
| Hotpatch (patches without restarting) | With an Azure Arc subscription | With an Azure Arc subscription | Included |
| Common roles (AD DS, DNS, DHCP, files, IIS, Hyper-V, RDS) | Yes | Yes | Yes |
The licensing rules, in brief
- Licensing is counted per physical core of the server: all cores must be licensed, with a minimum of 8 cores per processor and 16 cores per server, even if the server has fewer.
- With Standard, licensing all cores gives the right to 1 physical instance or 2 VMs of Windows Server. For 4 VMs, you license the cores twice, and so on. With Datacenter, VMs are unlimited.
- The rule is the same whatever the hypervisor: Hyper-V, Proxmox VE, VMware.
- Every user or device that accesses the server needs a client access licence (CAL). Remote Desktop also requires RDS CALs.
- 2025 licences include downgrade rights to previous versions.
The exact terms depend on the agreement (reseller, volume licensing, OEM): have your case checked by your licensing supplier.
3. Server Core or Desktop Experience?
| Server Core | Desktop Experience | |
|---|---|---|
| Interface | No graphical interface: console, PowerShell and SConfig | Full Windows desktop, Server Manager |
| Disk footprint | About 4 GB less | Larger |
| Attack surface, updates | Smaller: fewer components to patch, fewer restarts | Larger |
| Administration | Remote: Windows Admin Center, RSAT tools, PowerShell | Local or remote |
| Recommended for | Domain controllers, Hyper-V hosts, file servers, run by teams comfortable with PowerShell | First steps, applications that require a graphical interface, small organisations |
The choice is final
You can't switch from Server Core to Desktop Experience (or the other way round) without reinstalling. If in doubt, choose Desktop Experience for a first server.
4. Getting the ISO image
| Source | For whom | Good to know |
|---|---|---|
| Microsoft Evaluation Center | Tests, lab, homelab | Full version valid for 180 days; can then be converted to a licensed version |
| Microsoft 365 admin centre or volume licensing portal | Organisations under agreement | Licensed image, key provided |
| Server supplied by the manufacturer (OEM) | Physical server bought with Windows | Image and licence tied to the hardware |
Evaluation and conversion
A Desktop Experience evaluation can be converted to licensed Standard or Datacenter. However, a Server Core Standard evaluation can only be converted to Datacenter Core: for Standard Core, start directly from the licensed image. And a domain controller installed from an evaluation can't be converted: never install one from an evaluation version for production.
5. Installing
On a physical server
Create a USB stick with Rufus (see the software catalogue), then boot from it. In the BIOS or UEFI: virtualisation (VT-x or AMD-V) turned on if the server is to host Hyper-V, Secure Boot and TPM 2.0 turned on (essential for BitLocker and modern security protections).
In a VM
| Hypervisor | Recommended settings |
|---|---|
| Hyper-V | Generation 2 VM, Secure Boot turned on, virtual TPM turned on |
| Proxmox VE | Guest OS type Microsoft Windows 11/2022/2025, BIOS OVMF (UEFI), virtual TPM 2.0, VirtIO disk and network card; add a second ISO image with the VirtIO drivers for Windows (virtio-win.iso), to load during installation so the disk appears |
| VMware | Guest OS type Windows Server 2025, PVSCSI controller, VMXNET3 card (drivers in VMware Tools) |
Minimum memory during installation
Microsoft's documentation warns that a VM with the bare minimum (1 vCPU, 1,024 MB) fails to install. Give it at least 2 GB during installation; you can adjust afterwards.
The installer screens
- Language, time format, keyboard: choose your language and region, for example English (United Kingdom), and the matching keyboard.
- Install Windows Server; tick the box acknowledging that settings and files will be deleted if you reinstall.
- Product key: enter it, or skip this step with an evaluation version.
- Image: choose the edition (Standard or Datacenter) and the installation option: the (Desktop Experience) entries install the graphical interface, the others install Server Core.
- Licence terms: accept.
- Disk: select the unallocated space (or load the VirtIO driver if no disk appears), then Install.
- At restart, set the Administrator account password: long and unique, stored in your password manager.
6. The first settings
Do these before installing any role: changing the name later, once the server is part of a domain, is much trickier.
| Setting | Example | Why |
|---|---|---|
| Server name | SRV-AD01, SRV-FS01 |
The generated name (WIN-8F3K…) is unreadable; 15 characters maximum |
| Fixed IP address | 192.168.1.20/24, gateway 192.168.1.1 |
A server mustn't change address |
| DNS server | The network's, then the domain controller once created | Essential for Active Directory |
| Time zone | Your own, for example London (UTC+00:00) | Consistent logs and scheduled tasks |
| Updates | Full installation, then restart | Patch before exposing the server |
| Remote Desktop | Turned on with NLA, if needed | Remote administration |
| Activation | Product key or KMS | Mandatory outside evaluation |
With the graphical interface
Server Manager opens at start-up. Under Local Server, every line is clickable: computer name, Ethernet (IP address), time zone, Remote Desktop, Windows Update.
With SConfig (Server Core, and also with the graphical interface)
On Server Core, SConfig opens automatically at sign-in. Elsewhere, type SConfig in PowerShell. You choose an option by its number:
| Option | Setting |
|---|---|
1 |
Domain or workgroup |
2 |
Computer name |
6 |
Install updates |
7 |
Remote Desktop |
8 |
Network settings (IP address, DNS) |
9 |
Date and time |
11 |
Windows activation |
With PowerShell
In an administrator PowerShell. First find the name of the network adapter:
Get-NetAdapter
Name InterfaceDescription ifIndex Status LinkSpeed
---- -------------------- ------- ------ ---------
Ethernet Red Hat VirtIO Ethernet Adapter 6 Up 10 Gbps
Fixed IP address, gateway and DNS:
New-NetIPAddress -InterfaceAlias "Ethernet" -IPAddress 192.168.1.20 -PrefixLength 24 -DefaultGateway 192.168.1.1
Set-DnsClientServerAddress -InterfaceAlias "Ethernet" -ServerAddresses 192.168.1.1
Time zone, here London (Get-TimeZone -ListAvailable lists the identifiers):
Set-TimeZone -Id "GMT Standard Time"
Remote Desktop with NLA, and opening the firewall (the rule group is referred to by its identifier, which works whatever the system language):
Set-ItemProperty -Path 'HKLM:\System\CurrentControlSet\Control\Terminal Server' -Name fDenyTSConnections -Value 0
Set-ItemProperty -Path 'HKLM:\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' -Name UserAuthentication -Value 1
Enable-NetFirewallRule -Group "@FirewallAPI.dll,-28752"
Rename and restart, last of all:
Rename-Computer -NewName "SRV-AD01" -Restart
Activating, or converting an evaluation
Licence status:
slmgr.vbs /dlv
Install a key and activate:
slmgr.vbs /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
slmgr.vbs /ato
Convert an evaluation to a licensed version (in an administrator prompt):
DISM /online /Get-CurrentEdition
DISM /online /Get-TargetEditions
DISM /online /Set-Edition:ServerStandard /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEula
The server restarts, possibly several times. The edition name to give is the one listed by /Get-TargetEditions.
7. Installing roles and features
With the graphical interface: Server Manager > Manage > Add Roles and Features. In PowerShell:
Get-WindowsFeature | Where-Object Installed
Install-WindowsFeature -Name Windows-Server-Backup -IncludeManagementTools
| Role or feature name | What it is |
|---|---|
AD-Domain-Services |
Active Directory (domain controller) |
DNS |
DNS server |
DHCP |
DHCP server |
FS-FileServer |
File server |
Hyper-V |
Hypervisor |
Web-Server |
IIS web server |
Windows-Server-Backup |
Windows Server Backup |
One role per server remains good practice: a domain controller should only be a domain controller (and DNS).
8. Administering remotely
| Tool | What for |
|---|---|
| Windows Admin Center | Microsoft's free web console for administering servers, clusters and Hyper-V from a browser; install it on a server or an administration workstation |
| RSAT tools on Windows 11 | The classic consoles (Active Directory Users and Computers, DNS, DHCP, Group Policy); in Settings > System > Optional features |
| PowerShell remoting | Enter-PSSession -ComputerName SRV-AD01, or a command on several servers with Invoke-Command |
| Server Manager | Add other servers (Manage > Add Servers) to manage them from a single console |
9. The security baseline
- Monthly updates installed and restarts scheduled; hotpatching reduces these restarts with an Azure Arc subscription.
- Windows Firewall active on all three profiles; open only the ports you need.
- Remote Desktop only from the administration network or through a VPN, never exposed to the internet.
- The built-in Administrator account with a long, unique password; across a fleet, Windows LAPS (built in) gives each server a different password and rotates it.
- Named accounts for administration, with no web browsing or email from the server.
- Microsoft Defender active (see antivirus and security tools).
- Backup from day one: Windows Server Backup, or your backup software, with a copy off the server (see the 3-2-1 rule).
Key points
- New installation: Windows Server 2025, supported until November 2034; migrate 2016 servers before 12 January 2027.
- Standard for 2 VMs per full licence, Datacenter for unlimited VMs; licensing per core (16 minimum) plus CALs.
- Server Core for security and lightness, Desktop Experience to get started; changing your mind means reinstalling.
- First settings before any role: name, fixed IP, DNS, time zone, updates, activation.
- Remote administration (Windows Admin Center, RSAT, PowerShell), Remote Desktop never exposed to the internet.