Windows Server 2016 end of support: an 11-week plan for your small business
Microsoft repeated it last week: Windows Server 2016 reaches the end of extended support on January 12, 2027. After that date there are no more security fixes, no more technical support and no more updates, for every edition: Datacenter, Essentials, MultiPoint Premium and Standard. Mainstream support already ended in January 2022.
Many small businesses still have one of these servers in a closet: the shared-files server, the accounting software box, or the line-of-business app “nobody touches because it works.” There are 78 days left, with the holidays in the middle. Here are the dates to remember, the four possible paths, and a realistic 11-week plan for Windows Server 2016 end of support.
Windows Server 2016 end of support: the dates that matter
Microsoft recommends moving to Windows Server 2025, whose extended support runs until November 14, 2034. For organizations that can’t migrate in time, paid Extended Security Updates (ESUs) are available through Azure Arc, configurable in the Azure portal since August 3, 2026.
Why this is a security issue, not just an IT chore
A server without patches doesn’t break down the next day. The risk is the next vulnerability. As soon as a flaw affects Windows Server, attackers compare the fixes released for supported versions and look for servers that will never get them. A 2016 server reachable from the internet, through Remote Desktop (RDP), a web portal or a VPN, becomes a door that will never close again.
It’s the same problem as forgotten software nobody updates anymore, but at the heart of your network: a server often holds your files, your accounts and your backups. And for a cyber insurer, an unsupported system weighs heavily on a questionnaire.
Step 1: know what you have
Before choosing anything, fill in one sheet per server. Ten minutes each is enough, and it’s what prevents nasty surprises in December.
Step 2: pick the right path for each server
There’s no single right answer. The same office can upgrade its domain controller, move its files into Microsoft 365 and keep an ESU for an old app for a year.
⬆️
In-place upgrade
Same machine, new version
✔ When it fits
- Recent hardware in good shape.
- Simple roles, apps confirmed compatible.
- Direct jump from 2016 to 2025 is supported.
⚠ Watch out
- Backup required before you start.
- No language change and no Core ↔ Desktop switch.
- Not every role: domain controllers need preparation.
- A new licence is required.
🆕
New server and migration
Clean install, then move
✔ When it fits
- 2016-era hardware, out of warranty.
- You want a clean start without 10 years of tweaks.
- Several roles to split up.
⚠ Watch out
- Migration plan role by role.
- Testing with users before the switchover.
- Really turn the old server off after the switchover.
☁️
To the cloud
Fewer servers to maintain
✔ When it fits
- File server: SharePoint, OneDrive and Teams in Microsoft 365.
- Apps that come in a cloud version.
⚠ Watch out
- Review permissions before moving folders.
- Office bandwidth.
- Some line-of-business apps can’t follow.
🩹
ESUs through Azure Arc
Temporary, paid bridge
✔ When it fits
- An app that can’t move before January.
- Critical and Important security fixes only, up to 3 years.
⚠ Watch out
- Software Assurance (or SPLA / subscription) required.
- Azure Connected Machine agent 1.62 or later.
- Billed from January 13, 2027; late enrollment is back-billed.
Our take: ESUs are paid, deliver only security fixes and push the problem back instead of solving it. Keep them for the server that truly can’t move, with a written exit date. For everything else, our server management and cloud services start from your inventory sheet, and our Microsoft 365 services handle moving shared files.
Step 3: a schedule that accounts for the holidays
The 11-week plan (weeks starting Monday)
The free Windows Server 2025 evaluation (180 days) is available from the Microsoft Evaluation Center: ideal for testing your apps before the real switchover.
Two rules prevent most trouble. First, backup and disaster recovery come before anything else: a full copy, actually restored on another machine, before you touch the server. Second, no big switchover during the week of December 21: if a key person or vendor is away, a small outage turns into a long shutdown.
During the transition: watch what’s left
Even well planned, a migration leaves a window where the old and new servers coexist. That’s when a forgotten access path or a service account nobody closed goes unnoticed. Our automated 24/7 monitoring with on-call technician intervention keeps an eye on both during the switchover, then confirms the old server is really off.
Before January 12, 2027, check off:
- ☐ Every 2016 server has its sheet: role, edition, hardware, apps, external access.
- ☐ A full backup has been successfully restored on another machine.
- ☐ Each app vendor has confirmed compatibility with Windows Server 2025.
- ☐ No 2016 server is directly reachable from the internet (RDP, portal, Remote Web Access).
- ☐ A path is chosen and dated for each server, ESUs included.
- ☐ Old servers have a final shutdown date.
Frequently asked questions
Q1. Will my server stop working on January 13?
No. It keeps booting and serving your files. What stops are Microsoft’s security fixes and technical support. Every new vulnerability found after that date stays open.
Q2. Can I go straight from Windows Server 2016 to 2025?
Yes. Microsoft supports a direct in-place upgrade to 2019, 2022 or 2025, with a backup first and a new licence. Some roles and configurations aren’t suited to it: a clean install is safer then.
Q3. Are ESUs a good idea?
As a bridge, yes, for a server that truly can’t move before January. They require Software Assurance (or an SPLA or subscription licence), deliver only Critical and Important fixes, and are billed from January 13, 2027, even if you enable them later.
Q4. I run Windows Server Essentials 2016. What else changes?
Essentials-specific features, including Remote Web Access, also stop on January 12. If staff use it to work from home, plan another remote access option now.
Book your free cyber check
Not sure how many Windows Server 2016 machines are still running at your business, or which ones are exposed? The free cyber check reviews your servers, backups and remote access, and you leave with a clear priority list before January 12.
Call us at 438-476-2322 or email info@neotechcloudsolutions.com.
Sources
- BleepingComputer (October 23, 2026): Microsoft: Windows Server 2016 reaches end of support in January
- Microsoft Learn: Windows Server 2016 lifecycle
- Microsoft Learn: Prepare to deliver Extended Security Updates for Windows Server 2016 with Azure Arc
- Microsoft Learn: Billing for Windows Server 2016 ESUs enabled by Azure Arc
- Microsoft Learn: Windows Server upgrade overview
Photo: panumas nikhomkhai, Pexels (Pexels licence).