Windows Server 2016 End of Support: A Dental Office Plan for Jan 2027

The date usually arrives sideways. A cyber-insurance renewal asks which operating systems your servers run. The Dentrix requirements sheet carries a footnote about Windows Server 2016. Or a quote for a new server lands in a month when nobody budgeted for one, and someone has to find out whether the deadline is real.

This guide is for the office that has to turn that date into a decision. It gives Microsoft's dates in plain US calendar terms, a way to confirm what your own server runs, what Henry Schein One, Patterson and Open Dental publish about Windows Server versions, the facts on Extended Security Updates that most summaries skip, and the sequence an IT provider should follow so the move does not cost you a clinic day. Every Microsoft and vendor page quoted was read on 6 November 2026.

What ends for Windows Server 2016 on 12 January 2027?

Microsoft lists Windows Server 2016's extended support end date as 12 January 2027. Mainstream support ended in January 2022, so the last five years brought security fixes only. From 13 January 2027 there are no further security updates, no non-security fixes and no Microsoft support for the product unless the server is enrolled in Extended Security Updates.

Two Microsoft pages carry the date. The lifecycle page shows "Support dates are shown in the Pacific Time Zone" with an extended end stamp of 1/13/2027 at 6:59:59, which marks the close of the last day, 12 January 2027. The Windows Server release information page prints the same thing without the time zone puzzle: extended support end date 2027-01-12. If a summary you read says 13 January, it copied the time stamp rather than the date.

The server does not switch off. Practice software keeps opening, images keep loading, and nothing on the screen changes. What changes is that every Windows flaw published after that date stays open on that machine, and the machine in question holds the practice database, the imaging archive and the logins for every workstation.

Dates are Microsoft's lifecycle and release-information pages read on 6 November 2026, written as the last US calendar day of support.

One more date sits on some dental servers. If any application on the box uses Microsoft SQL Server, check that version too: SQL Server 2016's extended support ended on 14 July 2026, and Microsoft's lifecycle page lists paid Extended Security Update years for it running to July 2029. The database engine and the operating system can fall out of support in different months, and fixing one does not fix the other.

A last point on what "unsupported" means for your vendors. Patterson's current Eaglesoft requirements document already says of Windows 7, 8 and Server 2012 R2 that they "have reached end-of-life" and that "Patterson no longer recommends its continued use", with support reduced to "best effort". Expect Windows Server 2016 to join that list after January; Henry Schein One prints the 1/12/2027 date on the Dentrix requirements sheet today.

Which option fits your practice: upgrade, replace, cloud or Extended Security Updates?

Four paths exist. The right one depends on three facts about your server: its age and processor, which edition of Windows Server 2016 it runs, and what else sits on it. For most single offices the realistic choice is a new server or a hosted practice platform; in-place upgrades suit recent hardware; Extended Security Updates fit very few practices.

If you want the economics of server versus cloud for a dental office laid out in full, our guide to dental server replacement vs cloud migration does that, and our note on whether you still need a server with cloud dental software covers the imaging question. This page stays on the deadline itself.

A default path by practice type

• • Single office, Dentrix or Eaglesoft on a 2016-era server: replace the server with Windows Server 2025 Standard on hardware that clears your vendor's current minimum, and move the database with the vendor's server-move procedure.
• • Single office on a server bought in 2022 or later that happens to run 2016: price an in-place upgrade against a replacement; the hardware may be fine.
• • Office already unhappy with its practice software: decide the software question first, because a hosted platform changes what the new server needs to be.
• • Two or more locations: standardise the server build across sites in the same project, and treat any acquired office's server as part of the inventory.
• • A server running one orphaned application (an old imaging bridge, a lab system): isolate it, plan its retirement, and ask your licensing reseller whether Extended Security Updates are even available to you before counting on them.

How do you check whether your server is really on Windows Server 2016?

Sign in to the server itself, not a workstation, and open Settings, then System, then About; or press the Windows key, type winver and press Enter. The window shows the edition (Windows Server 2016 Standard, Essentials or Datacenter) and the build number, which for Server 2016 starts with 14393. Then check for a second server and for SQL Server.

Five minutes of looking answers most of the questions an IT quote raises. Work through these in order and write down what you find.

