Dental Software System Requirements Guide: Windows, Servers, Workstations, Networks, Imaging and Safe Upgrades

Windows has started nagging about an update on the front desk PC. The imaging company says its next release needs a newer operating system. Before anyone clicks "install", you want to know what your dental software actually needs, and how to change it without losing a clinical day.

Here is the direct answer. Dental software system requirements are the operating system, hardware, database and network conditions a vendor supports for one exact version of its product. Read the current requirements for every product you run (practice management, imaging, bridges, security agents), then add headroom for your workload, and upgrade only after a pilot passes your own acceptance tests.

This guide shows how to read those requirements, which Windows dates matter in 2026 and 2027, how to build a bridge inventory, and how to run an upgrade in a fixed order: back up, update the server, pilot one workstation, test the clinical day, then roll out.

What are dental software system requirements, and where do you find the current ones?

Dental software system requirements are a vendor's published list of the operating systems, processors, memory, storage, database engines and network conditions it supports for a specific release. Find them in the vendor's own support portal or manual, note the date you read them, and recheck them before every upgrade, purchase or Windows change.

Three habits make the list useful instead of misleading.

Read the version, not the brand. Requirements belong to a release. A practice running an older version of its practice management system (PMS) can be unsupported on an operating system that the current release handles well, and the other way round. Write the installed version and the target version at the top of your notes before you read a single spec line.

Read every product, not only the PMS. The PMS is one line in a stack. Imaging software, sensor drivers, intraoral camera software, scanner utilities, e-claims and patient-communication connectors, antivirus and backup agents all publish their own supported lists. The strictest one sets your limit.

Write down the date you read it. Vendors revise these pages without much notice. A requirement copied into a binder in 2023 is a historical document. When you cite a requirement in a purchase decision, keep the link and the read date next to it, the same way this page lists its sources.

Where the per-platform requirement pages live

This guide covers the method that applies to every product. For a specific platform's environment, see Legend's platform pages: Dentrix IT support and Dentrix server planning, Open Dental IT support and server planning and Eaglesoft IT support and hardware planning. Each vendor's own support portal remains the authority for the numbers.

Minimum supported is not the same as production-ready

Vendor minimum requirements answer "can this software start and run?" A practice has to answer a harder question: "can this workflow run reliably through a full clinical day, with imaging open in every operatory, the backup running, security agents scanning and the schedule full?" The gap between the two is where most slow-computer complaints begin.

A minimum is tested in a clean lab: one application, no imaging, no endpoint protection, a short database. Your front desk runs the PMS, a browser with insurance portals, a document scanner and a label printer at the same time. Your operatory computers run the PMS, the imaging bridge, sensor drivers and a second display. Plan for that load.

DENTAL SOFTWARE READINESS MATRIX

Use this as a worksheet before any upgrade. Mark each row ready, review or blocked, and do not schedule the change while any row is blocked.

The old version of this matrix showed every row as "verified". A matrix is only useful when it can say "blocked".

Verify the exact software version before reading requirements

Requirements change by version and release. Record the installed and target versions for every product before you plan any Windows, server or workstation change, then check the current official vendor documentation for that pair. An inventory takes an afternoon; skipping it is how a routine update turns into a lost morning.

VERSION INVENTORY CHECKLIST

