If your Perth business is running an on-premises server, there's a deadline coming that your IT setup may not be ready for — and most small business owners won't hear about it until something goes wrong.
Microsoft's Windows Server end-of-life (EoL) schedule means that once a server version passes its support deadline, security patches stop entirely. The server keeps working — but every vulnerability found after that date stays permanently open. For a Perth SMB handling client data, financial records or any Privacy Act obligations, that's not a theoretical risk. It's a direct legal and operational exposure.
This guide explains which server versions are affected, what end of life actually means in practice, and the realistic options Perth businesses have for dealing with it — whether that's a hardware refresh, a cloud migration, or a hybrid of both. If Managed ICT Solutions is not already managing your server environment, this is the right time to have that conversation.
Windows Server 2016 reaches end of extended support on 12 January 2027. That's well under a year away — and server migrations take time to plan and execute properly. Perth businesses still on Server 2016 should be assessing their options now, not in December.
What "End of Life" Actually Means for Your Server
Microsoft follows a fixed lifecycle for every Windows Server version: a mainstream support phase (new features, bug fixes, security patches), then an extended support phase (security patches only), and finally end of life — when everything stops.
On the EoL date, your server doesn't switch off or refuse to work. Nothing dramatic happens on the day itself. What stops is Microsoft's commitment to find and fix security vulnerabilities in that version. Every security researcher, cybercriminal and automated scanner in the world continues looking for holes in old software — and after EoL, those holes stay open permanently, because there's no patch coming.
Why This Matters More Than It Used To
Ten years ago, running slightly outdated server software was a calculated risk that many small Perth businesses quietly accepted. The threat landscape has changed substantially since then. Ransomware groups now specifically target businesses running EoL infrastructure — it's lower effort to exploit a known, unpatched vulnerability than to find a new one. Automated tools scan the internet for EoL software signatures and flag them as high-value targets.
There's also an insurance dimension that Perth business owners increasingly need to understand. Cyber insurers have started including explicit exclusions for breaches that occur on EoL software. If your server is out of support when a ransomware attack hits, your insurer may decline the claim entirely — leaving you to cover remediation costs, data recovery, notification obligations and any regulatory response out of pocket.
Windows Server End-of-Life Schedule: Which Versions Are Affected
| Windows Server Version | End of Mainstream Support | End of Extended Support | Status |
|---|---|---|---|
| Windows Server 2012 / 2012 R2 | October 2018 | October 2023 | ● End of Life |
| Windows Server 2016 | January 2022 | 12 January 2027 | ● Act Now |
| Windows Server 2019 | January 2024 | 9 January 2029 | ● Extended Support |
| Windows Server 2022 | October 2026 | 14 October 2031 | ✓ Supported |
| Windows Server 2025 | October 2029 | 10 October 2034 | ✓ Current Release |
Windows Server 2012 and 2012 R2 have been unsupported since October 2023. If your Perth business is still running either of these, your server is operating without any security patches right now. This is an urgent situation — contact Managed ICT Solutions immediately for an assessment.
The Real Business Risks of Running an EoL Server
Cybersecurity Exposure
Unpatched servers are among the most common entry points for ransomware and data theft. Once Microsoft stops patching a version, every vulnerability discovered after that date becomes a permanent attack surface. Threat actors maintain updated databases of known exploits for EoL Microsoft products — your server can be scanned, fingerprinted and targeted without you knowing. Perth businesses that have experienced ransomware attacks are disproportionately running unpatched or EoL server software.
Cyber Insurance Complications
Most cyber insurance policies now include questionnaires during renewal that ask specifically about EoL software. Answering incorrectly is a policy breach. Answering correctly — that you're running EoL server software — may result in premium increases, coverage exclusions, or policy non-renewal. And if a breach occurs on an EoL system you failed to disclose, insurers have grounds to decline the claim entirely.
Compliance Obligations
Perth businesses in healthcare, financial services, legal and education all operate under obligations — the Privacy Act, APRA CPS 234, or sector-specific requirements — that include maintaining IT systems in a secure and supported state. Running EoL server software is increasingly being cited in breach notifications and regulatory responses as evidence of inadequate security controls. This matters particularly for any business that suffered an incident and is asked to demonstrate what security measures were in place.
Software and Hardware Compatibility
As server versions age, software vendors stop certifying their products against them. The accounting package, CRM, or line-of-business application your team relies on may drop support for Server 2016 or 2019 before Microsoft's EoL deadline. When that happens, you lose access to updates and eventually to the software itself — on a timeline you don't control. Hardware vendors similarly stop releasing drivers and firmware updates for older server operating systems.
Performance and Reliability
Older servers running EoL software tend to accumulate performance problems that can no longer be resolved via patches. Disk health, memory errors, network stack issues — without patches and without vendor support, these degrade gradually and often without warning until a critical failure. A server crash during business hours on a system with an aging EoL OS is a worst-case scenario: slow to recover, expensive to fix, and often avoidable with planned migration.
Your Three Paths Forward
Perth businesses facing an EoL server situation have three realistic options. Which one is right depends on what your server actually does, your budget cycle, and your longer-term IT direction.
Path 1: Hardware Refresh — New Server, New OS
Replace the aging server hardware with a new physical or virtual server running Windows Server 2022 or 2025, and migrate your workloads across.
- Best for: Businesses with software that must remain on-premises (specialised manufacturing, clinical, legal or POS applications); businesses with intermittent or limited internet connectivity; regulated environments requiring data sovereignty on-site
- Typical cost for Perth SMBs: $4,000 – $15,000 for hardware depending on spec, plus migration labour and licensing
- Timeline: 3–8 weeks from assessment to cutover for a well-planned migration
- Lifespan: A properly specified Server 2022 build gives you a supported runway to 2031
Path 2: Cloud Migration — Move Workloads to Azure or Microsoft 365
Migrate server functions to cloud services — file storage to SharePoint/OneDrive, email to Exchange Online, applications to Azure virtual machines or SaaS alternatives — and eliminate the on-premises server entirely or reduce it significantly.
- Best for: Businesses primarily using Microsoft 365, SaaS applications and shared file storage with no compelling reason for on-premises infrastructure
- Typical cost: Microsoft 365 Business Premium runs ~$32–$38 AUD per user/month; Azure VMs for hosted applications are priced per consumption
- Timeline: 2–6 weeks depending on complexity of data migration and application dependencies
- Ongoing benefit: No hardware refresh cycles, Microsoft handles OS patching, built-in disaster recovery and geographic redundancy
Path 3: Hybrid — Some Cloud, One Streamlined On-Premises Server
Move suitable workloads to cloud (file sharing, email, backup) while retaining a single modernised on-premises server for applications that genuinely need to stay local.
- Best for: Most mid-sized Perth businesses — particularly those running a mix of cloud-based and on-premises applications, or those with specific software that can't move to cloud yet
- Typical cost: Combines a modest hardware spend with Microsoft 365 licensing; often results in lower total cost than a full hardware refresh
- Timeline: 4–8 weeks depending on complexity
- Practical result: A lighter, more modern server environment that's easier and cheaper to manage going forward
For most Perth SMBs we work with, the hybrid path delivers the best outcome — cloud for collaboration, file sharing and backup, a streamlined on-premises server only for what genuinely needs to stay local. It's usually cheaper than a full hardware refresh over five years, and significantly more resilient than an all-on-premises setup. We assess each client's specific application stack before making any recommendation.
What to Check on Your Server Right Now
Before any planning conversation, it helps to know what you're actually dealing with. Here are the key things to establish:
Which Windows Server version are you running?
On the server, open Command Prompt and type winver — this shows the exact OS version and build number. If you see Server 2012, 2012 R2, or Server 2016, you're either already past EoL or approaching it fast. Alternatively, your IT provider should be able to tell you immediately — if they can't, that's a signal in itself.
What roles is your server actually performing?
Common server roles for Perth SMBs include: file server (shared network drives), Active Directory / domain controller, print server, Remote Desktop Services (RDS), on-premises email (Exchange), line-of-business application host, or backup target. Knowing which roles are in use tells you which workloads can move to cloud and which need to stay on-premises — this determines your migration path.
What software is running on the server?
Make a list of every application installed on or served by the server — accounting software, CRM, practice management, ERP, POS back-end, or anything else staff access. Check whether each application supports Windows Server 2022 or 2025, and whether a cloud or SaaS version exists. Software compatibility is one of the most common sources of delay in server migrations — discovering it early avoids nasty surprises mid-project.
Is your backup actually working?
Before any migration, verify your current backup is complete, recent, and restorable. Many Perth businesses discover during migration planning that their backup jobs have been silently failing for months. A server migration without a verified backup is a high-risk exercise — if something goes wrong mid-migration and your backup is broken, you have no fallback. Test a restore from backup before you start any migration work.
When is your cyber insurance renewal?
Cross-reference your cyber insurance renewal date with your migration timeline. If renewal is in the next six months, it's worth getting your EoL situation resolved before then — both to avoid exclusion questions and to potentially reduce your premium. Insurers increasingly reward demonstrably up-to-date, managed infrastructure with more favourable terms.
Real Perth Business Scenarios
Here's how the EoL situation plays out across different types of Perth businesses we work with.
File server, one accounting application (MYOB AccountRight), and Active Directory on a single Server 2016 box. MYOB supports Server 2022, file sharing is moving to SharePoint, Active Directory will remain on a new Server 2022 VM hosted on a refurbished hardware platform. Hybrid path. Migration planned for six weeks, cutover on a Saturday. Total cost: approximately $7,200 including hardware, licensing and labour. Done well before the January 2027 deadline.
Already past EoL since October 2023. Running Best Practice clinical software and storing patient records locally. Best Practice supports Server 2022 and has an Azure-hosted option. Practice data has not been encrypted — it has not been breached yet, but the window of exposure is real. Immediate remediation: new Server 2022 hardware plus a move to cloud backup. Urgent timeline: four weeks. This is a situation where Managed ICT Solutions recommends treating it as a priority rather than scheduling it for the next available slot.
Extended support runs to January 2029 — not an immediate crisis, but a planning conversation worth having now. CAD software runs locally, files are large, on-premises storage makes sense. Recommendation: continue on Server 2019 for now but plan for a migration to Server 2025 by 2027–2028, move backup to cloud immediately, add monitoring. No panic needed — but no ignoring it either.
Point-of-sale system runs on a central server, inventory management, staff rostering. POS vendor confirmed compatibility with Server 2022. Recommended path: new hardware, migrate POS and inventory to Server 2022, move file sharing and email to Microsoft 365. The third location opening next quarter is the perfect trigger — set it up correctly from day one rather than replicating the old setup. Full migration including third-site setup: eight weeks.
What the Migration Process Looks Like
A well-run server migration from an experienced Perth IT provider follows a clear sequence. Rushed migrations that skip steps are the primary cause of post-migration problems.
IT Assessment & Discovery
A thorough inventory of your current server — roles, software, data volumes, Active Directory configuration, connected devices, printers, network shares and user access permissions. This is where the migration path is determined. Managed ICT Solutions conducts this as a documented assessment, not a verbal conversation — you should have a written report at the end of this phase.
Migration Plan & Timeline
A detailed plan covering which workloads move where, in what order, with cutover date and rollback procedures documented. For Perth businesses with client-facing operations, cutovers are typically scheduled for a Friday night or Saturday to give the weekend as a buffer before Monday business resumption.
Pre-Migration Testing
New server built and configured in parallel with the existing one. Applications tested, user access verified, backup confirmed working on the new system before the cutover date. This parallel-run phase is what separates a smooth migration from a stressful one — issues found here are caught before staff are affected.
Cutover & Validation
Final data sync, DNS and network pointing updated, staff redirected to new server, confirmation that all applications and shared resources are functioning. A structured checklist is run through before the migration is declared complete — not a "seems fine, let's go" sign-off.
Post-Migration Monitoring & Handover
Active monitoring of the new environment for 2–4 weeks post-migration to catch anything that wasn't surfaced in testing. Documentation updated. Old server hardware decommissioned securely — data wiped to DoD standard before disposal. Ongoing managed IT support continues under your existing or new managed services agreement with Managed ICT Solutions.
Frequently Asked Questions
What does Windows Server end of life mean for my Perth business?
When a Windows Server version reaches end of life, Microsoft stops releasing security patches for it. Your server continues operating, but every vulnerability discovered after that date stays permanently unpatched — making it a high-value target for ransomware and data theft. For Perth businesses with Privacy Act obligations or cyber insurance requirements, running EoL server software also creates direct legal and financial exposure.
Is Windows Server 2016 end of life?
Not yet — but the deadline is approaching fast. Server 2016 reaches end of extended support on 12 January 2027. Given that server migrations typically take 4–8 weeks to plan and execute properly, Perth businesses still on Server 2016 should be starting their assessment now to avoid a rushed migration close to the deadline.
Can I just keep using my server after end of life?
The server will keep running, but without security patches, every unresolved vulnerability becomes permanent. Cyber insurers increasingly exclude coverage for breaches on EoL software — meaning a ransomware attack on an unpatched server could leave you with no insurance payout. Microsoft offers paid Extended Security Updates (ESUs) for some versions, but these are expensive and only delay the problem. They're not a substitute for migration.
Should I upgrade hardware or move to the cloud?
It depends entirely on what your server does. If you're running specialised on-premises software (clinical, manufacturing, legal), a hardware refresh to Server 2022 or 2025 is likely the right call. If your server mainly handles file sharing, email, and Microsoft 365 adjacent workloads, migrating to cloud is often more cost-effective long-term. Most Perth SMBs end up with a hybrid — some workloads to cloud, one streamlined on-premises server for what genuinely needs to stay local. Managed ICT Solutions assesses this case by case, not with a one-size answer.
How long does a server migration take?
For a typical Perth SMB with 10–30 users, a well-planned server migration takes two to six weeks from assessment to cutover — with the actual cutover happening over a weekend. The bulk of that time is planning, parallel testing and data validation, not the migration itself. Migrations rushed without proper testing are the most common cause of post-migration problems that affect staff productivity the following Monday.
Not Sure Where Your Server Stands? We'll Find Out for You.
Managed ICT Solutions offers a free server assessment for Perth businesses — we'll identify your exact server version, check your EoL status, review your backup integrity, and give you a clear migration recommendation with no obligation. If your server needs attention, we'll tell you honestly. If it doesn't, we'll tell you that too.
Book a Free Server Assessment Call (08) 9242 4511