1. 1. Find every box that acts as a server. The practice database usually lives on one machine, but imaging software often has its own server, and a CBCT or scanner cart can hold an image archive that other operatories read from. A NAS (network storage box) used for shared files or backups counts too, though it runs its own software rather than Windows Server.
2. 1. Read the edition, not just the version. Windows Server 2016 Essentials was Microsoft's small-business edition of the product, listed on its lifecycle page beside Standard and Datacenter. Two things follow. Microsoft's Extended Security Updates for Windows Server 2016 "support Windows Server 2016 Standard and Datacenter editions", so an Essentials server has no ESU route. And Henry Schein One's requirements say "Server Essentials (including essentials role) and Small Business are not supported due to port conflicts with backups", so a Dentrix office on Essentials has two reasons to move, not one.
3. 1. Look for SQL Server. Open Control Panel, then Programs and Features, and look for any "Microsoft SQL Server" entry; the year in its name is the version. Some imaging, orthodontic and multi-location practice systems rely on it. SQL Server 2016's extended support ran out in July 2026.
4. 1. Note what else runs there. Shared drives, the print server, the backup agent, remote-access software, Active Directory (the system that holds staff logins), the clearinghouse or eServices background service. Each one has to be rebuilt or moved, and each is a line on the migration plan.
5. 1. Record the hardware. Processor model, memory, drive type and free space, purchase date if anyone knows it. This decides upgrade versus replace in the next two sections.

If the person doing this is not comfortable signing in to the server, stop at step one and hand the list to your IT provider; the point is that the list exists before anyone quotes anything.

What do Dentrix, Eaglesoft and Open Dental say about Windows Server versions?

All three list Windows Server 2016 through 2025 as supported today. The differences are in the detail: Dentrix excludes Essentials and Server Core, Eaglesoft needs version 24.20.03 or higher for Windows Server 2025 and a dedicated, wired server, and Open Dental will also run its database on Linux. Read the current document, not a summary of it.

Three lines in those documents change what you buy. First, Henry Schein One's footnote reads: "Windows Server 2016 support ended in 2022; extended support continues until 1/12/2027." The vendor is telling you the date on its own sheet. Second, Patterson's document opens by saying it "structures supported versions of Eaglesoft around Microsoft's support of Operating Systems", so a Windows version falling out of Microsoft support is the trigger for Eaglesoft's own list to change. Third, Patterson's Server 2025 line, "Support for 32-bit applications must be enabled in Server Manager", is the kind of detail that turns a clean install into a morning of "Eaglesoft won't start" if nobody read it.

Imaging vendors publish their own server requirements, and the image database often needs a particular SQL Server or storage layout. Ask each one, in writing, which Windows Server versions its current release supports before the new server is ordered; our guide to dental software system requirements collects the practice-software side in one place.

Can you upgrade Windows Server 2016 in place, or does the hardware have to go?

Microsoft supports an in-place upgrade from Windows Server 2016 to 2019, 2022 or 2025, and says each upgrade needs its own licence and a full backup first. Whether you should depends on the hardware: a server that fails Dentrix's or Eaglesoft's current processor, memory or storage minimum stays below them after the upgrade, and a 2016-era box usually does.

Microsoft's upgrade overview puts it plainly: "Starting with Windows Server 2025, nonclustered systems can upgrade up to four versions at a time. You can upgrade directly to Windows Server 2025 from Windows Server 2012 R2 and later." Its table of supported paths from installation media reads, for a Windows Server 2016 source: to 2019 yes, to 2022 yes, to 2025 yes. Two sentences on the same page matter for a practice: "Unlike Windows client, each Windows Server upgrade requires a separate license", and "Always back up your system and important files before performing an in-place upgrade".

The hardware test

Run the test and the decision usually makes itself. A server bought with Windows Server 2016 in its first years on sale is now seven to ten years old, and a processor from that period usually sits below Dentrix's 9th-generation line; the honest quote is a replacement. A server that shipped with 2016 because the vendor's software was not yet validated for 2019 or 2022 may be young enough to upgrade in place. Either way, pair the server decision with the operatory PCs: our guide to which computers to buy for a dental office covers the workstation side so the two purchases are planned together.

Two habits from the same documents belong in the plan whichever way you go. Patterson recommends "weekly reboots of your physical data server to allow Windows updates to install", and Microsoft notes that an in-place upgrade can also arrive "as a feature update through Windows Update", so the new server's update policy should be written down, not left to chance. Our note on dental server shutdown mistakes to avoid covers the restart side.

