Serving the continental U.S. | Business · Government · Education · Non-Profit
IT Management

Windows Server 2016 support ends in January. Your budget year probably does not.

Most of the advice being published assumes you can buy something in January. If you run on a July fiscal year or inside a grant, the honest plan looks different.

Windows Server 2016 reaches end of support on 12 January 2027. After that Microsoft stops issuing security updates for it. The server keeps running, which is what makes this easy to defer, and it stops receiving patches for vulnerabilities discovered from that day onwards.

There is no shortage of articles telling you to upgrade before January. Most of them are written for organizations that can decide to spend money in the same quarter they decide to spend it. If you are a school district, a county agency or a nonprofit, that is not how any of this works, and advice that ignores the point is not advice.

The date does not line up with your budget

Take a district on a July to June fiscal year. FY27 runs from July 2026 to June 2027, and it was built in the spring. If a server refresh is not already in it, the January deadline lands in the middle of a year whose money is committed. The next genuine opportunity is FY28, requested in spring 2027 and available from July 2027, which is six months after support ends.

Now take a county or municipal body on a calendar year. The CY27 budget is being assembled right now, this autumn. That is a real window and it closes shortly. This is the group for whom the standard advice applies, and the action is to get the line item in during the process already underway.

Nonprofits are usually a third case again, where the technology spend sits inside a grant awarded for a defined purpose and cannot simply be redirected at a server.

So the first question is not which version of Windows Server to move to. It is which of those three you are, because it decides whether you are planning a purchase or planning a stopgap.

If the money is not there, plan the bridge properly

Microsoft sells Extended Security Updates for Server 2016, purchasable for up to three years past end of support. Used deliberately, that is a legitimate answer: it buys you to the next budget cycle with security patches still arriving.

Be clear about what ESU is. Security updates only: no fixes, no features, and the price rises each year you stay on it. It is a stopgap, so the upgrade still has to be scoped and costed now, with a real number in the next budget request instead of a placeholder.

A documented decision to run ESU for one year while FY28 funds the replacement is a defensible position. Arriving at January with no plan is not, and the difference between them is a paragraph written in September.

Start with an inventory, because it is free

Before any of that, find out what you have. In most buildings the Server 2016 estate is smaller than people fear and stranger than they expect. It is rarely the main file server, which somebody has already worried about. It is the machine running one application nobody owns, the box that came with a phone system or a camera recorder, or a virtual server built for a project that ended in 2019 and never got switched off.

For each one, three questions settle it. What does it do, does anything still depend on it, and can it be retired instead of replaced. A meaningful number of these can simply be turned off, which is the cheapest upgrade available.

The compliance angle you may not have priced in

Unsupported operating systems show up in two places that cost money.

Cyber insurance underwriting increasingly asks whether you run unsupported software, and an honest yes affects your terms. Compliance and audit frameworks treat unsupported systems as a finding.

So the cost of doing nothing is not zero, and it is not only the risk of a breach. It can turn up in a renewal quote or an audit report before it ever turns up as an incident.

What to do this month

Inventory your Server 2016 machines and write down what each one does. Decide which can be retired. For the rest, get a real number for replacing them. Then look at your own fiscal calendar and work out honestly whether that number can be spent before January, or whether you are bridging to the next cycle.

If it would help to have someone go through the inventory with you and put a number on it, we will do that. Having the figure in hand before your budget process is most of the value, and you do not need to buy the upgrade from us to want it.

← All news

Let's talk about what's not working.

A 20-minute call with a consultant. No sales script.