Skip to main content
Infrastructure · INFRASTRUCTURE

Dental Server Support in 2026: What It Covers and Who Fixes What

The practice software took forty seconds to open a chart this morning, the same as last Tuesday. The server in the back closet has been restarted twice in a month. The old IT company's quote has a line called "server support" with a monthly figure and no description, and the new one's has the same line, a different figure and no description either. You are the owner, and nobody has told you what that line is supposed to buy.

This guide lists those tasks, puts them on a calendar, and says who fixes each common server problem: your IT provider, the software vendor (Dentrix, Eaglesoft, Open Dental, DEXIS, Carestream, Planmeca) or your own team. It is about the server that works today. When the server is already down, use the guide for the first four hours when the dental server is down; when you are deciding whether to buy another one, the replacement section near the end hands you to the right guide.

Most server failures follow the same pattern: the practice had a server, had someone who "looked after it", and found out at the failure that nobody had tested the backup, read the event log or checked the disk in months. The office had a server. It did not have server support in the sense below.

In this guide
  1. What does dental server support cover?
  2. What is actually running on a dental office server?
  3. Who fixes each dental server problem: your IT provider or the software vendor?
  4. What should a dental server maintenance calendar look like?
  5. How should Windows Server and database updates be handled on a dental server?
  6. How do you know the backups actually work?
  7. How does imaging storage growth change server support?
  8. What does server monitoring watch, and what should you hear about?
  9. What about power, UPS and shutdowns?
  10. How should remote access, antivirus and user accounts be handled on the server?
  11. When is it time to replace the server or move the practice software to the cloud?
  12. The IT side: what a good server support plan includes
  13. What to ask your IT provider about your server
  14. What to verify before you sign a server support plan
  15. How Legend Networking can help
  16. Frequently asked questions
  17. The bottom line

What does dental server support cover?

Dental server support covers eleven recurring tasks: operating-system patching in a planned window, database engine care, imaging storage management, backup verification by test restore, UPS and shutdown protection, hardware and service monitoring, remote access control, server antivirus or EDR, user and permission changes, lifecycle planning against Microsoft's end-of-support dates, and a monthly report. Each task has one owner.

Read the table as the job description for the machine. "IT" is your IT provider, "vendor" is the maker of the software involved, "practice" is your office manager or owner. Where two columns are marked, the first named is accountable and the second contributes.

TaskIT providerSoftware vendorPractice
Windows Server updates in a planned windowOwns: schedules, tests, installs, confirms the practice software opens afterwardsPublishes which Windows versions it supportsAgrees the window; reports anything odd the next morning
Database engine care (version, settings, integrity checks)Owns the engine the software runs on; schedules checks after hoursOwns errors inside its own database tool; publishes supported engine versionsReports error messages word for word
Imaging storage growthOwns: watches free space, moves or expands storage before it runs outStates where its images are stored and how to relocate themTells IT before adding a CBCT, scanner or new imaging software
Backup verificationOwns: daily check, monthly test restore, written resultStates what folders must be backed upReads the monthly report; asks for the last restore date
UPS and clean shutdownOwns: sizing, shutdown software, battery testNoneNever holds the power button; calls before touching it
Monitoring (disk, RAID, temperature, services, logins)Owns the monitoring and the responseNoneReceives the summary
Remote access to the serverOwns: one controlled door, multifactor sign-in, logsNeeds access for support sessions; uses the door IT providesApproves who may connect
Antivirus or EDR on the serverOwns installation, exclusions the software needs, alertsPublishes required exclusionsNone
User accounts and permissionsOwns Windows accounts, shares and remote accessOwns accounts inside the practice softwareTells IT the same day someone starts or leaves
Lifecycle planningOwns: tracks warranty, Windows Server and database end-of-support dates; proposes the replacement yearPublishes system requirements per versionBudgets; approves
Monthly reportOwnsNoneReads it; asks questions

If your current plan covers the first row and the sixth and nothing else, you have monitoring with patching, not server support. The remaining sections explain each row well enough that you can tell the difference on a quote.

