| Windows Server end of life is the end of Microsoft’s standard extended support for a release. The software can continue running, but normal security updates and support end. Eligible Extended Security Updates may provide a temporary, limited bridge for some versions; they do not renew the full support lifecycle. |
An old server can keep working after it reaches Windows Server end of life, when Microsoft’s standard support ends. The practical question is which version it runs, whether security updates are still available, and what depends on it. This guide sets out the dates and the choices before you commission a change.
As checked on 14 October 2026, Windows Server 2012 and 2012 R2 are beyond their published ESU period. Windows Server 2016 still receives standard security updates until 12 January 2027. Confirm the installed version and plan the destination for each workload rather than assuming every old server needs the same replacement.
The sections below cover the current Windows Server end of life dates, what Extended Security Updates do and do not provide, how to identify the version you run, what to record before choosing a destination, the options for each workload, cost, and how to plan the move with a path back.
What are the current Windows Server end of life dates?
The table lists the Windows Server end of life date, meaning the end of standard support, for each long-term release, with its position as checked on 14 October 2026. Dates follow Microsoft’s Windows Server release information, which publishes them in US Pacific time. In New Zealand, each cut-off falls during the following day.
| Version | Standard support ends | Position now |
|---|---|---|
| 2012 and 2012 R2 | 10 October 2023 | Standard support ended. The published ESU period ended on 13 October 2026. |
| 2016 | 12 January 2027 | Standard security updates continue. Microsoft has announced an ESU option. |
| 2019 | 9 January 2029 | In extended support. Standard security updates continue. |
| 2022 | 14 October 2031 | Mainstream support ended on 13 October 2026. Standard security updates continue. |
| 2025 | 14 November 2034 | Current long-term release. Confirm workload and vendor suitability. |
Mainstream support ending is not the same as security updates ending. During extended support, Microsoft continues to release security updates but stops non-security feature changes. That distinction matters for Windows Server 2022 now: its mainstream support ended on 13 October 2026, and standard security updates continue until 14 October 2031.
Specialist editions and other release channels follow their own dates, so check them separately. Windows Server end of life applies to the operating system, not to the hardware it runs on or to the applications installed on it.
What do Extended Security Updates cover?
Extended Security Updates (ESU) provide limited security updates for eligible products after standard support ends. According to Microsoft’s ESU lifecycle FAQ, the programme does not extend the product’s lifecycle and does not add new features or non-security fixes.
- What ESU provides. Critical and important security updates for an eligible release, for a defined period after its extended support ends.
- What it does not provide. A renewed support lifecycle, new features, non-security fixes or general technical support for the release.
- Windows Server 2012 and 2012 R2. The published ESU period, including the route for workloads hosted in Azure, ended on 13 October 2026. It is no longer a current option.
- Windows Server 2016. Microsoft has announced an ESU programme. Confirm eligibility, deployment route, terms and cost before treating it as a bridge.
Do not assume ESU prices rise on a fixed scale. Microsoft’s published commercial pricing for 2012 and 2012 R2 used the same percentage for each annual period, and current programme, eligibility and billing terms need checking for any later release. Give any bridge an agreed exit date, because ESU buys time to move rather than a place to stay.
For a 2016 server, the practical decision is timing. If its workloads cannot move before the Windows Server end of life date of 12 January 2027, compare the cost and terms of a short ESU bridge with the cost of bringing the project forward, and record which applies to each server.
Can you keep running a server after Windows Server end of life?
The server will keep running, which is why an unsupported release can stay in place long after its Windows Server end of life date. Normal security updates stop, so a weakness discovered later may stay open on that release. The exposure depends on what the server does, who can reach it and what it connects to.
Restricting network access, removing internet exposure and monitoring the server can reduce risk while a move is planned. Those steps do not restore vendor support, so treat them as a time-limited transition with an agreed end.
Be careful with claims about legal and insurance consequences. An unsupported server does not automatically void cyber insurance or breach the Privacy Act. Policy wording, the representations made to the insurer and the circumstances all matter, so ask your broker or insurer about the actual condition of your systems. Information privacy principle 5 requires security safeguards that are reasonable in the circumstances; it does not prescribe a particular Windows Server version. Our guide to the Privacy Act and cybersecurity explains that principle in more detail.
Application support is a separate question. A line-of-business vendor may stop supporting its product on an older release before or after the Microsoft date, so check each application against its own vendor requirements.
How do you find out which version a server runs?
Before planning for Windows Server end of life, record the operating system version and edition for every physical host and virtual machine. Hardware age and purchase date do not identify the operating system or establish its maintenance history, and a server bought in one year may run a release from another.
The version and edition appear in the server’s system information and in management tools your IT provider uses. Check the build and update status as well as the name, because two servers on the same release can sit at different update levels.
The long-term releases in current use are 2012, 2012 R2, 2016, 2019, 2022 and 2025. Searches sometimes mention other years, such as Windows Server 2015 or 2021, that do not match any long-term release. If a record names a version you cannot match to the table, check the server itself before planning around a date. Annual and semi-annual channel releases have their own, shorter lifecycles.
What should you record before choosing a destination?
A single older server can carry several roles at once: file storage, printing, the domain controller that handles logins, a database and a line-of-business application. Record each one before deciding where it goes.
| Record | Why it affects the decision |
|---|---|
| Version and coverage | Operating system, edition, update status, any ESU entitlement and its end date. |
| Workloads and owners | Files, print, directory, database, applications and scheduled jobs, each with a business owner. |
| Dependencies | Devices, users, service accounts, integrations, DNS and applications that rely on each role. |
| Vendor requirements | Supported application, database, drivers and backup tooling for the proposed destination. |
| Recovery and costs | Backup restore checks, acceptable interruption, licences, migration and ongoing management. |
Directory roles need particular care. If the server runs Active Directory, the move needs a planned transfer of roles, replication checks and a clear order for retiring the old domain controller. Our Active Directory management service covers keeping logins and access working through that change.
The inventory can also surface forgotten work: a scheduled task, a service account used by another system, or a backup job writing to storage that is no longer checked. Finding these before the move keeps the change planned rather than reactive.
What are your options at Windows Server end of life?
Choose the route for each workload rather than for the server as a whole. Different roles on the same machine may suit different destinations, and the routes below are alternatives rather than a sequence to follow in order.
- Upgrade existing hardware. Where the platform, roles and vendor requirements support it. Compare a fresh build with an in-place upgrade. Microsoft’s upgrade overview supports some nonclustered in-place paths to Windows Server 2025 from 2012 R2 onward, but not every role or configuration.
- Replace hardware and software. Where condition, capacity, warranty or support makes new hardware sensible, with a supported software stack on it. Our IT infrastructure service covers server refreshes.
- Move to supported hosting or cloud. Compare supported hosted infrastructure with a suitable cloud service. Microsoft 365 can suit collaboration and some file needs, but it does not replace every server role. Our cloud migration services cover hosted destinations.
- Consolidate or retire. Consolidate onto supported infrastructure, or retire unused roles after checking dependencies and retention. Server virtualisation can reduce hardware, but virtualising an unchanged unsupported release does not solve its lifecycle problem.
Confirm the source and destination release, roles, edition, drivers, capacity, licences and application vendor requirements before committing to any route. Do not assume that every old server can upgrade directly, or that every move needs intermediate releases.
Does moving to the cloud or virtualising fix the support date?
No. Moving a server into a virtual machine, on your own hardware or in a cloud, leaves the operating system version and its support date unchanged. A supported host does not make an unsupported guest supported.
The responsibility also depends on the service model. With infrastructure as a service, such as a virtual machine in Azure, your business or its appointed provider still manages the guest operating system and the applications on it. With software as a service, such as Microsoft 365, Microsoft manages the platform and your business manages its users, data and settings. For any destination, agree in writing who handles updates, access, backups and recovery.
Hosting changes where a server runs; it does not change the Windows Server end of life date for the release. Retire or replace the workload on a supported platform, and check application, database and backup-agent support separately for the destination you choose.
How do you compare the cost of each route?
Compare the full cost of each response to Windows Server end of life over the period you plan to run the result, not only the upfront price. An in-place upgrade is not automatically the cheapest route, and cloud services carry setup and migration costs as well as recurring charges.
- Hardware. New servers, storage or networking, and any warranty or support contract.
- Licences. Server and access licences, plus any application or database licences affected by the change.
- Project work. Application changes, migration, data transfer and testing.
- Running costs. Hosting, monitoring, support, backup and recovery for the destination.
A quote should state its assumptions, inclusions and any separately charged work, so different routes can be compared on the same basis.
How do you plan the migration and the path back?
Moving off a server at Windows Server end of life is a project with a start and an end. Agree acceptance tests, interruption, final synchronisation, communication and rollback criteria before the move starts. Planning reduces risk without guaranteeing an uninterrupted or loss-free move.
Check recovery first
Confirm that current backups restore correctly before anything changes, and record what a restore would and would not bring back. A migration plan that relies on an untested backup carries more risk than it appears to.
Agree tests and interruption
Write down the acceptance tests, the expected interruption, the communication to staff and the criteria for stopping or rolling back. Agree who signs off each workload.
Move and synchronise
Transfer data and configuration, then complete a final synchronisation at cutover so changes made during the move are not lost. Directory, DNS and file permissions need particular care.
Test real work and reconcile
Test real logins, application transactions, file access and printing after the move. Reconcile any changes made after cutover, and record who now looks after updates, access, backups and recovery.
Retire the old server
Keep the old environment only within a valid recovery plan. Restrict access, set its retirement date, and remove obsolete connections and data as agreed.
A path back needs designing for each workload. A restored copy is not automatically current, because changes made after cutover need reconciling, and a demoted domain controller cannot simply be switched back on as a universal rollback. Keep the technical recovery design in the project scope rather than assuming it.
Windows Server support from Exodesk
Exodesk can scope the workloads on a server approaching or past Windows Server end of life, compare destinations and plan the move around the work that cannot stop. Server refreshes sit with our IT infrastructure service, hosted destinations with cloud migration, and ongoing support date tracking with managed IT services.
Exodesk has supported New Zealand businesses since 1989. Today, our Christchurch and Dunedin teams support businesses nationwide.
NEXT STEP
Have a server approaching or past its support date?
Tell us the server version if you know it, the main applications it runs and the work that cannot stop. Please keep passwords and business records out of the enquiry.
Or see our cloud migration services.
Frequently Asked Questions
What does Windows Server end of life mean for my business?
It marks the end of standard extended support for a release, including normal security updates. The server may keep working. Any remaining Extended Security Updates coverage is separate and limited, so confirm the version, the coverage and the systems that rely on the server before choosing the next step.
Can I keep using a server after it reaches end of life?
The software can continue running, but normal updates and support have ended. Restricting access and monitoring the server may reduce exposure while you move, but they do not restore vendor support. Agree a time-limited transition and a supported destination, and check whether a current ESU programme applies.
Which Windows Server versions have reached end of life?
As checked on 14 October 2026, Windows Server 2012 and 2012 R2 are beyond standard support and beyond their published ESU period, which ended on 13 October 2026. Windows Server 2016 still receives standard security updates until 12 January 2027. Later releases have separate dates, shown in the table above.
What are my options when a server reaches end of life?
Upgrade on suitable existing hardware, replace the hardware and the supported software stack, move a workload to supported hosted infrastructure or a suitable cloud service, or retire an unused role. Different roles may need different routes. Virtualising the same old operating system does not reset its support date.
How long does it take to migrate off an old server?
Timing depends on the roles, data, application compatibility, vendor work, testing and the change window. Agree milestones and expected interruption once the requirements are understood. A small server can still support critical dependencies, so its size alone does not determine the length of the project.
How much does it cost to replace an end of life server?
Compare the complete project and ongoing cost: hardware, licences, application changes, data transfer, testing, hosting, support and recovery. An in-place upgrade is not automatically the lowest-cost route. The quote should state its assumptions, inclusions and any separately charged work.
Is it better to upgrade my server or move to the cloud?
Choose by workload, vendor support, access, connectivity, recovery and full cost. Some roles fit Microsoft 365 or another cloud service, while others need a supported local or hosted server. With a cloud virtual machine, the operating system and applications still need agreed management, and a mix of routes may suit best.
What happens to my data during a server migration?
The plan sets out backup and restore checks, data transfer, final synchronisation, permissions and acceptance tests. Rollback depends on the workload and on changes made after cutover. Verify the new system and reconcile records before retiring the source, because a backup does not guarantee that every recent change can be recovered.
Can Exodesk manage the whole server migration?
Exodesk can scope the workloads, compare destinations and plan the migration around agreed operating requirements, with teams in Christchurch and Dunedin supporting businesses nationwide. The proposal sets out vendor responsibilities, expected interruption, recovery, costs and ongoing management, and the old server is retired only after the new setup has been accepted.
Contact us or call 0800 396 337 to talk through a server you are unsure about.
