Still Running an Ageing Windows Server?

Windows Server 2019 is still supported — but planning should already have started

Server 2019 is not an emergency today. Server 2016 is much more urgent. Both should be on a documented lifecycle plan.

• Windows Server 2016 — Extended Support ends 12 January 2027
• Windows Server 2019 — Extended Support ends 9 January 2029
• Windows Server 2022 — Extended Support ends 14 October 2031
• Windows Server 2025 — Extended Support ends 14 November 2034

Verify current lifecycle dates at the Microsoft Lifecycle Products website before making decisions.

Still running Server 2016?

Windows Server 2016 Extended Support ends 12 January 2027. If a migration project is not already underway, start planning now.

Who this service is for

• Server 2016 still in use — immediate lifecycle project
• Server 2019 still in use — plan migration while there is a comfortable support window
• Ageing physical server — hardware replacement, consolidation or virtualisation
• Old Hyper-V host — refresh host hardware and Windows Server platform
• Remote Desktop Server — review whether RDS remains the right architecture
• Active Directory Server — migrate domain-controller roles safely
• File Server — assess replacement, migration or cloud alternatives
• Line-of-Business Application Server — review vendor compatibility and target platform
• SQL Application Server — coordinate Windows Server and SQL lifecycle
• Business moving office — good opportunity to reconsider physical infrastructure
• Business moving to Microsoft 365 — assess whether remaining server workloads can be reduced

First question: why does the server still exist?

Before planning the target platform, Altitude reviews server roles, users, applications, databases, dependencies, hardware, storage, networking, backup, recovery, printers, remote access, integrations, third-party suppliers and licensing.

Potential outcomes for each workload:

• Upgrade — keep the server role but move to a supported Windows Server version
• Migrate — move the workload to new infrastructure
• Replace — replace the application or platform with a supported alternative
• Cloud — move appropriate workloads to Microsoft 365, Azure, SaaS or specialist hosted services
• Consolidate — reduce unnecessary infrastructure
• Retire — remove a server that no longer needs to exist

Do not spend money upgrading a server until you have established whether the business still needs it.

Services included

Windows Server Upgrades

Support projects involving Server 2016, 2019, 2022 and 2025. Upgrade path, edition, licensing, hardware and application compatibility reviewed before committing to an approach.

Server Replacement

Plan replacement of ageing physical infrastructure. Hardware age, warranty, storage, RAID, memory, networking, redundancy and UPS reviewed.

Active Directory Migration

Controlled migration of domain controllers, DNS, DHCP where applicable, FSMO roles and authentication services. Active Directory should be migrated deliberately, not treated as another application on the server.

Hyper-V Host Refresh

Replace Hyper-V hosts, migrate VMs and storage to Server 2025 Hyper-V. Review whether existing VMs should remain, be consolidated, retired or moved elsewhere.

File Server Migration

Assess new Windows file server, SharePoint Online, OneDrive, Azure Files or specialist document management. A file server migration is a data and workflow project, not simply a copy operation.

Remote Desktop Services

Review RDS Session Hosts, RD Gateway, licensing, profiles, applications, printers, MFA and security. Evaluate newer RDS, Azure Virtual Desktop, Windows 365 or SaaS as alternatives.

If users only need Remote Desktop to reach one old application, challenge the application before rebuilding the whole RDS platform.

Line-of-Business Application Migration

Support accounting, ERP, CRM, document management and industry-specific applications through a server change. Working on a newer server is not the same as being supported on a newer server.

SQL Server Review

Document SQL version, edition, instances, databases, application dependencies, backup, recovery and support lifecycle where SQL is present.

Azure Migration

Evaluate Azure VM, Azure Virtual Desktop, Azure Files, Microsoft Entra, cloud backup and hybrid identity where appropriate. Moving the server into Azure removes the hardware. It does not automatically remove the server-management cost.

The best server replacement project may end with fewer servers than you started with.

In-place upgrade vs migration

In-Place Upgrade

Potentially suitable where infrastructure is healthy, the server is virtual, applications support the target OS and technical debt is limited. Risks: legacy configuration retained, compatibility issues, more complex rollback.

Migration / Rebuild

Potentially suitable where physical hardware is ageing, Active Directory is involved, architecture needs redesign or technical debt exists. Advantages: cleaner architecture, supported hardware, opportunity to remove old configuration.

An operating-system upgrade changes Windows. A migration gives you the opportunity to fix the infrastructure.

Server 2019 to Server 2025: what the upgrade path actually means

Microsoft currently supports a direct in-place upgrade from Windows Server 2019 to Windows Server 2025 for appropriate non-clustered systems. Operating-system support does not prove application support, driver support, database support, backup compatibility or EDR compatibility.

Microsoft may support the upgrade path while the software running on the server does not.

What we check before migration

Operating system: current version, target version, support dates, patch status. Hardware: age, warranty, storage, firmware, compatibility. Applications: vendor support, versions, integrations, database, licences. Active Directory: health, replication, DNS, roles. Backup: current backups, offsite protection, application-aware backup, restore test. Security: administrator access, RDP, VPN, endpoint security, firewall, vulnerabilities. Business: acceptable downtime, critical periods, user testing, project owner, budget.

Backup and rollback

Before major server work Altitude establishes: valid backup, recovery procedure, recovery credentials, application backups, database backups, system-state backup where relevant, rollback plan and cut-off point.

The upgrade plan is incomplete until the recovery plan has been tested.

Server security

Altitude reviews security controls as part of every migration project: security updates, Microsoft Defender / EDR, administrator accounts, service accounts, firewall, RDP exposure, TLS, SMB, vulnerabilities, local administrator use, MFA for remote access and backup protection.

There is little value moving an old server onto a new operating system while carrying every old security weakness with it.

Cyber Essentials and server lifecycle

Cyber Essentials requires supported software with up-to-date security patches. Server 2019 remains within Microsoft Extended Support and does not currently fail Cyber Essentials. Server 2016 becomes urgent because Extended Support ends January 2027.

Cyber Essentials should not be the first time a business discovers its server is approaching end of support.

Running Windows Server on VMware ESXi?

A hypervisor decision and a Windows Server lifecycle decision can be scoped together. Before choosing a like-for-like replacement for Server 2019 or 2022, read our independent VMware review.

The Altitude server project process

1. Discover — inventory servers, VMs, roles, applications, databases, dependencies, hardware, backups, remote access and suppliers
2. Design — decide upgrade, migrate, replace, cloud, consolidate or retire for each workload
3. Verify — confirm application support, Windows support, database support, licensing, backup and recovery
4. Build — prepare hardware, VMs or cloud infrastructure; install and configure Windows, security, backup and monitoring
5. Migrate — move users, data, applications, roles and services within agreed downtime, with testing and rollback plan
6. Retire — remove obsolete servers, old VMs, service accounts, firewall rules, monitoring agents, backup jobs and licences

A migration is not complete while the old server is still quietly running in the corner.

Operational Heartbeat

Server lifecycle needs an Operational Heartbeat: operating systems, hardware, applications, databases, backups and support dates should be reviewed before they become urgent.