Windows Server 2016 reaches end of extended support on 12 January 2027, after which Microsoft stops issuing security updates for it. Windows Server 2012 and 2012 R2 passed that point in October 2023. bcom ICT audits what the server actually does, then plans the right answer — replace it, move the workload to Azure, or retire it entirely. Call 07 3041 8993.
Microsoft lifecycle dates are published by Microsoft and occasionally revised. Confirm the current date for your exact version and edition on Microsoft's lifecycle documentation before making a decision that depends on it. Reviewed September 2026.
The dates that matter
Windows Server 2012 / 2012 R2
Support ended October 2023. Any of these still running have had no security updates for nearly three years.
Windows Server 2016
Extended support ends 12 January 2027. That is roughly four months away, and it is the one catching Gold Coast businesses right now.
Windows Server 2019
Extended support ends January 2029. Not urgent, but it is the one to plan the budget around.
Windows Server 2022 / 2025
Current. If you are replacing now, this is what you land on.
Nothing breaks on the day
That is what makes this easy to ignore. On 13 January 2027 a Windows Server 2016 machine will start up, serve files, run the application and behave exactly as it did the day before. No warning appears. Nobody notices.
What stops is the flow of security updates. Every vulnerability discovered from that point onward stays open on that machine, permanently. The risk does not arrive on the day — it accumulates quietly afterwards, which is why the businesses that get caught by this are almost never the ones who decided to take the risk. They are the ones who never had the conversation.
There is a second dimension now too. Clients, insurers and security questionnaires increasingly ask directly whether systems are supported, and “it still works” is not an answer that survives that question.
What to actually do about it
In roughly the order we would consider them, and the last one is a legitimate choice if it is made deliberately.
1. Replace the server
New hardware, current Windows Server, same architecture. Suits a business with a line-of-business application that needs a real server, a good connection to it, and no appetite for change.
2. Move the workload to Azure
The application keeps running on Windows, just not in your cupboard. Suits businesses with multiple sites, or where the server room is the weakest link.
3. Retire it entirely
A surprising number of servers now exist to run file sharing and a print queue. Both of those moved to Microsoft 365 years ago and nobody revisited the server.
4. Do nothing, deliberately
Sometimes defensible for a short, bounded period with the server isolated. It should be a decision with an end date, not a drift.
The question we would ask first is not which of these you want. It is what does the server actually do? That answer decides the rest, and it is surprisingly often not what the business thinks.
What we hear about server replacement
“It is running fine, so what is the actual risk?”
Usually a server doing its job on an operating system that stopped receiving security updates. Nothing visibly changes on the day support ends, which is exactly the problem.
What we do The exposure is not performance, it is that newly discovered vulnerabilities stop being fixed. For a business handling client or health information, that is also increasingly a question your insurer and your clients will ask about.
“Nobody knows what the server actually does”
Usually a box that has accumulated roles over a decade — files, print, a licensing service, a nightly data exchange, a share somebody scripted against years ago.
What we do Audit what depends on it before planning anything. We have found a server everyone described as a file server also running the licence service for the industry application, which nobody mentioned because nobody knew.
“We were quoted for a new server and it seemed like a lot”
Usually a like-for-like replacement quoted without asking whether the business still needs a server at all.
What we do Establish what the workload actually is first. If it is file sharing and printing, the answer may be no server, and that conversation should happen before anyone prices hardware.
“We will move it to the cloud, that will be cheaper”
Usually an assumption that frequently does not survive contact with a bill. A steady always-on workload can cost more per year in Azure than owning the equivalent hardware.
What we do Model the actual running cost over three years against replacement, including the connection you will need. Cloud wins on flexibility and resilience far more often than it wins on price.
“Our line-of-business software vendor says it needs a server”
Usually sometimes true and sometimes a version behind. Vendors update their hosting options and their documentation does not always keep pace.
What we do Ask them directly what they support now, including hosted options. It is a ten-minute call that occasionally removes the whole project.
“We have backups, so a migration is low risk”
Usually backups nobody has restored from. A migration is the moment you discover whether they work, and that is a bad moment to find out.
What we do Test a restore before the migration, not as part of it. It is the cheapest insurance available on a project like this.
What a server audit turns up before anyone quotes
A representative engagement, drawn from real work with client and staff names removed.
The server replacement they did not need
The situation
A business of eighteen staff was quoted for a new server after being told their Windows Server 2016 machine was approaching end of support. The quote was substantial and the reasoning was sound, so they asked us for a second opinion before signing.
What we found
Auditing what the server actually did found two things: a file share, and a print queue. That was the whole workload. Both had been moved to Microsoft 365 four years earlier during a separate project, and staff had been saving to SharePoint ever since. The server was still switched on, still being backed up, and still carrying a maintenance line in the budget, but the only thing genuinely depending on it was an old mapped drive on three machines that nobody had repointed.
What we did
Repointed the three mapped drives, verified nothing else touched the server across a fortnight of monitoring, migrated the remaining print queue to a direct network configuration, and decommissioned the machine.
The outcome
No server was purchased. The business removed a maintenance cost, a backup target and a security exposure at the same time, and the only work required was two hours of checking what actually depended on it. The quote had not been wrong — the question had simply never been asked.
Questions Gold Coast businesses ask us
When does Windows Server 2016 reach end of support?
12 January 2027. After that date Microsoft stops issuing security updates for it, and any newly discovered vulnerability stays unpatched. Windows Server 2012 and 2012 R2 already passed end of support in October 2023. Windows Server 2019 runs until January 2029. Confirm current dates on Microsoft's lifecycle documentation before acting on anything time-sensitive.
What happens if we keep running an unsupported Windows Server?
It keeps working — nothing breaks on the day. What stops is security updates, so every vulnerability found from that point onward remains open. For businesses handling client, health or financial information, it also becomes something your insurer and your clients may ask about directly, and 'it still works' is not an answer that survives a security questionnaire.
Should we replace the server or move to the cloud?
It depends on what the server actually does. If it runs a line-of-business application that needs to be close to your staff and your connection is unremarkable, replacing it is often the right answer. If you have multiple sites, or the server room is genuinely the weakest link in the business, moving the workload to Azure makes more sense. And a surprising number of servers now exist to share files and run a print queue, both of which moved to Microsoft 365 years ago.
Is moving to Azure cheaper than a new server?
Often not, and anyone telling you otherwise has not modelled it. A steady always-on workload can cost more per year in Azure than owning the hardware outright. Azure wins on flexibility, resilience and not owning a box in a cupboard — which are good reasons — but it should be chosen on those rather than on an assumption about price.
How long does a server migration take?
Planning is weeks; the cutover is usually a weekend. Most of the work is establishing what actually depends on the server, because that is where migrations go wrong — a scheduled task, a licensing service or a nightly data exchange nobody documented.
Can you migrate without downtime?
Rarely entirely, and we would not promise it. What we do commit to is a cutover scheduled outside trading hours, with a tested way back and an agreed point at which we revert regardless of progress. That preparation is the difference between a failed cutover and a lost week.
Still running 2016?
We will audit what the server actually does before anybody quotes anything. Occasionally the answer is that you no longer need one.