Support and Evolution

Windows Server 2016 runs out of patches in January

In this article

Nori.mx8 min read

Plant serverYour applicationSQL Server 2016Windows Server 2016Last patchJanuary 12, 20271Upgrade2022 or 2025, app on top2Extended updatesThrough 2030, via Azure Arc3IsolateOff the general network

Two things happened quietly on October 13. The last update of the paid extension for Windows Server 2012 shipped, and Windows 10 LTSB 2016 stopped receiving updates. That edition is very common on the PCs that come attached to a test machine or an HMI.

The next date is bigger. Windows Server 2016 reaches end of support on January 12, 2027, and its last security patch ships that day. SQL Server 2016, which often lives on the same box, already ran out of support in July.

If your plant’s server room has a server installed between 2017 and 2019, there is a good chance it runs 2016. And what runs on top of it is almost never just Windows.

What happens on January 13, and what does not

Nothing shuts off. The server boots, the application opens and the report prints the same as before. That is exactly why the date slips by.

What changes is that when someone finds a new security flaw in Windows Server 2016, Microsoft will no longer fix it for you, and those flaws get published every month. From January on, each one that appears stays open for good unless you pay for the extension.

The practical risk at a plant is not someone stealing a drawing. It is ransomware: software that encrypts your servers and demands payment. It almost always gets in through an old machine on the network, and plant networks tend to be flat: the office PC, the label server and the line station can all see each other. One unpatched door is enough for the problem to reach the place where shipping labels get printed.

Why someone outside IT is going to ask about it

Even if you have never been attacked, an old server has a second way of costing you: the audit.

If your plant is CTPAT certified, the minimum security criteria that U.S. Customs and Border Protection publishes for foreign manufacturers spell it out. Criterion 4.2 requires security software to be current and to receive regular security updates. Criterion 4.3 requires testing your IT infrastructure for vulnerabilities and fixing what turns up “as soon as feasible”. The criteria do not name Windows, but on an unsupported server the flaw the scan finds cannot be fixed, because the patch no longer exists.

The same goes for the security questionnaires many customers send their suppliers: they usually ask whether your equipment runs supported versions. From January, if you have 2016, the honest answer is no.

The three ways out

There are three, and most plants will need more than one.

Upgrade. A new server, or the same one with Windows Server 2022 or 2025, and the application installed on top. It is the permanent answer and, when the application allows it, the cheapest one over the medium term.

Buy the extension. Microsoft sells Extended Security Updates (ESUs) for Windows Server 2016 for up to three years, through 2030. Three conditions are worth knowing before you budget for them. They only include critical and important security patches, no other kind of fix. For Windows Server 2016 they are bought mainly through Azure Arc, which means the server has to connect to Microsoft’s cloud. And you need Software Assurance on your volume licensing, unless your servers are licensed by subscription or through SPLA. Billing starts on January 13. It is a bridge, not a destination: it buys time to do the first option, it does not replace it.

Isolate. Some equipment cannot be upgraded: the PC on a machine whose maker only certifies that version of Windows, or a test rig that costs more than the whole server. For those, the answer is to take them off the general network, leave open only what they need and write it down. That does not make them safe. It makes them containable, and it gives the auditor a written answer instead of a silence.

What actually holds the migration back

Installing Windows Server on a new machine takes an afternoon. What nobody knows is whether the application will start on the other side.

The reasons a plant application refuses to move are almost always the same:

  • It was written for an old version of something. Visual Basic 6, an old .NET Framework, or a 32-bit component nobody has rebuilt since.
  • It depends on a driver. The label printer, the scanner, the scale or the PLC has a driver its maker stopped updating.
  • The server name is written inside it. Or its IP address, or the path to a shared folder. It works as long as nothing moves.
  • The license is tied to the hardware. Some programs activate against the network card or the disk, and on another machine they will not open.
  • The database is just as old. A SQL Server 2008 or 2012 that nobody dares upgrade, because the reports come from queries nobody has read in years.

