Windows Server 2016 reaches end of support on 12 January 2027. After that date, Microsoft’s regular security updates will stop. Businesses still using it will need to move to a supported setup or arrange eligible Extended Security Updates while they complete the work.
For a business relying on Windows Server 2016 for shared files, staff logins or accounting software, the first job is to establish exactly what depends on it. That will determine how much work is involved, which suppliers need to help and when the change can happen.
Your server will keep running, but regular security updates will stop
The support deadline won’t switch your server off. Staff may still be able to open files and use applications as usual, which can make the change easy to overlook.
The risk is that newly discovered weaknesses in the operating system will no longer receive fixes through Microsoft’s regular security updates. A server can appear to work normally while becoming harder to protect.
Microsoft sets out the deadline and update arrangements in its Windows Server 2016 end-of-support guidance.
Start with the applications and services your staff use
A server’s name or age won’t tell you everything it does. One machine might hold shared folders, run a database and manage access to other systems. Some of those jobs may be obvious; others may only become apparent when something stops working.
Ask your IT team or support provider to check:
- Which physical and virtual servers run Windows Server 2016.
- Which applications, databases and services run on each one.
- Who uses them and which other systems connect to them.
- Whether the software suppliers support moving them to a newer environment.
- Whether any services are no longer needed.
For example, moving shared files might be straightforward, but an accounts package on the same server could require a software upgrade first. Identifying that dependency early gives you time to speak to the supplier and include their work in the schedule.
Choosing between a server upgrade and cloud migration
There are several ways to move away from Windows Server 2016. The right choice depends on your software, existing equipment, budget and how your staff work.
Move to a supported Windows Server environment. This may suit applications that still need a server. Check application compatibility, hardware requirements, licensing and the remaining support life of the proposed version before choosing it.
Move suitable services to the cloud. Some shared files may be suitable for SharePoint or Teams within Microsoft 365. A software supplier may also offer a hosted version of an application you currently run locally. Each service needs assessing separately: Microsoft 365 is not a replacement for every server application.
Keep a combination of local and cloud services. You might retain a server for specialist software while moving other services elsewhere. This can allow changes to happen in stages.
Retire services you no longer use. Check whether older applications or duplicate systems still have a purpose before paying to move them. Any data that needs keeping should remain accessible.
Moving a Windows Server 2016 virtual machine to a different location does not, by itself, resolve its operating-system support deadline. The migration plan still needs to address the version of Windows it runs.
Extended Security Updates can provide extra time
Microsoft offers Extended Security Updates, or ESUs, for eligible Windows Server 2016 environments for up to three years after end of support. They provide critical and important security updates, with limited support relating to ESUs, rather than restoring the full support available to a current product.
This may be useful if an application upgrade or migration cannot be completed before January. Eligibility, licensing and costs need checking for your particular setup.
If you need ESUs, include them in a migration plan with an agreed completion date. They won’t resolve ageing hardware or compatibility problems with the applications running on it.
Agree the costs, downtime and recovery plan
Before work begins, you should have a clear explanation of what is changing and what it will mean for staff. A proposal should cover more than the price of a replacement server.
It should identify:
- Costs: equipment, licences, supplier charges, migration work and ongoing subscriptions.
- Timing: the order of work, supplier availability and any periods when systems will be unavailable.
- Backups: how data will be protected and whether it can be restored.
- Testing: how applications, permissions and connections to other systems will be checked.
- Recovery arrangements: what happens if the change cannot be completed as planned.
- Staff support: what users need to know and who they should contact afterwards.
-
Your backup and disaster recovery arrangements should be reviewed as part of the project. Having a recent backup is useful; knowing it can be restored is essential when making changes to a system your business depends on.
Get help planning your Windows Server 2016 migration
Serveline helps businesses review their servers, check application dependencies and plan upgrades or cloud migrations. We can help you assess the options, agree the work involved and coordinate the move around your operations.
If you’re unsure whether Windows Server 2016 is still in use, speak to our team. We’ll help you establish what’s running and which systems need attention before 12 January 2027.