• • PMS name and exact version (for example the version number on the program's Help or About screen)
• • Imaging software and exact version, on every computer that captures or views images
• • Server and database version where relevant (for example MySQL or MariaDB for Open Dental, SQL Server for some other platforms)
• • Workstation operating system edition and version (Windows 11 Pro 24H2, 25H2 and so on)
• • Device drivers and acquisition software for each sensor, camera and scanner model
• • Third-party bridge and integration versions (see the bridge inventory below)
• • Security and backup agents that must coexist with the PMS and imaging database
• • Printer and scanner drivers used for claims, labels, consent forms and prescriptions

Do not design a 2026 infrastructure plan from an old PDF saved in a vendor folder. Link to the vendor's current documentation, record when you read it, and avoid copying transient spec numbers into internal notes that will outlive them.

What is a bridge inventory, and why do you need one before an upgrade?

A bridge inventory is a list of every link between your PMS and another program: imaging, sensors, cameras, e-claims, patient communication, payments and reporting. For each bridge you record its version, who supports it and when it was last tested. Upgrades break bridges more often than they break the PMS itself.

A bridge is a small piece of configuration or software that lets one program open another with the right patient. When you click the imaging button in the chart and the correct patient's X-rays appear, a bridge did that. Bridges have their own version numbers and their own supported lists, and they are easy to forget because nobody touches them until they fail.

Bridge inventory table

Copy this table and fill one row per bridge, per computer type where it differs.

Three rules keep it honest. A row with "unknown" in the supported column is a blocker until someone confirms it in writing. A "tested on" cell must name a real patient-free test, not "looked fine". And the inventory belongs to the practice, not to whoever installed the software, so it survives a change of IT provider. For the symptoms that follow a broken bridge, see dental imaging integration troubleshooting.

Which Windows and Windows Server dates should a dental practice plan around in 2026 and 2027?

Plan around four Microsoft dates. Windows 10 support ended on 14 October 2025. Windows 11 Home and Pro version 24H2 reached its listed end date on 14 October 2026. Version 25H2 is listed to 13 October 2027. Windows Server 2016 extended support ends in January 2027. Check each against your vendors' lists.

Source: Microsoft Lifecycle pages for each product, read 22 October 2026 (listed in this page's sources). Dates are Microsoft's; vendor support for each version is a separate question.

Two practical points follow. First, a Windows feature update is a new operating system version as far as your dental vendors are concerned, so it goes through the same pilot as a PMS upgrade. Second, the Windows Server 2016 date often decides whether you replace the server like-for-like or move part of the workload to the cloud; dental server replacement vs cloud migration walks through that choice. If you still have Windows 10 machines to retire, budgeting the move off Windows 10 covers the cost side.

Microsoft's minimum hardware for Windows 11 includes a compatible 64-bit processor with two or more cores, 4 GB of memory, 64 GB of storage, UEFI with Secure Boot and TPM 2.0. Those are Windows minimums, not dental minimums. Older operatory computers frequently fail the TPM or processor check, which is why a Windows deadline often becomes a hardware project.

Server readiness: size for the practice, not only the PMS

For server-based systems, treat the vendor's requirement as the floor, then size for the real workload: number of workstations, database size, imaging storage, storage speed, backup window, security tooling and how long you expect the server to last. A server that meets today's minimum can become the bottleneck within a year of imaging growth.

The connection limit that catches growing practices

Small offices sometimes run the PMS database or image share on a desktop computer instead of a server. Open Dental's requirements page lists a limit of 20 simultaneous connections for a Windows 10 or Windows 11 file share, in every edition, and notes that Home editions are sometimes unacceptable because of connection and networking limits. Carestream's CS Imaging version 8 guide lists Windows 10 and 11 64-bit with a maximum of 20 stations and recommends the Professional edition. When an office adds operatories, front-desk seats and remote users, that ceiling arrives sooner than expected and shows up as intermittent disconnects.

Open Dental also recommends a dedicated server to protect data, and keeping the server name under 15 characters because of a Windows limitation. Those are the kind of small, specific vendor notes worth reading in full before you buy hardware.

Workstations should be specified by role

An operatory imaging workstation and a front-desk scheduling PC may run the same PMS but need different processors, graphics, storage, ports and displays. Standardize by role, buy each role to the strictest requirement of the software it runs, and stop buying one lowest-common-denominator PC for the whole office.

A role standard also makes upgrades faster. When every operatory PC is the same model with the same driver set, one successful pilot tells you a lot about the rest. When every PC is different, every PC is its own pilot.

Windows upgrades are dental-software projects, not generic PC updates

Before a fleet-wide Windows upgrade, confirm that the PMS version, imaging applications, sensor drivers, bridge software, printers and security tools all support the target Windows version. Then pilot one representative workstation per role and roll out in waves. A Windows feature update changes the platform every dental program sits on.

MIGRATION WALKTHROUGH

How do you upgrade dental software safely?

Upgrade dental software in a fixed order. Before: take a backup and a restore point, record versions and bridges, and read each vendor's compatibility notes. During: update the server first, then pilot one workstation. After: test charting, imaging capture on every sensor, claims, e-services, printers and reports before the whole office uses it.

This is the version upgrade acceptance checklist. Print it, assign a name to each line and keep the completed copy with the date.

Before the upgrade

During the upgrade

After the upgrade: acceptance tests

Run each test on the pilot workstation with a test patient, then on one workstation of every other role before the first patient arrives.

If any line fails, the rollout stops at the pilot. Fix it, record the fix, retest, and only then move to the next wave. Monitor the first full clinical day after the change, with someone ready to act on problems.

How does an Open Dental update work, and what should you check after it?

In Open Dental, the update is installed on the server or a designated update computer, and the other workstations update themselves the next time the program is opened. Open Dental must be closed on every workstation during the update, which the vendor says generally takes 15 to 30 minutes and can take up to an hour.

Open Dental's own update instructions add several details worth following:

• • Set an Update Server name. Open Dental lets you name the one computer allowed to run updates. The vendor notes this prevents accidental updates and matters most with eServices, HL7 or multiple locations.
• • Run it from the server when possible to avoid network permission problems.
• • Expect the automatic backup format. Some updates create an automatic database backup as a precaution. Open Dental notes the format of those backups and the extra step InnoDB offices face if they restore one, so read that section before you rely on it.
• • Multiple databases. Choose one main database to run updates, use the shutdown tool on the others, then open each of the others afterwards; users stay locked out until you do.
• • The countdown does not start the update. The update notification countdown warns workstations, but someone still has to start the update manually.
• • Older versions take longer. The vendor allows up to an hour for slow servers or versions more than two years old.

After the update, run the acceptance tests above. For Open Dental offices, pay particular attention to imaging bridges, eServices and any connector that reads the database directly, because those are the pieces with their own version cycles. If charts or imaging open slowly after the update, why Open Dental is slow and how to find the cause walks through the checks layer by layer. For the Open Dental environment as a whole, see Open Dental IT support and server planning. Other platforms follow the same server-first, pilot-first pattern with their own steps; Dentrix IT support and Eaglesoft IT support cover those environments. If performance drops after an upgrade, why Dentrix is slow and how to find the cause shows how to separate a software problem from a workstation, server or network one.

Network requirements are hidden inside software requirements

Even when a vendor lists only "network connection", dental workflows depend on reliable switching, name resolution, a wired path to the server, segmentation, enough bandwidth for imaging and predictable access to cloud services. A requirement page rarely says this out loud, but every slow chart and dropped image traces back to it.

Run the database server and imaging share on a wired connection. Wi-Fi is fine for a tablet in the consult room; it is a poor foundation for the computer every chart depends on.

Imaging requirements can exceed PMS requirements

A computer that satisfies the PMS may still be underpowered or unsupported for imaging, CBCT, intraoral scanner or camera software. Validate the imaging vendor's requirements separately, for every component (acquisition, viewer, server, connector), because imaging vendors often publish stricter operating system, graphics and storage requirements than the PMS does.

IMAGING SPECIFICATION CRITERIA

• • Acquisition software and driver support for the target Windows version, per sensor model
• • Viewer and rendering requirements, especially for 3D studies
• • Local cache or storage on capture and viewer workstations
• • Monitor and display requirements where the vendor specifies them
• • USB and interface compatibility for sensors and cameras, including powered hubs
• • Network and storage location for images, and the permissions on that share
• • Backup and retention impact of large image growth

What IT infrastructure does a fully digital dental imaging environment need?

A fully digital imaging office needs five layers that work together: capture devices with supported drivers, capture workstations, a central image store, a wired network path between them, and a backup that can restore images as well as the database. The PMS links to imaging through a bridge on every workstation that opens images.

Image stores grow every month and never shrink unless you archive. Size storage and backup for several years of growth, and test a restore of images, not only the PMS database. The dental backup and disaster recovery checklist covers the restore test itself.

Use a pre-upgrade go/no-go checklist

Before you change a major operating system, server or PMS version, confirm supportability, backup, dependencies, vendor availability and rollback. A technical upgrade is approved only when the clinical workflows have a test plan and someone owns the decision to stop. The acceptance checklist above is the detail; these gates are the summary.

What Does Dental IT Support Cost in 2026?

For an upgrade, budget two separate lines: the ongoing support agreement and the one-time project. Windows upgrades, server replacements, workstation refreshes and PMS version changes are usually scoped as projects, with hardware and software licensing priced on their own. Ask for the project estimate in writing, with the pilot and acceptance testing listed as tasks.

For how dental IT support itself is priced and how to compare quotes line by line, see the dental IT support cost guide.

Add lifecycle headroom instead of buying to today's minimum

Dental workstations often stay in service for years. If the practice buys exactly to today's minimum, the next Windows release, imaging update or PMS version can force another replacement sooner than planned. Buy for the expected lifecycle: the next two Windows feature releases, imaging growth and the security tools you will add.

PRODUCTION-READY CONSIDERATIONS

• • Expected device lifecycle and hardware warranty terms
• • Windows 11 hardware requirements (TPM 2.0, Secure Boot, supported processor) and the next feature releases
• • Imaging growth and CBCT rendering needs on the viewer workstations
• • Security agents, threat monitoring and audit logging overhead on every device
• • Multi-monitor layouts at the front desk and in the operatory
• • Solid-state storage, with enough free space for feature updates and local caches
• • Standard models that can be supported consistently across multiple locations

Remember that cloud PMS still has local requirements

Cloud software removes the local PMS server, but it does not remove workstation, network, browser, identity, sensor, scanner, printing or imaging requirements. Most cloud dental systems still need a local imaging bridge or acquisition software on the capture PCs. The practice still has to standardize endpoints and keep the internet connection reliable.

CLOUD READINESS INCLUDES

• • Supported browsers and operating systems, by version
• • Endpoint security and user identity configurations, including multi-factor sign-in
• • Local device and driver compatibility for sensors, cameras and scanners
• • Two internet connections with automatic failover
• • Imaging bridge or local acquisition software on each capture PC
• • Local printing and scanning workflows
• • Where images are stored (cloud, local or both) and how they are backed up

Cloud releases arrive on the vendor's schedule rather than yours. That makes the local side (drivers, browsers, bridges) the part you still control, and the part to retest after each vendor release.

Build a change-control rule for Windows and vendor updates

The goal is not to delay security patches indefinitely. The goal is to separate urgent security maintenance from feature and operating system changes that can affect dental applications or devices. NIST describes patching as preventive maintenance that needs a planned strategy; for a dental office that means a simple written rule.

THE CONTROLLED UPDATE SEQUENCE

A workable rule for most practices: monthly Windows security updates are applied on a schedule after a short pilot; Windows feature updates, PMS version upgrades and imaging upgrades go through the full acceptance checklist; emergency security fixes follow the vendor's guidance with a pilot first wherever time allows.

What to ask your IT provider before a software or Windows upgrade

Ask these before you approve the change window. Good answers are specific and written down.

1. 1. Which exact versions are we running today for the PMS, imaging, database, Windows and each bridge, and where is that inventory kept?
2. 1. Which vendor pages did you check for the target versions, and on what date?
3. 1. Which of our computers fail the Windows 11 hardware check or the strictest vendor requirement?
4. 1. Which bridges have you confirmed for the target version, and which are still unknown?
5. 1. When was the last test restore of our PMS database and image store, and what was restored?
6. 1. Which workstation will be the pilot for each role, and who runs the acceptance tests?
7. 1. What is the rollback plan, and who decides to use it?
8. 1. When does our server's operating system reach end of support, and what is the plan before then?
9. 1. Is this upgrade inside our monthly agreement or a separate project, and what does the estimate include?
10. 1. Who watches the first full clinical day after the change?

Where Legend adds value

Legend's role is to translate changing vendor requirements into a stable practice-level standard: checking the exact supported versions, then accounting for the complete workload of PMS, imaging, security, backups, network and expected lifecycle, rather than buying to the minimum line in a PDF.

Legend supports the IT environments around Dentrix, Eaglesoft, Open Dental and Archy, and imaging systems including DEXIS, Vatech, Carestream, Planmeca/Romexis and Dolphin Imaging. Legend has served over 3,500 practices since 2004, with in-house engineers; no outsourced first-level triage, 24/7 monitoring, and onsite dispatch by appointment across served dental markets; remote-first nationwide. Legend's operations are led by Ian Lynch: 22 years in dental IT; oversees the NOC, onsite dispatch and client technology roadmaps. On Google, Legend shows a 4.8 rating · 173 Google reviews.

Your Practice Needs Clear Technology Ownership

Technology should protect your patient schedule, not interrupt it. Every product in the stack has an owner on paper (the vendor) and an owner in practice (whoever answers when it breaks). Without one named owner for the whole dependency picture, upgrades become guesswork and each vendor points at the next.

Clear ownership means three documents kept current: the version inventory, the bridge inventory and the acceptance checklist from the last upgrade. With those, any qualified person can plan the next change, and the practice is not dependent on one person's memory.