Windows Server 2016: Support Ends in 2027 – What You Should Plan Now

Do you have shared files on your server, does it run your ERP system, or does it manage user logins? Then it is worth taking a look at the operating system now. In many companies, Windows Server 2016 has handled these tasks reliably for years. With the end of support approaching, a decision is due.

Which solution fits depends on your applications, your hardware and the requirements of your business. An upgrade can make sense, and so can a new server environment or a move to a data center. This article helps you classify the options and prepare the next steps.

Windows Server 2016 end of support: What happens on January 12, 2027

On January 12, 2027, Microsoft ends extended support for Windows Server 2016. The date affects the Standard, Datacenter and Essentials editions, among others – on physical servers as well as on virtual machines. Microsoft on the end of support

For your business, this means:

• The server keeps running. The end of support switches off neither the operating system nor your applications.
• Regular security updates end. Extended Security Updates are required to keep receiving them.
• You should plan the replacement in good time. Applications, licenses, hardware and maintenance windows have to fit together.

Even a server that works may require action. What matters is whether you can keep operating it securely in the future, with the support of the vendors involved.

An example: one server, five jobs

A fictional tax advisory firm uses an older server for user management, network addresses, file storage, its practice software and print services. The first thought: an operating system upgrade over the weekend.

The inventory shows, however, that the practice software is only approved for certain target versions. At the same time, the old hardware is due to be replaced. The firm therefore decides on a new environment in which the tasks are spread across several virtual servers. The changeover happens step by step, with tests before go-live.

The example shows that a single device can hide several business tasks. If you record them early, you can plan effort, costs and interruptions better.

Inventory first: What is really running on Windows Server 2016?

Before you order new hardware or commission an upgrade, you need an overview of what you have. Four questions help:

1. Which systems are affected? Check physical servers, virtual machines and the systems that host your virtual servers.
2. Which tasks do they handle? These include user management, file storage, print services, terminal servers, databases and industry-specific software.
3. Which target versions are approved? Ask the software vendor which Windows Server version your application supports.
4. Which dependencies exist? Also think of scanners, interfaces, remote access and backup software.

A simple overview is enough to start with:

What you record	Why it matters
Server and operating system	Shows which systems are affected
Tasks and applications	Determines the right migration path
Vendor approvals	Narrows down the possible target versions
Hardware condition	Helps with the decision about replacement
Owner and deadline	Turns the inventory into an actionable plan

If you lack this overview, we support you with an IT analysis. It lets you prioritize the necessary measures before you invest.

The options compared

Several paths are possible for the replacement. Within one company, different solutions can make sense.

In-place upgrade to Windows Server 2022 or 2025

With an in-place upgrade, a newer Windows Server version is installed over the existing installation. Settings, data and supported server roles are kept.

This can fit if the hardware is to be reused, the applications are approved and the existing roles support the change. For domain controllers, Microsoft recommends a clean installation followed by a migration. Other roles also have to be checked separately. Microsoft on migrating server roles

Before an upgrade, preparation includes a full backup, a tested recovery path and an agreed maintenance window.

Clean installation: new server or virtual machine

A new environment is particularly suitable if the hardware is to be renewed as well, or if many tasks have accumulated on one system over the years.

Applications and server roles can be prepared, tested and then moved step by step. This also lets you check which tasks should run on separate virtual servers in the future.

In the area of Servers & Networks we support you in planning and implementing an environment that fits your business.

Move to a data center or the cloud

The end of support is a good occasion to review where you operate your systems as well. Do you want to keep running your own servers, or move hardware and infrastructure elsewhere?

With server hosting in TERRA CLOUD, servers and applications can be operated in a German data center. For Microsoft-based environments, Azure and hybrid cloud solutions are also an option.

The move also includes reviewing the operating system: A Windows Server 2016 VM taken over unchanged keeps its existing support status. So plan the modernization right away.

Extended Security Updates as a temporary bridge

If an application cannot be migrated yet, Extended Security Updates, ESU for short, can buy additional time.

For Windows Server 2016 Standard and Datacenter, Microsoft offers critical and important security updates for up to three more years. Licensing prerequisites apply to delivery through Azure Arc, such as Software Assurance or a suitable subscription or SPLA license. Microsoft on ESU through Azure Arc

Have your eligibility and the costs checked in advance. At the same time, decide when the final replacement is to take place.

Switch off or isolate

During the inventory, you occasionally come across systems that are hardly used any more. Check whether applications or data are still needed and which retention obligations apply. The server can then be decommissioned in an orderly way.

If a legacy system has to stay for the time being, additional protective measures and a fixed end date are required. Isolating it on the network alone does not replace security updates.

Which target version: 2019, 2022 or 2025?

The approval of your applications is a key selection criterion. After that, it is worth looking at the remaining support period:

Version	Extended support until	Classification for planning
Windows Server 2019	January 2029	Comparatively short remaining term
Windows Server 2022	October 2031	Possible target version if the vendor has approved it
Windows Server 2025	November 2034	Longest term of the three versions