What is actually running on a dental office server?

A dental office server runs a database engine for the practice management software, a store of images and documents, several background services the software depends on, file shares, a backup agent, a remote access tool and security software. Each piece fails in its own way and has its own support path, so "the server" is never one problem.

ComponentWhat it doesVendor-documented fact (read 18 November 2026)Who supports it
Practice management database engineHolds every chart, ledger and appointmentOpen Dental runs on MySQL or MariaDB and recommends "MariaDB 10.5, however many offices are on MySQL 5.5"; "MySQL 8.0 is not compatible with Open Dental." Dentrix and Eaglesoft install the database engine they need with the software; ask the vendor in writing which engine and version your server runsIT keeps the engine on a supported version and the server it runs on healthy; the vendor supports its own database tools
Image and document storeX-rays, intraoral photos, scans, scanned documentsOpen Dental's manual names two paths to back up: the database folder and the "OpenDentImages" A to Z folder. Imaging suites keep their own storesIT watches space and permissions; the imaging vendor owns the image database format
Background servicesJobs that run with nobody logged inThe Open Dental Service "should only be installed on the server" and, among other things, "Imports clearinghouse reports if Receive Reports by Service is checked", downloads email and runs aging and recurring chargesIT keeps the service running and starts it after restarts; the vendor supports its configuration
File shares and permissionsWorkstations reach the database and images over the networkOpen Dental states its database files are always "on the same computer where MySQL is installed, not to another computer or NAS (too slow)"IT
Backup agentCopies the database and images off the machineOpen Dental: "At minimum, backups should be made daily."IT, with the vendor's list of what to include
Remote access toolLets IT and vendors work on the server from outsideCISA: "Do not expose services, such as remote desktop protocol, on the web."IT
Antivirus or EDRWatches the server for malicious softwareVendors publish folders to exclude from scanningIT
Operating systemWindows Server, with its own support clockSee the lifecycle table belowIT

Two things follow from the table. First, a server that "works" can still be quietly failing a row: the backup agent copying an empty folder, the background service stopped since the last restart so clearinghouse reports never arrive, the database engine two versions behind what the vendor supports. Second, the vendor's support line is for the software's own windows and tools; the machine under it is the IT provider's. Legend's platform pages describe the IT side for Open Dental, Dentrix and Eaglesoft offices, and the wider dental practice management software support page covers imaging.

Who fixes each dental server problem: your IT provider or the software vendor?

Your IT provider fixes anything about the machine, Windows, the network path, storage, backups, accounts and security; the software vendor fixes what happens inside its own program or database tools once the machine is healthy. Call IT first for slowness, errors on several computers, missing images and anything after a restart, update or power event; IT brings in the vendor.

The vendors say as much about their own scope. Open Dental's support page states that "Up to two specific issues can be answered per call/email/chat" and lists a phone number and email for its technical support; Dentrix publishes a support phone line and chat for weekdays. Neither offers to manage your Windows updates, your backups or your storage. That is the boundary.