Is Extended Security Updates a realistic bridge for a dental office?

Microsoft offers Extended Security Updates for Windows Server 2016 through Azure Arc for up to three years after 12 January 2027. For a typical dental office the answer is still usually no: Microsoft limits it to Standard and Datacenter editions, ties purchase to Software Assurance or a Server Subscription, and bills monthly from 13 January 2027.

Microsoft's Azure Arc page is the source, and it is specific: "Extended Security Updates for Windows Server 2016 provide Critical and Important security updates for up to three years, through 2030. ESUs don't include new features, customer-requested nonsecurity hotfixes, or design change requests." Microsoft says the program can be configured in the Azure portal starting 3 August 2026, and "Billing for Windows Server 2016 ESUs enabled by Azure Arc begins January 13, 2027."

The conditions are what most summaries leave out:

• • Editions. "Windows Server 2016 Extended Security Updates support Windows Server 2016 Standard and Datacenter editions." An Essentials server is not eligible.
• • Licensing. "To purchase ESUs, you must have Software Assurance" through an Enterprise Agreement, Enterprise Agreement Subscription, Enrollment for Education Solutions, Server and Cloud Enrollment or Open Value program; alternatively a server "licensed through SPLA or with a Server Subscription" does not need Software Assurance. A practice that bought its server licence with the hardware from a dental reseller should ask that reseller, in writing, which of these it holds before counting on ESU at all.
• • Mechanics. The server runs Microsoft's Azure Connected Machine agent ("For Windows Server 2016 ESUs, use agent version 1.62 or higher"), is connected to an Azure subscription, and when the licence is created you "specify the SKU (Standard or Datacenter) and the number of cores". Someone has to run that subscription and its bill every month.
• • Purpose. Microsoft's own overview calls the program "a last resort option for customers who need to run certain legacy Microsoft products past the end of support."

Where it does fit: a server that runs one application no vendor will move before January, where the move is already scheduled for spring and the practice wants patches in the gap. Even then, the server should be kept off the internet-facing side of the network, remote access to it restricted, and the plan to retire it dated. A machine with no patches at all is a different matter: CISA lists "Use of unsupported (or end-of-life) software" among its published Bad Practices and adds that the practice "is especially egregious in technologies accessible from the Internet". If a server on an expired operating system is also the box your remote-access tool answers on, that sentence is about you.

For the HIPAA question your insurer or consultant will raise, the Security Rule's text at 45 CFR 164.308(a)(1)(ii)(A) requires covered entities to "conduct an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity, and availability of electronic protected health information". Whether an operating system that no longer receives security fixes appears in your practice's assessment, and how it is documented, is a question for you and your compliance advisor; this page only shows where the text lives.

How does the Windows 10 deadline for your workstations fit in?

Treat it as one project with two dates. Windows 10 reached end of support on 14 October 2025, new Dentrix installs on Windows 10 lost vendor support after 30 June 2026, and the server date follows in January. The server move is the moment to replace the operatory PCs that cannot run Windows 11, since every workstation is re-pointed anyway.

The two programs are separate: Windows 10 Extended Security Updates are bought per PC and work differently from the Azure Arc program for servers. Our guide to whether Windows 10 is still OK in a dental office sorts the PCs into keep, cover, isolate or replace and gives Microsoft's ESU terms for them, and our piece on budgeting the Windows 10 transition covers the spreadsheet. Here, the practical rule is simple: do not order a server and then discover in the same week that six operatory PCs also need replacing and the imaging vendor has a Windows 11 driver caveat. Inventory both, order both, and schedule one cut-over.

The IT side: the nine steps of a dental server migration

A dental server move is a sequence, not a weekend. The database, the document store, the imaging archive, the staff logins and the backup chain all have to arrive on the new machine and be tested from a real operatory before the old one is switched off. Nine steps, in this order, is what a competent provider will quote.