If Windows Server 2025 is suitable for your applications and hardware, this version offers the longest planning horizon. If your industry software is so far only approved for Windows Server 2022, that version can be the right choice.

Also check the lifecycles of your applications and databases. The term of the operating system says nothing yet about how long the whole environment is supported.

Decision aid: Which path for which server?

The following overview helps with a first classification:

Your starting point	What you should check
Hardware is current, applications are approved	Upgrade or new virtual machine
Hardware is old or maintenance has expired	New server environment and planned move
Several tasks on one server	Spread the tasks across separate systems
Own server room is to be dropped	Hosting or cloud
Industry software cannot be migrated yet	Temporary ESU bridge with a replacement plan
Server is no longer needed	Back up the data and decommission in an orderly way

Whether a solution makes economic sense depends on purchase costs, ongoing operation, support effort and the availability you need. We look at these points together with you.

Licenses, CALs and terminal servers

Clarify licensing early, so that it is already accounted for during implementation:

• Windows Server: Suitable usage rights must be in place for the target version. Existing Software Assurance may already include rights to newer versions.
• Access licenses: Check which user or device client access licenses, known as CALs, are required for the new environment.
• Virtual servers: Edition, processor cores and the number of Windows Server instances affect the license requirement. This also applies when a different virtualization system is used. Microsoft licensing guide
• Terminal servers: Suitable RDS CALs are required in addition. Older RDS CALs do not entitle you to access newer Windows Server versions. Microsoft on RDS CALs

On terminal servers, Microsoft 365 Apps also deserve special attention: Support on Windows Server 2016 and 2019 ended in October 2025, and on Windows Server 2022 in October 2026; Microsoft only provides security updates for the apps there until October 10, 2028. For Windows Server 2025, Microsoft currently names a support period until 2029. This deadline belongs in your planning, even if the operating system itself is supported for longer. Microsoft on Microsoft 365 Apps support

Timeline up to January 12, 2027

The year-end holidays fall immediately before the end of support. So plan changeovers with some distance from the turn of the year if possible. As a guide for the coming weeks:

• In November: Record systems, obtain vendor approvals and assign owners.
• By the end of November: Clarify the target environment, budget, licenses and required hardware.
• In December: Prepare new systems, test applications and carry out the agreed changeovers.
• Before the holidays: Have users sign off critical functions and document open points.
• By the deadline: Final check of remaining systems and activation of necessary interim solutions.

How much lead time your project needs depends on your inventory and applications. If it is already foreseeable that time will be tight, the interim solution should be planned in parallel with the migration.

Typical mistakes

1. Looking only at the visible device. Virtual machines and other systems in the background are easily overlooked.
2. Relying on past reliability. Trouble-free operation does not answer questions about security updates or vendor support.
3. Clarifying the software approval too late. It can largely determine the target version and the schedule.
4. Leaving backups untested. Before the changeover, it must be clear how the previous state can be restored.
5. Setting the deadline too tight. Delivery times, queries and failed tests need a reserve.

How to prepare backup and recovery sensibly is explained in our guide to the backup strategy for SMEs.

Are there legal implications?

If your server processes personal data, its security state is also part of the data protection assessment. Article 32 GDPR requires appropriate technical and organizational measures, taking into account the state of the art and the existing risks. GDPR, Art. 32 at EUR-Lex

Which measures are required depends on the individual case. Involve your data protection officer if a system is to continue operating without regular security updates. Also check possible requirements from customer contracts and your cyber insurance.

When outside help makes sense

Support is particularly worthwhile when several applications are interconnected, vendor approvals are unclear, or day-to-day work leaves no time for planning and testing.

We support you with:

• taking inventory of your servers and applications,
• selecting a suitable target environment,
• clarifying license and hardware needs,
• preparation, migration and functional testing,
• the subsequent operation and support.

We work out whether new on-premises servers, a virtual environment or hosting fits better based on your requirements.

Frequently asked questions

Will my server keep running after January 12, 2027?

Yes. The end of support does not lead to a shutdown. However, you should have decided beforehand how the server will be updated, protected or replaced in the future.

Can I upgrade directly from Windows Server 2016 to 2025?

Microsoft generally supports this upgrade path with the installation media. Whether it is suitable for your server depends on hardware, applications and server roles. Microsoft on upgrade paths

Do I need new hardware?

That depends on the condition and compatibility of your existing hardware. With older devices, it is worth considering the operating system change, maintenance and replacement purchases together.

What do I do if my industry software cannot be migrated yet?

First clarify with the vendor which version is supported and when an approval is to be expected. A suitable migration path or a temporary interim solution can then be defined.

Conclusion

The end of support for Windows Server 2016 is a concrete reason to review your server environment. An early inventory shows which systems are affected, which applications determine the schedule and where modernization pays off.

Are you unsure whether Windows Server 2016 is still in use in your company, or which solution fits? We go through your inventory with you and plan the next steps.

Arrange a no-obligation initial consultation with WSV.