Windows Server 2016 End of Support: An MSP Action Plan

Microsoft ends support for Windows Server 2016 on January 12, 2027. After that, Microsoft will stop shipping security updates for the operating system. It will be with one exception, though: servers enrolled in the paid Extended Security Updates program. Servers will not stop working that day. They boot the next morning as usual, which is why the date is easy to push down the to-do list. Every server still running Windows Server 2016 after that date needs a decision: upgrade it, migrate it or cover it with ESU.

Windows Server 2016 End of Life: Key Dates and What Follows

The date is January 12, 2027, when extended support closes under Microsoft’s lifecycle policy. Mainstream support already ended way back in January 2022. It essentially means the product has been getting security patches and little else for almost 5 years. Those will also stop after the January date.

On the day itself, servers carry on as usual. The trouble accumulates afterwards, and below are the places it tends to show up:

• Vulnerabilities found after January 12 stay unpatched on any server without ESU coverage.

• Microsoft’s technical support for the product ends, apart from the narrow help that comes with ESU.

• Compliance frameworks and cyber insurance questionnaires commonly ask whether systems run supported software, so an unsupported server can become a finding on a client’s next review.

Source:

Current releases stand as follows:

Windows Server 2022 deserves a closer look. Its mainstream support ended recently on October 13, 2026, so a Windows Server 2022 upgrade gives a client security patches until October 2031 without any feature updates or other fixes.

Windows Server 2016 Upgrade Options: Top Four Options MSPs Can Consider

A Windows Server 2016 upgrade comes down to four routes, and one client’s estate often ends up using more than one. Below are listed a few practical Windows Server 2016 migration options:

A 2016 server doesn’t have to step through 2019 or 2022 on the way to Windows Server 2025. If it isn’t part of a cluster, one in-place upgrade covers the whole move.

From Windows Server 2025 onward, Microsoft’s upgrade documentation allows jumps of up to four versions, where earlier releases allowed two.

For most clients, a Windows Server 2025 upgrade is the stronger choice, as mainstream support runs until November 2029 and extended support until November 2034. Windows Server 2022 is the fallback when an application vendor hasn’t certified Windows Server 2025.

For clients looking to move their on-premises servers to Azure, Windows Server 2016 migration to Azure is an alternative. Azure Migrate can assess the servers before anything moves. For MSPs that want help with the move itself, Infrassist offers Azure cloud migration services.

No matter which path you choose, frame the project as server modernization rather than a version bump, and use the legacy server migration to retire roles clients no longer use.

Is Windows Server 2016 ESU a Long-Term Solution?

No. Microsoft’s own ESU FAQ calls the program a last-resort paid option and a temporary bridge to a newer platform.

Windows Server 2016 extended security updates carry critical and important fixes only, for up to three years past the end-of-support date, which means through 2030. New features, non-security fixes and standard technical support aren’t part of the deal.

Outside Azure, Windows Server 2016 ESU is delivered through Azure Arc. You can enroll in the Azure portal since August 3, 2026, but customers who enroll late are back-billed to January 12, 2027, the end-of-support date. Monthly charges depend on the core count, edition, and applicable discounts.

Licensing limits the options for MSPs in particular. ESU requires Software Assurance or an equivalent server subscription, and Microsoft states that the Services Provider License Agreement (SPLA) is not available for Windows Server 2016 ESUs. A hosted server licensed through SPLA has to be upgraded or moved, because it cannot be covered.

Before quoting Azure ESU costs, verify Microsoft’s current pricing and eligibility terms for Windows Server 2016. Do not assume that the free security update terms published for Windows Server 2012 and 2012 R2 also apply to Windows Server 2016.

What MSPs & End Businesses Should Do Before Windows Server 2016 EOL

Plan the order of work

Planning for Windows Server 2016 end of support works best in a set sequence, since every step feeds the one after it.

