What happens on 12 January 2027
That day extended support ends for Windows Server 2016 in all its editions (Essentials, Standard and Datacenter). Microsoft releases the last security update and stops fixing bugs and providing technical support.
The server does not shut down or stop working. The problem comes afterwards: any vulnerability discovered from then on stays unpatched, and attackers look precisely for unsupported systems because they know nobody will fix them. An unpatched file or domain server is one of ransomware’s favourite ways in.
It also matters for compliance: the GDPR, public-sector security frameworks and many cyber insurance policies require up-to-date systems, and an unsupported server is hard to justify in an audit.
How to tell whether it affects you
In a small business, Windows Server 2016 usually sits behind things nobody looks at until they fail:
- The domain controller: users, passwords and permissions.
- The file server and shared folders.
- DNS, DHCP and the office printers.
- The management software or ERP and its database.
- Remote desktops and Hyper-V virtual machines.
To check, open Server Manager or run winver. Check the virtual machines too: a new server can host virtual machines running Windows Server 2016, and those also lose their patches.
The four ways out
| Option | What it means | When it makes sense |
|---|---|---|
| Pay for extended security updates (ESU) | Buys time, does not solve it; if available for your licence, every year costs more | If the migration needs a few more months |
| Move it to the cloud | A monthly fee and a dependency on the connection | If you already work in the cloud and have good fibre |
| A new server in the office | One investment, with Windows Server 2025 (supported until 2034) or Linux | The usual choice for businesses with local data and software |
| Isolate it | No internet, on a separate network, only for those who use it | Only for an old program that cannot migrate yet |
Upgrading the same server to Windows Server 2025 is possible, but a 2016 or 2017 machine is usually at the end of its life: disks with many hours, an expired warranty and little memory. A new server migrated in parallel, with the old one as a fallback until the last day, almost always pays off.
How to migrate without stopping the office
- Inventory: which roles and programs there are, who uses them and how much data there is.
- Software: confirm with your ERP vendor and every application vendor that they run on the new version.
- A full, tested backup before touching anything: restore something as a test to know it works.
- The new server in parallel: it joins the domain, takes over the roles and the old one is retired once everything works.
- Files with their permissions, outside working hours. If the paths stay the same, the computers do not notice the change.
- Retiring the old one: its disks are wiped with a certificate or stored encrypted.
Which new server to choose
Size it for the next five years, not for today: a server processor, ECC memory with free slots, NVMe drives for the system and databases and high-capacity drives in RAID for files. With remote management through a dedicated KVM-IPMI it can be serviced remotely even when the system does not boot.
On licensing, Windows Server 2025 Standard is licensed per core (at least 16 per server) and needs a client access licence (CAL) per user or per device. If all you need is files and backups, a Linux server avoids those licences.
Use the change to review your backups with the 3-2-1 rule: three copies, on two different media, one of them off site or offline. That is what saves a business from ransomware. And if you are thinking about private AI, the new server can be sized to run it too.
A realistic timeline
With two and a half months to go, a sensible order is this: in November, inventory and proposal; in December, building the new server and its 24-hour test; and in the first week of January, the migration, with the old server running as a fallback until the 12th.
Related hardware and guides
Frequently asked questions
Does the server stop working on 12 January?
No. It keeps booting and serving, but it no longer receives security patches, and the risk grows every month it goes without updates.
Can I upgrade the same server to Windows Server 2025?
It is possible, but on a 2016 or 2017 machine the hardware is usually at the end of its life. A new server migrated in parallel, with the old one as a fallback, normally pays off.
How long does the migration take?
In a small business with a domain controller, files and management software, the migration itself usually takes one or two working days, well prepared beforehand. What takes longest is the inventory and checking the software.
What if an old program only runs on Windows Server 2016?
It can be kept in an isolated virtual machine, without internet access and only for those who use it, while the vendor updates it. It is a temporary measure.
Do you have a Windows Server 2016 machine?
Tell us what it does and how many people use it. We propose the new server, at a fixed price, in under 12 business hours.