What you seeMost likely causeWho fixes itWhat to do first
Every computer is slow in the practice software, all dayServer disk near full, failing drive in a RAID set, database maintenance running during hours, antivirus scanning the database folderITAsk IT for the free space, the RAID status and the last database maintenance time
One computer is slow, the rest are fineThe workstation or its network cable, not the serverITSay so on the call; it changes the diagnosis
"Cannot connect to database" or "server not found" on every screenDatabase service stopped, server restarted and the service did not start, network switch or cable to the serverITDo not restart the server yourself; call IT and follow the outage guide linked at the top of this page
An error inside the practice software that names a table, a record or a procedure codeData or configuration inside the vendor's databaseVendor, after IT confirms the server is healthyWrite the message down word for word; IT opens the vendor ticket with it
X-rays taken this morning are missing on another computerImaging store permission, mapped drive, or the imaging service on the serverIT, with the imaging vendor if its database is involvedNote the computer that took the image and the one that cannot see it
Clearinghouse reports, recurring charges or aging stopped arrivingA background service on the server is stoppedITAsk IT to check the service and when it last ran
Practice software asks for an update, or stopped working after oneThe vendor's update, or a Windows update it was not ready forVendor for the software update; IT for Windows and for installing the vendor's update on the serverAgree who installs updates and when (next section)
The server restarted on its own overnightPower event, failed update, hardware faultITAsk IT to read the event log; Microsoft says Windows logs Event ID 41 when a computer "shuts down unexpectedly"
A staff member who left can still sign inAccounts not removed in Windows, the practice software or the remote toolIT for Windows and remote access; the practice removes the software login, or asks IT toSame-day removal; see the employee IT onboarding and offboarding checklist
A vendor says "it is your network" and IT says "it is their software"Nobody holding both endsIT should own the ticket and stay on the vendor callAsk IT to run a joint session; the guide to dental software support vs IT support explains the boundary in detail

The rule that settles most arguments: the party that can see the server's event log, disk, services and network should go first, because almost every vendor diagnosis starts with "is the server healthy?" For the whole office, not only the server, the guide to who provides technical support to a dental office maps every system to its support source.

What should a dental server maintenance calendar look like?

A dental server maintenance calendar runs on five rhythms: daily automated checks of backups, disk and services; a weekly review of alerts and free space; a monthly patch window with a test restore and a written report; a quarterly check of accounts, UPS and database health; and an annual lifecycle review against warranty and Microsoft's dates.

RhythmTaskOwnerWhat "done" looks like
DailyBackup job completed and the copy exists off the serverIT (automated, human-read)A success record with size and time, and an alert when it fails
DailyDisk free space, RAID health, temperatures, critical services runningIT monitoringNo red lines; a ticket opens on any failure
DailyRemote access and failed login attempts reviewedIT monitoringUnusual attempts flagged
WeeklyAlerts reviewed, free-space trend checked, pending updates listedITA short note of what changed
WeeklyStaff report slowness or error messages in writingPracticeOne list, not ten phone calls
MonthlyWindows Server updates installed in the agreed window after hours; practice software and imaging opened on two workstations afterwardsITA record of what was installed and that the office opened clean
MonthlyTest restore of the database and a sample of images to a separate machineITA dated restore result in the report
MonthlyDatabase integrity check run after hours (Open Dental: "We do not recommend running database maintenance during office hours because it can cause severe network slowness.")IT, with the vendor's toolA clean result or a vendor ticket
MonthlyMonthly report delivered and readIT writes; practice readsQuestions asked within the month
QuarterlyWindows, practice software and remote-access accounts reconciled against the staff listIT and practiceLeavers gone, shared logins removed
QuarterlyUPS self-test and battery age checked; shutdown software confirmedITRuntime known; replacement date set
QuarterlyImaging storage growth measured; months of space remaining estimatedITA number, and a plan if it is under twelve months
AnnuallyWarranty, Windows Server and database end-of-support dates reviewed; replacement year proposedITA written line in the budget
AnnuallyFull restore rehearsal: could the office open on a loaner server tomorrow?ITTime to restore recorded

The two rows practices skip most are the monthly test restore and the annual rehearsal. A backup that has never been restored is a hope, not a plan; the backup section below says what the test has to prove.

How should Windows Server and database updates be handled on a dental server?

Updates on a dental server go in a planned window after hours, after the backup has run and with someone checking that the practice software and imaging open afterwards. Microsoft publishes its monthly security update on the second Tuesday of each month; the vendor's own updates are installed separately, never on the same night as a Windows update.

NIST's guide to patch management puts the principle plainly: "Patching should be considered a standard cost of doing business and should be rigorously followed and tracked." CISA says the same from the attacker's side, telling organisations to "Regularly patch and update software and operating systems to the latest available versions" and to "Install updates as soon as possible". A dental office has one extra constraint: the server cannot reboot at ten in the morning, and the practice software must be tested after every change. That is why server support means a window, a test and a record, not an "automatic updates on" checkbox.

