Skip to main content

Insights

Windows Server 2016 end of support: what should an SME do before 12 January 2027?

After 12 January 2027, Windows Server 2016 no longer receives security updates. Start by checking which edition you run: Essentials must be migrated, because no extension is offered. With Standard or Datacenter, you can migrate or, under certain conditions, pay for a temporary extension.

Published on By Smart ITReading 6 minutes

Organisational byline. Prepared with AI tools; every cited fact is automatically checked against its source.

A dimly lit server rack, punctuated by indicator lights and amber cabling.

The deadline falls just after the year-end holidays: as this article goes live, a little under ten weeks remain. That is rarely enough to replace everything without preparation, but it is enough to find out where you stand and to decide. Here is what actually stops, what depends on your edition, and how to choose.

What changes on 12 January 2027

Microsoft is explicit: extended support for Windows Server 2016 ends on 12 January 2027, after which servers stop receiving security updates. The product lifecycle page shows an end on 13 January at 6:59 AM: go by the date Microsoft announces, 12 January.

The server does not switch off that day. As Microsoft puts it, it may continue to run, but risk increases on four fronts: security, compliance, compatibility and operations. In practice, any flaw found after that date stays open. A software vendor may also stop supporting its product on this system, so ask them.

Check what runs on these servers too. SQL Server 2016, often installed alongside business software, already reached the end of extended support in July 2026: replacing the operating system without looking at the database only solves half the problem.

First check: which edition do you run?

This question decides what comes next. On every server, physical or virtual, record the exact edition shown in its system information. Don't forget the quiet machines: an old domain controller, a server for one business application, a virtual machine created for a finished project.

What the edition changes
EditionPaid extension (ESU)What it means
EssentialsNot availableMigration to finish before 12 January 2027, remote access included
StandardPossible, with conditionsMigrate, or buy time if a project cannot finish by the date
DatacenterPossible, with conditionsSame choices, with an inventory of hosted virtual machines

Illustrative example: a twelve-person practice uses an Essentials server for its files, accounts, remote access and workstation backup. A simple reinstall does not cover all of that. It needs a solution for each of these four uses, then a full trial before unplugging the old server.

The four options, and when to pick them

Comparing the options before the deadline
OptionBetter suited ifLimit to check
In-place upgradeThe hardware remains suitable, with few roles and a compatible applicationRoles involved, application compatibility, licence for the target version
Migration to a new serverThe hardware is at end of life, or you want a clean environmentPreparation time, re-creating access rights, service interruption
Moving to cloud or online servicesUsage is mainly office work, or the vendor offers an online versionBusiness applications, connection, backup, subscription
ESU while migratingBusiness software or a project forces a delay, on Standard or DatacenterEligibility, cost, migration end date set from the start

Upgrade or migration

According to Microsoft's guide, a direct upgrade from Windows Server 2016 to 2025 is possible using installation media. It is not always the right choice: not all roles support it, and new hardware points towards migration instead. Before deciding, also check that you have a valid product key and activation method for the target version, and that both the hardware and the business software are supported by their makers.

Windows Server 2025 or 2022

Remaining lifetime matters. Windows Server 2025 has mainstream support until November 2029 and extended support until November 2034. Windows Server 2022 left mainstream support in October 2026 and stays in extended support until October 2031. Choosing the newest version pushes the next project further away, unless your business application does not support it yet. An Essentials edition is still listed for 2025, but Microsoft states that 2016 is the last version to include the full Essentials experience: check that it covers your uses before choosing it.

The cloud

An end of support is a good moment to ask the question, because both paths can still be compared on equal terms. Our decision guide on office servers versus cloud reviews the criteria without taking sides. If you keep infrastructure of your own, our cloud and infrastructure page describes what we handle.

ESUs: a bridge, not a solution

Extended Security Updates (ESUs) extend Critical and Important security updates for up to three years, through January 2030. Microsoft describes them as a last-resort paid option. They do not extend the product's lifecycle or provide technical support, nor do they bring new features.

Before relying on them, put these questions to your licence reseller:

  • Are we eligible? Microsoft generally requires Software Assurance, the maintenance option of volume licensing, except for SPLA (licences obtained from a hosting provider) or Server Subscription licensing. If your licence came with the server, have this checked first.
  • What will it cost for our servers? Through Azure Arc, Microsoft's service that attaches an on-premises server to the Azure portal, ESUs are billed monthly from 13 January 2027, and the subscription can be stopped when a server is migrated or decommissioned: remember to do it. We quote no figure here: ask for an estimate for your setup.
  • What changes if the server moves to Azure? For the ESU programme in general, Microsoft states that updates are free for virtual machines in Azure, but the machine itself still has to be paid for.
  • When will the server be retired? Without a written date, a bridge quickly becomes a permanent installation.

A six-step plan before 12 January

  1. 1.Take inventory this week

    List each server, its edition, its warranty and what it holds. Microsoft advises recording roles, applications, users, remote access, backups, certificates, DNS and integrations. The article on IT maintenance gives a method for tracking these dates.

  2. 2.Ask the vendors

    For each business application, ask in writing which versions of Windows Server and database are supported, and whether a data transfer is planned.

  3. 3.Choose a target per server

    Not every machine needs the same answer. Some get retired, others migrated, and perhaps only one justifies an ESU.

  4. 4.Test a restore

    Before touching anything, check that the data can really be recovered. The method is in our article on business data backup.

  5. 5.Run a cutover trial

    Validate remote access, permissions, backup, DNS, certificates and the business application in the new environment, with a rollback planned.

  6. 6.Switch, then retire

    Avoid accounting close periods and team holidays. Once the migration is confirmed, shut down the old server and update the documentation.

If you won't be ready in time

Don't let the date pass without a decision. On Standard or Datacenter, check ESU eligibility now. On Essentials, or without eligibility, the aim is to reduce exposure while you finish: remove any direct access from the internet, limit what goes through this server, make sure a restorable backup exists and set an exit date. These steps limit the risk without removing it: Microsoft points out that third-party application control solutions do not replace security fixes. Management should know the risk exists and accept it in writing, for a fixed period. If a provider looks after your servers, also check what your managed IT contract says about an unsupported system.

Frequently asked questions

In short

Record your editions this week. If you run Essentials, start the migration without waiting. On Standard or Datacenter, choose a target for each server and keep ESUs only for what truly cannot finish in time, with a written exit date.

Review your servers before January

The free audit, a 45-minute remote session with no commitment, reviews your servers and the decisions to make. It is followed by a written summary.

Request a free audit