Before you price a replacement for a Windows Server 2016 machine, list what it actually does. In a small office it's usually 3 or 4 roles on one box, and each role moves on its own timeline. Give each role a date and a cost of waiting, and you'll see that the slowest one, usually an older app, sets the schedule for everything else.
That's the short version. Here's how I work through it with small offices ahead of the January 12, 2027 end of extended support.
The problem
Microsoft's lifecycle page lists extended support for Windows Server 2016 ending January 12, 2027. The server keeps booting after that. What stops is security fixes, and cyber insurance applications ask whether you run unsupported systems.
The trap is treating the server as one line item. Someone asks for a quote on a new server, the quote sits in an inbox, and nothing moves, because the hardware was never the hard part.
How a typical small office server breaks down
In the offices I work with, a Server 2016 box usually carries some combination of these roles.
Role What it does Typical path What sets the timeline
File share Shared folders for the team Move the files to SharePoint Usually a weekend of work
Domain controller Handles sign-ins Plan the identity move before anything else depends on it Needs planning
Print server Runs the office printers Rebuild on the new setup Small
Line-of-business app An older accounting or practice app Depends on the app vendor The vendor decides which newer server versions it supports
The table isn't exhaustive, and your box may run something else. The point is the last column. The file share is fast. The app is the slow part, and it's slow for a reason you don't control.
Steps
Inventory the roles. List every job the server does today. Ask the people who use it, not just the person who set it up.
Contact the app vendor first. Ask which newer server versions their current release supports. That answer sets the date for the whole move.
Move the easy roles early. The file share can go to SharePoint over a weekend, which shrinks what's left on the old box.
Put each role on the roadmap as its own row. Give it a forcing date, a cost to act now, a cost of waiting a year, a quarter and an owner.
Review it every quarter. A 30-minute review is enough to catch a vendor that's slipping.
What the rows look like
I keep this in a plain spreadsheet. A CSV header and one row per role is enough, with the prices filled in from real quotes.
item,forcing_date,options,cost_to_act_now,cost_of_waiting_a_year,quarter,owner
Server 2016 file share,2027-01-12,Move to SharePoint,[quote],[estimate],Q1 2027,[name]
Server 2016 sign-ins (domain controller),2027-01-12,Plan the identity move,[quote],[estimate],Q1 2027,[name]
Server 2016 line-of-business app,2027-01-12,Vendor upgrade path,[vendor quote],[estimate],Q1 2027,[name]
I leave the prices in brackets on purpose, because nobody should guess them. The file share's cost of waiting is mostly risk, since the box stops getting security fixes. The app's cost of waiting is time, and you don't get it back once the vendor is slow to answer.
Gotchas
Clients on Windows 10. If the PCs that connect to this server are still on Windows 10, give them their own rows. Businesses pay $61 per device for Year 1 of Extended Security Updates and the price doubles each year for up to 3 years. It's cumulative, so a PC that joins now pays $183. If those users can work from a virtual desktop, Windows 10 in Windows 365 or Azure Virtual Desktop gets the updates at no extra cost.
The tax calendar. In Texas, a replacement server is business personal property, valued as of January 1. If the new hardware is going to land near that date, it's worth asking a CPA which side of January 1 it should fall on.
Windows Server 2019 is not urgent. It's supported until January 2029. Leave it as one dated line and don't spend time on it yet.
Takeaway
Don't price the server. Price the roles. The role with the longest lead time, usually the app, decides when you have to start, and with the January 12 deadline that start date is already close.
As I write this in the third week of November, January 12 is 55 days away. If the app vendor takes a few weeks to answer and the move itself takes a few weeks after that, the realistic start date is this month, not after the holidays.
The longer version of this, with the rest of a 2027 roadmap for a small office, is on our site: building an IT roadmap for a Fort Worth small business.
Top comments (0)