A patch window that works in a dental office

    1. The backup runs and is confirmed before anything is installed.
    1. Windows Server updates install in the agreed after-hours window; the server restarts once.
    1. The database service and the practice software's background service are confirmed running.
    1. The practice software and the imaging software are opened on two workstations and a chart with images is loaded.
    1. The result is written down: what was installed, what was tested, anything deferred and why.
    1. Vendor updates to the practice software are scheduled on a different night, after reading the vendor's release notes. Open Dental, for example, offers a "New stable version" that "has gone through the beta testing phase and is considered stable" and a beta it says "should only be installed if the practice is willing to take a small risk".

The guide to dental IT patch management covers the workstations and the exceptions, such as a sensor driver that a Windows update breaks.

The lifecycle table: when the server's software stops being supported

Each version of Windows Server and SQL Server has a published end date after which Microsoft issues no security updates. The dates below are from Microsoft's lifecycle pages, read on 18 November 2026, written as US dates.

ProductMainstream support ended or endsExtended support endsWhat it means for a dental server
Windows Server 201611 January 202212 January 2027Plan now; see the Windows Server 2016 end of support plan for January 2027
Windows Server 20199 January 20249 January 2029Security updates only; a replacement decision belongs in the 2027 or 2028 budget
Windows Server 202213 October 202614 October 2031Now in extended support: security fixes continue, feature updates do not
Windows Server 202513 November 202914 November 2034The current version for a new server
SQL Server 201613 July 202114 July 2026Extended support has ended; Microsoft's page lists only paid Extended Security Updates beyond it. Any imaging or practice software still using it needs a vendor conversation
SQL Server 201928 February 20258 January 2030Security updates only
SQL Server 202211 January 202811 January 2033Current

Not every dental system uses Microsoft SQL Server; Open Dental uses MySQL or MariaDB, and other vendors run their own engines. The point of the table is that whoever supports your server should be able to tell you, today, which of these dates applies to your machine and what the plan is. If they cannot, that is the first question to ask.

How do you know the backups actually work?

You know a dental backup works when someone has restored it, recently, to a machine that is not the server, and opened the practice software against the restored copy. A green "backup completed" message proves a job ran, not that the copy is usable. Open Dental's manual says backups should be "tested regularly to ensure quality" and describes exactly how.

The method in that manual is the one to ask your IT provider to follow: verify "by restoring backups to a secure, off-site computer not connected to the office network", so the test can never overwrite the live database. The manual also lists what has to be in the copy for Open Dental: the database folder and the images folder, plus any other office documents. Every practice management system has an equivalent list, and the vendor publishes it; your IT provider should be able to show you where it is.

Three sentences from primary sources belong on the wall of any server closet:

    • Open Dental: "RAID is not a backup solution and should not be relied on for backups or disaster recovery plans." Mirrored disks protect you from one drive dying; they copy a deleted chart or an encrypted file to both drives at once.
    • CISA's ransomware guide: "Maintain offline, encrypted backups of critical data, and regularly test the availability and integrity of backups in a disaster recovery scenario." A copy the server can reach is a copy an attacker on the server can reach.
    • 45 CFR 164.308, the data backup plan standard: "Establish and implement procedures to create and maintain retrievable exact copies of electronic protected health information." The word that matters is retrievable; ask your compliance adviser how it applies to your office, because this guide does not interpret the rule.

What this means for the support plan: a daily backup to two places, one of them off site and one of them not reachable with the server's own credentials; a monthly test restore with the date and the time it took written in the report; and a yearly rehearsal of opening the office from the copy. The design choices, including cloud versus local and how long to keep copies, are in the guide to dental data backup; the targets for how fast each system must come back belong in a written dental disaster recovery plan; the server support plan is what checks that both are still working every month.

How does imaging storage growth change server support?