1. 1. Inventory and decision. The list from the check-your-server section, plus the hardware test, plus a written choice: in-place upgrade, replacement, hosted platform or hybrid.
2. 1. Vendor tickets before hardware. Open a server-move case with your practice-software vendor and each imaging vendor, ask which Windows Server version and edition they support today, whether the move is a billable service, and what lead time they need. Their calendars set yours.
3. 1. Licensing. Windows Server 2025 Standard for the server, the client access licences your reseller specifies for your workstation count, and any SQL Server edition an imaging product requires. Microsoft's rule that each Windows Server upgrade "requires a separate license" applies to in-place upgrades too.
4. 1. Build and stage. The new server is built, patched, joined to the domain (or set up as the new domain controller if the old one held that role), and burned in before it reaches the office. Redundant storage and a battery backup are standard; so is a monitoring agent that reports when a disk or a service fails.
5. 1. Move the data in the vendor's order. The practice database with the vendor's tool, the document store (Dentrix's Document Center; Open Dental's A to Z folder), the imaging database and image files with the imaging vendor's procedure, letter templates and scanned forms, then shared drives. Each store is checked on the new server before the next one moves.
6. 1. Re-point and re-register. Every workstation's practice software and imaging software is pointed at the new server; drive mappings, printers, the clearinghouse or eServices service and any remote-access tool are re-registered. Sensor and camera bridges are tested chair by chair, because a bridge that worked on the old path is the first thing to fail on the new one.
7. 1. Backups re-seeded and restored once. The backup job is rebuilt for the new server and a test restore of the database and a day's images is performed before go-live, not after. One owner's line from a dentists' forum explains why: "our cloud backup (our only backup) hadn't been updating for a few weeks". Our guide to dental data backup sets the standard to hold your provider to.
8. 1. Cut-over with a fallback. The move runs after the last patient of the week, the old server stays powered but disconnected from the network for an agreed period, and a named person signs off that scheduling, charting, imaging, claims and reports work from two operatories and the front desk before Monday.
9. 1. Retire the old server. Drives hold patient data; they are wiped or destroyed and the disposal is recorded, licences are released, and the old box leaves the inventory, the monitoring and the backup plan.

Dentrix offices will recognise most of this from our Dentrix server migration checklist; the sequence above is the vendor-neutral version. If a move goes wrong, the first four hours are their own subject, covered in what to do when the dental server is down.

A calendar from today to 12 January 2027

In early November that leaves nine or ten weeks, which is enough if the first week happens this week. The weeks that disappear are always the same ones: hardware lead time, the vendor's move calendar in December, and the holiday fortnight when nobody should be cutting over a practice database.

What should you budget for before the January deadline?

Budget six lines, not one: server hardware; the Windows Server licence and client access licences; any SQL Server licence an imaging product needs; your practice-software and imaging vendors' server-move fees; your IT provider's labour for the sequence above; and the workstations folded into the same cut-over. Ask for each line separately so the quote can be compared and explained.

Three questions sharpen the numbers. Does the quote separate hardware from support, so that a cheaper box or a longer warranty can be discussed without reopening everything else? Does it include the vendor fees, which practices often discover afterwards? And does it state what happens to the old server's drives? If a purchase before 31 December is on the table for tax reasons, ask your accountant how Section 179 applies; this page makes no tax claim.

Groups with several locations should also read the hidden cost line: an inherited server on an expired operating system at one site is a shared risk for every site that reads from it, and standardising the server build across locations is cheaper done once than repeated per office.

What to ask your IT provider about Windows Server 2016

These nine questions turn a Windows Server 2016 quote into something you can compare. Ask them in writing, in three rounds: what you have today, what the plan is, and what happens after the move. A provider who answers all nine clearly has already done the inventory work this page describes.

How Legend Networking can help

Legend Networking is a Dallas-based dental IT company with 22+ years in dental IT. It has served over 3,500 practices since 2004. Legend supports the IT environment for the practice software Dentrix, Eaglesoft, Open Dental and Archy, and for the imaging systems DEXIS, Vatech, Carestream, Planmeca/Romexis and Dolphin Imaging. Hardware procurement, major cabling projects and software licensing are quoted separately, so the server line and the support line stay visible. Onsite dispatch is by appointment across served dental markets; support is remote-first nationwide, with 24/7 monitoring. For the day-to-day side, see our dental servers and workstations service, and for an office that wants one provider to own the whole stack, our managed IT services for dental practices.

The author, Ian Lynch, has 22 years in dental IT and oversees the NOC, onsite dispatch and client technology roadmaps. Legend holds a 4.8 rating from 173 Google reviews. For an example of the ground this covers, see a technology onboarding that reviewed a practice's network and server, security, backups, software and user access. To see where Legend works near you, start from dental IT in your city.