1. 1. Build the inventory. Export every 2016 instance from the RMM platform and compare the list with client documentation, because virtual machines built for a one-off project often appear in neither. Teams that outsource RMM services can ask the provider for the same export.
2. 2. Sort each server by role and risk. A domain controller, a file server and a server hosting a line-of-business application each need a different plan and a different window.
3. 3. Get the application vendor’s answer in writing on which Windows Server versions it supports. A written reply protects the MSP if the application misbehaves after the upgrade.
4. 4. Confirm licensing server by server, including Software Assurance status, edition and any hosting arrangement. ESU eligibility depends on those details.
5. 5. Quote the work and book the windows. Put internet-facing and high-risk servers at the front of the queue, so any slippage lands on the safer ones.

Checks to Complete Before a Server Upgrade

Fold these checks into your scheduled audits and the results land in the client record before anyone opens the installer.

• A recent backup, with proof that it restores.

• Free disk space for setup, and a snapshot or image to roll back to if the upgrade goes wrong.

• Firmware, drivers and hardware support for the target version on physical hosts.

• Whether the backup, antivirus and monitoring agents on the box support the new version.

Downtime reduction during a server migration

Most downtime comes down to how much gets finished before the window opens. With a side-by-side move the old server keeps serving users until cutover. An in-place upgrade doesn’t have that luxury, since the server is offline while setup runs.

1. 1. Build and patch the target server ahead of time, so the window is spent on cutover rather than installation.
2. 2. Copy data early, then sync only the changes just before cutover.
3. 3. Drop the DNS TTL a day or two before cutover. Clients then pick up the new address fast.
4. 4. Fix a go or no-go time with the client in advance. Testing that hasn’t passed by then means a rollback.
5. 5. Once cutover finishes, confirm sign-in, shares and the main application work before declaring the server live.
6. 6. Keep the old server powered off but untouched for an agreed period. Some problems only surface after a full day of real use.

Server Maintenance Once the Upgrade Is Done

The upgrade ends the project, but the server’s maintenance cycle starts over. Baselines taken on the old version no longer apply, which makes the first weeks the time when server monitoring and maintenance needs the closest attention. MSPs often split that work between the helpdesk and a managed NOC that handles alerts and routine checks.

1. 1. Cutover day: check services, scheduled tasks, certificates and activation against the pre-upgrade list.
2. 2. Watch logs and system alerts for the first seven days, since some bugs only pop up once real users start using the server.
3. 3. Recalculate alert thresholds from fresh baselines. CPU and memory profiles can shift between versions.
4. 4. Bring asset records, network diagrams and credentials up to date, then close the project ticket.

Source:

After the first month, managed server maintenance settles into a routine of its own:

• Server patch management on a monthly cycle, with a small test group patched before the rest.

• CPU, memory and disk latency tracked through server performance monitoring, with alerts tied to the new baselines.

• Restore tests built into server backup and recovery, so a green job status is not the only evidence.

• Remote server monitoring and management through NOC monitoring, so alerts get triaged without waiting for the MSP’s own team to log in.

How Infrassist Supports Server Upgrades and Maintenance for MSPs

Team Infrassist works behind MSPs, which suits a deadline that hits many clients at once.

On the project side, Infrassist engineers can take on the inventory, compatibility checks, migration and post-cutover validation as white label server upgrade services delivered under the MSP’s own brand. An MSP that decides to outsource server migration this way keeps the client relationship and still gets extra hands for the busy months. Before anything is handed over, the MSP and Infrassist should settle scope, access and escalation paths and how reporting will work.

After the upgrade, NOC server maintenance services cover routine patching, performance monitoring and backup checks. Infrassist also provides white-label server upgrade and migration support, allowing MSPs to manage the project and ongoing maintenance under their own brand.

Conclusion

Windows Server 2016 end of support isn’t moving, and the work is simple enough to describe in one breath: find every 2016 server, choose a route, book the windows and keep maintaining the servers once they reach a supported release. Completing the planned work well before January 12, 2027, gives teams time to test changes and resolve issues before support ends. Treating the effort as server infrastructure modernization, rather than a one-off patch exercise, can also leave clients with a tidier estate.