Imaging turns a dental server from a database machine into a storage machine. Sensors add a little every day; a CBCT unit, intraoral scanner or new imaging suite adds a great deal, and the first symptom of a full disk is usually the practice software slowing for everyone. Server support means measuring the growth quarterly and acting a year ahead.

The reason this is a support task and not a one-off purchase decision is that the image store moves through three stages that each need a hand. First, free space: the monitoring in the calendar above should hold a free-space number and the months it represents at the current growth rate. Second, the location of the store: imaging software keeps its own database and file paths, and moving them to a larger disk or a second volume is a documented procedure for each product, not a drag and drop; when an office adds a scanner or CBCT, IT needs to know before the installer arrives. Third, the archive: old studies that are rarely opened but must be kept can live on slower storage, with the imaging vendor's own archive feature where one exists, and that decision is easier taken before the disk is at ninety-five percent than after.

The CBCT computer and network requirements guide covers the hardware side: what a 3D unit asks of the server and the network. Each imaging suite in common use, from DEXIS and Carestream to Planmeca Romexis, keeps its own store, and that store is where most of the growth lands.

A point for the owner, not the technician: the backup must grow with the store. A backup target sized for last year's images silently stops copying the newest ones when it fills, which is how an office finds out, on the day it needs a restore, that its only backup stopped updating weeks ago.

What does server monitoring watch, and what should you hear about?

Server monitoring watches the things that fail before the practice notices: disk space and drive health, RAID status, the services the practice software needs, backup job results, failed and unusual logins, pending reboots and unexpected restarts. The practice should hear about failures the same day and see everything else in a plain monthly report.

Monitoring without a response is a dashboard. What you are buying is the pair: a sensor and a person who acts on it. The guide to 24/7 monitoring versus dental IT support explains the difference between watching and supporting; this section is about what the report should prove.