None of those has anything to do with Windows. They have to do with who wrote the application, and if that person is gone, it is the same problem we covered in you inherited software nobody documented. The test is the same too: try to stand it up on a clean machine, on the new Windows version, against a copy of the database. Whatever breaks that afternoon is your work list. If it comes up clean, the migration is paperwork.

The inventory you can do in an afternoon

Before quoting servers or licenses, one sheet with these columns and a row per machine:

  1. Machine name, exact Windows version and exact SQL Server version. Not the one somebody remembers, the one the machine reports. That alone is half the conversation.
  2. Which applications run there, and who owns each one inside the plant. The owner is not IT. It is whoever yells when it goes down.
  3. What stops if that machine is off for an hour. Labels, shipping, the IMMEX report, payroll. That column sorts the list by itself.
  4. Whether the installer and the source code exist, or only what is installed. If only the installation exists, that row is not a migration, it is a rebuild, and it goes first.
  5. Whether there is a backup and when it was last restored. A backup nobody has ever restored is not a backup.

Do not forget the PCs on the floor. The ones on Windows 10 LTSB 2016 already ran out of patches in October, and they tend to be the ones nobody counts because they are “part of the machine”. The same rule we use before connecting the first machine applies: what is not on the list cannot be protected.

What to do with the rest of the year

There are about eleven weeks left. That is enough to get organised, not to migrate everything, and it is better to accept that now:

  • This week, the sheet above. Without it, everything else is guessing.
  • Before December, decide which server takes which way out. Upgrade the ones that pass the clean-machine test, extend the ones that will not make it in time, and isolate the ones with no fix.
  • If any of them will need the extension, start the licensing paperwork now. It requires Software Assurance and connecting the server to Azure Arc, and neither gets done during Christmas week.
  • For every application that will not move, a decision with a date: fix it so it runs on the new version, replace it, or retire it. All three are valid. What does not work is buying three years of extension and reaching 2030 with the same program and the same question.

If this lands on top of the fronts you already had open for January, like electronic workday records or the year-end inventory count, deciding what goes first is worth more than attacking them all at once.

Where we come in

We do the part that gets stuck: taking the application that only runs on the old box, finding out why, and leaving it running on a supported version, with its code in a repository and its installation written down. When it is not worth rescuing, we rebuild it in stages, without switching off the one that works until the new one does the same job.

If you have a 2016 server and do not know what is on it, we will assess the application at no cost and tell you which of the three ways out fits. And if you would rather start on your own, Chira asks you the questions above in five minutes and leaves you a document with the order.

References

The dates and conditions in this article come from Microsoft’s official pages and from U.S. Customs and Border Protection. Extension terms change from time to time, so confirm them with your licensing reseller before you budget.

Related service

Support and Evolution

Launching the software is the beginning. Keeping it alive is the work.

See the service

Articles on this service

Copy 1Office serverCopy 2External driveCopy 3OffsiteRestore testFile: invoices-2026.xlsxCopy used: 3, offsiteOn another machineIt opened in full

Support and Evolution

A backup is worthless until you restore it

Almost every company backs up and almost none tests a restore. What to copy, where to keep it, how to test it and who has to own it.

7 min read

NOVEMBERSunday12:00 → 1:00Juárez and El PasoScans1:40Pallet A1st pass1:10Pallet B2nd passDowntime−45 min1:50 → 1:05actual: 15 minBy time: B before ANight shift23:00 → 7:00Clock says8 hWorked9 h

Support and Evolution

On Sunday, 1 a.m. happens twice

This Sunday Juárez sets its clocks back an hour. What breaks that night in time clocks, reports and servers, and what to check before it happens.

7 min read

final_v3system.execonfig.inidata.mdb12 years on the floorThe two-hour testIs the source code there?Is it in version control?Does it build today?Does it run on a copy of the DB?If #1 fails, it is an installation

Support and Evolution

You inherited software nobody documented

It works, nobody knows how, and the person who wrote it is gone. How to tell whether it can be rescued or has to be replaced, and what to do in week one.

7 min read