Talk to us
WhatsApp us

Free cloud cost review: we will find the waste in your AWS or Azure bill in 5 business days. Book it

Cloud migration

Windows Server 2016 end of support: what to do before 12 January 2027

Extended support for Windows Server 2016 ends on 12 January 2027. A practical plan for the servers nobody wants to touch.

  • Updated
  • 4 min read

The short answer

Windows Server 2016 reaches the end of extended support on 12 January 2027, after which it stops receiving security updates. Organisations should inventory every 2016 server now, then decide per server whether to retire it, upgrade in place, rebuild on a supported version, replatform the application onto managed services, or migrate and upgrade together during a cloud move.

Key takeaways

  • Extended support for Windows Server 2016 ends on 12 January 2027
  • The hard part is finding every server, including the ones under desks and in old clusters
  • Decide per server: retire, upgrade, rebuild, replatform or migrate-and-upgrade
  • A cloud migration is often the cheapest moment to fix the operating system
Windows Server 2016 end of support: what to do before 12 January 2027

Windows Server 2016 has been out of mainstream support since January 2022. On 12 January 2027 its extended support ends too. From that date, servers still running it stop receiving security updates as standard. For most organisations, that turns a long-tolerated piece of technical debt into an audit finding, an insurance question and a real attack surface.

The deadline is not the hard part. The hard part is that Windows Server 2016 servers tend to host exactly the applications nobody wants to touch: a line-of-business system from a vendor that no longer exists, a reporting server someone built in 2018, a file server that grew into a shared drive for half the company.

Step one: find every 2016 server

Most organisations underestimate how many they have. The domain controller list is a start, not an answer. A complete inventory combines several sources:

  • Directory data — computer objects with their operating system version, filtered to those that have logged on recently.
  • Virtualisation platforms — every VM on VMware, Hyper-V or a cloud provider, with its guest OS.
  • Endpoint and patch tooling — the agents that already report OS versions.
  • Discovery tools — Azure Migrate's appliance discovers servers, installed software and dependencies, which helps for the next step too.

Cross-check the sources. Servers that appear in one but not the others are usually the ones that cause trouble later: test machines that became production, appliances running Windows underneath, and clusters nobody documented.

Step two: understand what each one does

For each server, record the application it hosts, who owns it, what depends on it and how critical it is. Dependency mapping matters here more than in most projects, because a 2016 server is often quietly feeding something else — an integration, a scheduled export, a licence server. Tools can map network connections; only people can tell you whether a connection matters.

Step three: choose a route per server

There is no single answer for an estate. Each server falls into one of a handful of routes:

  • Retire. Usually more servers than expected have no active users or a replacement already in place. Switching them off is the cheapest fix available.
  • Upgrade in place. Supported for many roles, and fast, but it carries forward every configuration quirk. Check the application vendor supports the newer version first.
  • Rebuild on a supported version. A clean server with the application reinstalled. Slower, but the result is documented and repeatable.
  • Replatform. Move the workload onto a managed service — web applications to Azure App Service, databases to Azure SQL — so the operating system stops being your problem.
  • Migrate and upgrade together. If a cloud migration is planned anyway, rebuild the server on a supported version as part of the move rather than lifting the old OS into the cloud.

What about extended security updates?

For earlier versions of Windows Server, Microsoft offered paid Extended Security Updates after the end of support, and included them at no extra charge for servers running in Azure. Whether a similar arrangement exists for Windows Server 2016, and on what terms, is something to confirm with Microsoft or your licensing partner directly rather than assume. Even where it is available, treat it as time bought to finish the work, not a strategy: it covers security fixes only and has its own cost and end date.

Why a cloud migration is often the right moment

If you were going to migrate some of these workloads to Azure or AWS in the next year or two, the end of support is a reason to bring that forward and combine the work. Rebuilding a server on a supported version during a migration costs little more than migrating it as-is, and it avoids paying twice. Our Azure migration and AWS migration programmes schedule end-of-support servers into the earliest waves for exactly this reason.

Two cautions. First, do not lift an unsupported operating system into the cloud and call it done — it is still unsupported. Second, licensing changes when you move: Windows Server licences with Software Assurance can often be reused in Azure through Azure Hybrid Benefit, which can make the cloud option considerably cheaper than list prices suggest.

A realistic timeline

With the deadline in January 2027, a workable plan for most mid-sized estates looks like this: inventory and classification in the first three to four weeks; retirements and simple in-place upgrades immediately after; rebuilds and replatforming in planned waves; and a short list of genuinely hard servers isolated, monitored and given a dated remediation plan. If you cannot finish everything in time, the priority is to know exactly which servers remain, why, and what compensating controls protect them.

The servers that will be left

Every estate has a few servers that cannot move by the deadline — usually because an application vendor has not certified a newer version, or because the application is due to be replaced. Isolate them on restricted network segments, remove internet access, limit who can log on, monitor them closely, and record the risk with an owner and a date. That is what auditors and insurers will ask to see.

Frequently asked questions

Extended support ends on 12 January 2027. Mainstream support ended in January 2022. After January 2027, servers no longer receive security updates as standard.

Technically yes, but without security updates it becomes a growing risk and an audit and insurance concern. If some servers must remain, isolate them, restrict access, monitor them and record a dated plan to remove them.

In-place upgrades are faster but carry forward old configuration. Rebuilding is slower but leaves a clean, documented server. For critical or poorly documented servers, rebuilding is usually worth the extra effort.

If a cloud migration is planned anyway, combining it with the operating system upgrade avoids doing the work twice. Rebuild on a supported version as part of the move rather than lifting the 2016 server as it is.

Count your 2016 servers before January

Send us a list or let us run discovery. We will classify every Windows Server 2016 machine into retire, upgrade, rebuild, replatform or migrate, with a plan that finishes before support ends.

Keep reading

How to sequence migration waves

A wave plan is where a migration succeeds or turns into an eighteen-month grind. How to group workloads, size the waves, and gate…

3 min read

What belongs in an AWS landing zone

The foundation every workload lands on. What a landing zone contains, why each part has to exist before migration starts, and…

3 min read