What a monthly server report should show

    • Backup results for every day of the month, the size of the last copy, and the date and duration of the last test restore.
    • Free disk space on each volume and the months of imaging growth it represents.
    • RAID and drive health, and any drive replaced.
    • Windows updates installed, the date of the window, and the result of the post-update test.
    • Database maintenance or integrity check: date and result.
    • Unexpected restarts (Microsoft's Event ID 41 entries) and power events, with the cause found.
    • Remote access sessions to the server: who, when, why.
    • Accounts added and removed in Windows and the remote tool.
    • Warranty end date and the Windows Server and database end-of-support dates that apply to this machine.
    • Open items, each with an owner and a date.

If you receive a report with the first, fourth and sixth lines missing, ask why. Those three are the ones that cost a day of production when they are wrong.

What about power, UPS and shutdowns?

A dental server needs an uninterruptible power supply sized to carry it through short outages and to shut it down cleanly in a long one, with shutdown software installed and the battery tested on a schedule. Server support owns that sizing and testing; staff own one rule, which is never to hold the power button or pull the plug.

Abrupt shutdowns are where databases get hurt, and Windows keeps the evidence: "If your computer shuts down unexpectedly, Windows logs Event ID 41 the next time that the computer starts." A support plan that reads that log each month knows about the power event the practice forgot to mention. The full treatment of safe shutdown, the restart mistakes and the UPS checklist is in the guide to dental server shutdown steps, restart mistakes and the UPS checklist. It is not repeated here; the support task is to make sure the UPS, the software and the test exist and are recorded in the report.

How should remote access, antivirus and user accounts be handled on the server?

Remote access to a dental server should go through one controlled door with multifactor sign-in and a log, never a remote desktop port open to the internet; the server should run security software that watches behaviour, with the exclusions the practice software vendor publishes; and every person should have their own account, removed the day they leave.

CISA's guidance is blunt about the first point: "Do not expose services, such as remote desktop protocol, on the web." Vendors need to reach the server for support sessions, and so does your IT provider, so the answer is not "no remote access" but one tool, owned by IT, that records who connected and when. The guide to dental office remote access security covers the tools and settings.

On the second point, a server is not a workstation: it runs a database whose files change constantly, so ordinary antivirus can slow it badly or quarantine a live database file unless the vendor's exclusion list is applied. Behaviour-based tools suit a server better; the guide to EDR versus antivirus for dental offices explains the difference. The server itself should be used only for its job: not for browsing, email or watching a video on the night shift, because every program opened on it widens what an attacker can reach.

On the third point, the practice software and Windows have separate account systems. Open Dental's manual states that "Every person who uses Open Dental should have a unique user name and password for logging on", and the same principle applies to Windows accounts and the remote tool. The HIPAA Security Rule's administrative safeguards list, at 45 CFR 164.308, includes "Log-in monitoring" and "Password management" among its implementation specifications and requires procedures to "regularly review records of information system activity, such as audit logs, access reports, and security incident tracking reports"; how it applies to your office is for your compliance adviser to say; this guide does not interpret it. The practical task for the support plan is the quarterly reconciliation in the calendar: every account on the server matched to a person who still works there.

When is it time to replace the server or move the practice software to the cloud?

It is time to decide when the server's Windows version is inside a year of its end-of-support date, the hardware warranty has ended, storage is inside a year of full, or the vendor's next version will not install on it. Server support is what tells you a year ahead; the decision itself, replace or move, deserves its own comparison.

SignWhat it tells youWhere to read next
Windows Server end of support within twelve monthsSecurity updates will stop; vendors drop support soon afterThe lifecycle table above, and the Windows Server 2016 plan linked from it if that is your version
Warranty expired, parts no longer soldA failed drive or power supply becomes a multi-day outageThe replacement comparison
Imaging storage under a year from fullA storage project is coming whether or not the server is replacedThe imaging section above
The practice software vendor's next version needs a newer Windows Server or database engineThe upgrade path runs through the serverAsk the vendor in writing; the dental software system requirements guide lists what the main systems publish
Second unexplained failure in a short periodThe machine is telling youThe replacement comparison
A cloud version of your software is under considerationThe server's role shrinks but rarely disappearsWhether you still need a server with cloud dental software

The comparison of a new on-site server against a hosted or cloud system, with the five-year worksheet and the scorecard, is the job of the guide to replacing the server or moving the practice software to the cloud. If the answer is a new server for a Dentrix office, the Dentrix server migration checklist covers the move itself. One support task remains after any replacement: the old server's drives hold patient data, and 45 CFR 164.310 lists "Disposal" as a required specification for "the hardware or electronic media on which it is stored". Ask for a written record of how the old drives were wiped or destroyed.

The IT side: what a good server support plan includes

A good server support plan names one party accountable for the whole machine, lists the eleven tasks from the first table with their rhythms, states the patch window and the test, promises a monthly report with a test-restore line, and says in writing how vendor tickets are handled. Everything else on the quote is detail.

Here is the IT side of each row, the part the practice does not see:

    • Patching is a window, a test and a record, every month, with the vendor's updates kept separate. It is not "automatic updates on".
    • Database care means keeping the engine on a version the vendor supports and running the vendor's integrity tool after hours. It does not mean editing your data; that is the vendor's.
    • Storage means a number of months of free space, reviewed each quarter, and a plan when the number is under twelve.
    • Backups mean two copies, one off site and one the server cannot reach with its own credentials, and a restore test with a date.
    • Monitoring means a person acts on the alert, and the report proves it.
    • Access means one remote door with multifactor sign-in, accounts tied to people, and a quarterly reconciliation.
    • Lifecycle means your provider can say, today, when your Windows Server and database versions stop being supported and what year the replacement is budgeted for.

Server support is usually one part of a wider agreement that also covers the workstations, the network and the help desk; the server is one of the nine components of a dental practice's IT infrastructure, and the others have their own standards. Where the wider agreement is the buying decision, the page on managed IT services for dental practices describes what a full plan should include, and the Legend page for dental servers and workstations describes how a server project itself runs, from review and quote to staging, installation and support. If the server trouble has you questioning the whole relationship, start with the guide to how to choose a dental IT company, compare against the best dental IT companies, and judge every candidate's dental IT support offer by whether it can answer the questions below in writing.

What to ask your IT provider about your server

Backups and restores

  • When was the last test restore of our database and images, how long did it take, and can we see the record?
  • Where are the two copies, and which one cannot be reached with the server's own credentials?

Updates and lifecycle

  • When is our monthly patch window, what is tested afterwards, and who installs the practice software vendor's updates?
  • Which Windows Server and database versions does our server run, and when does Microsoft stop supporting each?
  • When does the hardware warranty end, and what year is the replacement budgeted for?

Storage and performance

  • How much free space does the imaging store have, and how many months is that at our growth rate?
  • When did database maintenance last run, and what did it find?

Access and security

  • How do you and the vendors reach our server remotely, is multifactor sign-in on, and can we see the session log?
  • Which accounts exist on the server today, and when were they last matched to our staff list?
  • What security software runs on the server, and which folders are excluded for the practice software?

Reporting

  • Can we see last month's server report?

A provider who answers these from records, not from memory, is doing server support. A provider who needs to "check and get back to you" on the restore date is doing something less.

What to verify before you sign a server support plan

Quotes for server support look alike. These checks separate them, and each is a question you can put in writing before you sign.

    1. The task list. The eleven tasks from the first table, or your provider's equivalent, with the rhythm of each. "Server monitoring and maintenance" with no list is not a scope.
    1. The patch window and test. A stated window, a stated post-update test, and a record you receive.
    1. The restore test. How often, to what machine, and how it is reported. Ask for the most recent one from an existing client, redacted.
    1. Two backup copies. Where each lives and which one is unreachable from the server. Ask how retention is set and who can delete a copy.
    1. Vendor tickets. Who opens them, who stays on the call, and whether that time is inside the plan.
    1. Remote access. The tool, multifactor sign-in, and whether you can see the session log.
    1. The report. A sample, with the ten lines from the monitoring section above.
    1. Lifecycle. Whether the provider will tell you the replacement year in writing and track the Microsoft dates for you.
    1. What is excluded. Hardware, parts, after-hours project work, the vendor's own support fees. Written down.
    1. Exit. What you receive if you leave: documentation, admin credentials, the backup copies and the monitoring history.

Only after these are answered does the monthly figure mean anything. Two quotes with the same figure can describe very different amounts of work, and the cheaper one is often the one with no restore test.

How Legend Networking can help

Legend Networking, based in Dallas, has served over 3,500 practices since 2004: 22+ years in dental IT. Monitoring runs 24/7, and one general number, 1-800-794-1588, reaches a helpdesk staffed 24/7. The engineers are in-house, with no outsourced first-level triage; support is remote-first nationwide, with onsite dispatch by appointment across served dental markets. On the software side Legend supports the IT environment for Dentrix, Eaglesoft, Open Dental and Archy; on the imaging side, for DEXIS, Vatech, Carestream, Planmeca/Romexis and Dolphin Imaging.

Ian Lynch, who wrote this guide, has 22 years in dental IT and oversees the NOC, onsite dispatch and client technology roadmaps. On Google, Legend holds a 4.8 rating across 173 reviews. For an example of the starting point, see a technology onboarding project whose published scope covers network and server review, security, backups, software and user access, and find your area on the dental IT support in your city pages. The questions in the two sections above are a fair test for any provider, including us.

Questions

Frequently asked questions

What does dental server support include?

Dental server support includes planned Windows Server updates with a post-update test, care of the database engine the practice software runs on, imaging storage management, daily backup checks with a monthly test restore, UPS and shutdown protection, hardware and service monitoring, controlled remote access, server security software, account changes, lifecycle planning against Microsoft's dates, and a monthly written report.

How much is a dental server?

The price of a dental server depends on the processor and memory the practice software and imaging need, the storage and its mirroring, the Windows Server licence and any database licence, the warranty term, the UPS, and the labour to migrate data and reconnect every workstation and imaging device. Ask for a quote that separates hardware, licences and labour, and compare it with a hosted option in the same table.

How can I contact Dentrix tech support?

Henry Schein One publishes Dentrix support on dentrix.com/support: a US phone line at 800-336-8749 and a chat service, both available on weekdays, with hours listed on that page as of 18 November 2026. Before calling, have your IT provider confirm the server, its services and the network are healthy, because Dentrix support troubleshoots its software, not your Windows server or backups.

How often should a dental server be maintained?

Daily automated checks of backups, disk space and services; a weekly review of alerts; a monthly patch window, test restore, database integrity check and report; a quarterly reconciliation of accounts, a UPS test and a storage growth measurement; and an annual review of warranty and Microsoft end-of-support dates with a full restore rehearsal. The calendar in this guide lists each task with its owner.

Who fixes a Dentrix, Eaglesoft or Open Dental database error, the vendor or IT?

Your IT provider goes first, because almost every vendor diagnosis begins with whether the server, its services, storage and network are healthy. Once the machine is proven sound, the software vendor fixes errors inside its own database tools. Open Dental's support page, for example, answers software issues by phone, chat and email; neither it nor Dentrix manages your Windows updates, backups or storage.

Does a dental office still need server support with cloud practice software?

Usually some. Cloud practice software removes the practice database from the office, but imaging capture, CBCT storage, local file shares, printing and the network often stay on a local machine that still needs updates, backups, monitoring and access control. Our guide on whether you still need a server with cloud dental software covers what usually stays in the office.

Is RAID the same as a backup for a dental server?

No. Open Dental's manual is explicit that RAID is not a backup and should not be counted on for disaster recovery. Mirrored drives protect against one disk failing, but a deleted chart, a corrupted database or an encrypted file is written to both drives at once. A backup is a separate copy, kept off the server, with one copy off site.

What should a monthly dental server report show?

Backup results for every day with the last test-restore date, free disk space with months of imaging growth remaining, RAID and drive health, Windows updates installed and the post-update test, the database integrity check result, unexpected restarts and power events, remote access sessions, account changes, warranty and Microsoft end-of-support dates, and open items with owners and dates.

When should a dental server's Windows version be replaced?

Before Microsoft's extended support end date for that version, because security updates stop then. Windows Server 2016 reaches that date on 12 January 2027, Windows Server 2019 on 9 January 2029 and Windows Server 2022 on 14 October 2031, according to Microsoft's lifecycle pages read on 18 November 2026. Ask your practice software vendor when it stops supporting your version as well.

Can the dental server be used as a workstation when the office is busy?

It should not be. A server used for browsing, email or everyday work exposes the machine that holds every patient record to the same risks as a front-desk computer, and a program crash or a forced restart on it stops the whole office. Keep the server for its job, reach it only through the controlled remote tool, and give staff a spare workstation instead.

The bottom line

If the restore date, the patch window or the replacement year are not written down somewhere you can find, ask for a Free Dental IT Assessment. It reviews your computers, software, network security, backups and performance, and you receive written findings with prioritized recommendations. Legend's dental servers and workstations page describes how a server review and project run, and the dental IT support page describes the ongoing plan around it. Bring the two question lists from this guide; a good answer to each is what you are paying for.

Ian Lynch
About the author

Ian Lynch

Owner & Operator, Legend Networking

22 years in dental IT. Oversees the NOC, onsite dispatch and client technology roadmaps for practices nationwide.

  • Operations center

    Dallas, Texas

    Serving dental practices nationwide since 2004

  • NOC hours

    24/7 monitoring

    Helpdesk staffed 24/7 at 1-800-794-1588

  • Engineers

    In-house only

    No outsourced first-level dental IT triage

  • Onsite dispatch

    By appointment

    Technicians deployed across served dental markets

About Legend Networking
Your next step

Ask for a review of your server before it decides for you

Tell us what you are running and we will review it with you.

Or call 1-800-794-1588