Skip to main content
Software · ORAL SURGERY SOFTWARE

WinOMS Server vs Hosted vs Sensei Cloud: The IT Checklist for Oral Surgery Practices

It is Friday afternoon and three things are on your desk. The server in the back closet still runs Windows Server 2016. There is a quote for "the v10 conversion" that nobody in the office can quite explain. And an email from a software company says it is time to move to the cloud. Your software vendor's support line has already told you that the server, the network and the backup are your IT person's job. Before you spend money on any of it, you want to know what WinOMS actually needs.

This guide puts the WinOMS system requirements for all three setups on one page, from the vendor's current documents, checked on 26 October 2026. It gives you a decision table, a server spec sheet, the SQL licence thresholds, a v10 conversion worked example, a backup routine and the questions to ask before you sign. It is one part of our oral surgery practice IT guide, and the computers, network, server and backups around the software are what our dental IT support for oral surgery practices covers. It is written by Ian Lynch, who has 22 years in dental IT and oversees the NOC, onsite dispatch and client technology roadmaps at Legend Networking.

Who this is for:

- your WinOMS server runs Windows Server 2016, and Microsoft's extended support ends on 12 January 2027;
- a v9 (Sybase) to v10 (Microsoft SQL Server 2019) conversion is still pending;
- someone in the practice is pushing "the cloud", and you want to compare WinOMS Hosted and Sensei Cloud fairly;
- the vendor told you the network and the backup belong to your local technician, and you want to know what that covers.

In this guide
  1. Who is responsible for what when you run WinOMS?
  2. Which WinOMS setup fits your practice: on-premises, Hosted or Sensei Cloud?
  3. What server does WinOMS 10.1 need?
  4. SQL Server Express or Standard: which licence does your WinOMS database need?
  5. How long does the WinOMS v10 SQL conversion take, and what must happen first?
  6. How do you back up WinOMS properly?
  7. How much internet does WinOMS Hosted or Sensei Cloud need?
  8. How should satellite offices and remote surgeons reach WinOMS?
  9. What to ask your IT provider about a WinOMS server or cloud move
  10. The bottom line
  11. Frequently asked questions
  12. The bottom line

Who is responsible for what when you run WinOMS?

The vendor supports the WinOMS application. Its own technician guide makes the "local technician" fully responsible for the office network, the hardware configuration, and setting up and teaching backup and restore. The practice owns the backups and the SQL licence decision. Your IT team carries most of the work around the software.

That split comes straight from the vendor's WinOMS Technician's Installation Guide (the "Tech Pack"), whose Technician Acknowledgement reads: "The local technician is fully responsible for the configuration, installation, and maintenance of the client's computer network." It adds that WinOMS support "does not train offices on configuring the backup system or restoring a database." Here is the same split, task by task.

WinOMS taskSoftware vendor (WinOMS support)Your IT teamThe practice
Server hardware and WindowsPublishes the System RequirementsBuys, builds, patches and replaces the serverApproves the spend
Office network, switches, Wi-FiDoes not support "the installed network or its related issues"Designs and maintains itReports problems to IT first
PrintersNot supported, per the Tech PackInstalls and maintains themBuys from the certified list
Backup setupDoes not provide "MSSQL backup and database maintenance plans"Configures and monitors the routine"Responsible for maintaining backups"
Restoring dataAsks the office to contact support for a restoreKeeps the backup files readable and off-siteBooks a test restore with the vendor
SQL Server licenceSells and assigns the Express or Standard licenceReports the database sizePays for the licence
v9 to v10 conversion (on-premises)Supplies installer, checklist and troubleshootingRuns the conversion windowPicks the date and stops using WinOMS
v9 to v10 conversion (Hosted)Carestream Dental Cloud team performs it on a weekendChecks the office workstations and devicesOffers three weekends
Workstation updatesSupplies the updateRuns it on each PC after the serverLogs out on time
Remote and satellite accessStates what is supported (RDS is not)Builds the VPN and firewall exceptionsDecides who may work remotely

Source: WinOMS Tech Pack OL700-03, pages 1, 4, 5 and 8; WinOMS 10.1.x System Requirements, page 7. Checked 26 October 2026.

For support with the application itself, use the vendor's WinOMS support page, which lists phone, email and chat. For the whole-office question of who to call for what, see the pillar guide.

Which WinOMS setup fits your practice: on-premises, Hosted or Sensei Cloud?

On-premises WinOMS suits a practice that wants its database in the building and has an IT team to run the server and backups. WinOMS Hosted suits an office happy to swap the server for a steady internet line. Sensei Cloud is a move to a different, browser-based product. If you are unsure about the software itself, decide that first.

The table below compares what each choice asks of your office. Every figure comes from the current vendor documents named under the table.

What changesOn-premises WinOMS 10.1WinOMS Hosted (Citrix)Sensei Cloud (browser)Another OMS system
Where the database livesYour dedicated server, on SQL Server 2019Carestream Dental's serversThe vendor's cloudDecide software first
Server you buyQuad-core, 16 GB, 100 GB free recommendedNone for WinOMS itselfNone for the software itselfCompare practice management software
Internet neededBroadband recommended for eClaims and ePayments; the database runs on your office network10 to 40+ Mbps by user count, 2 Mbps per simultaneous user, latency 50 ms or less10/10 Mbps minimum, 25/10 recommendedAsk that vendor
WorkstationWindows 11 Pro recommended, Windows 10 Pro supportedCore i5, 8 GB, Windows 11 Pro recommended; Mac through Citrix WorkspaceCore i3, 8 GB, Chrome or Edge, a supported Windows 10 or laterAsk that vendor
What stays in the officeEverythingImaging capture, the monitor station, scanners, signature pads, card terminalsImaging (CS Imaging 8, Windows only), the monitor PC, TWAIN scannersAsk that vendor
Vitals monitorAnesthesia Module installed locally over LAN or VPNVirtual Channel client on the monitor PC; stays wiredCriticare monitors only (Sensei help, checked 26 Oct 2026)Ask which monitors are supported
Who runs upgradesYour IT team, server firstCarestream Dental Cloud teamThe vendorThat vendor
Who owns the backupThe practice, through your IT teamAsk the vendor what it keeps and how you get a copyAsk the vendor what it keeps and how you get a copyAsk that vendor

Sources: WinOMS 10.1.x System Requirements pages 1, 2 and 7; WinOMS 10.1.x Hosted System Requirements pages 1 to 3; Sensei Cloud System Requirements; Sensei vitals monitor integration help. Checked 26 October 2026.

Whichever column you are in, the monitor station stays a wired, local device; how to connect the sedation monitor station has its own guide. What happens on a surgery day when the server or the internet fails is covered in the surgery-day downtime plan.

Choose on-premises WinOMS if:

    • you want the database on hardware you control, and you have budget for a server refresh before 12 January 2027;
    • your IT team can run a stopped-database backup every night and check it;
    • your internet is slow or unreliable, or several surgeons work from the same building.

Choose WinOMS Hosted if:

    • you would rather pay for a strong internet line than for a server and its replacements;
    • your staff already use WinOMS and you do not want to retrain them;
    • you can wire every front-desk and monitor PC and keep the latency at 50 ms or less.

Consider Sensei Cloud if:

    • you are ready for a different product, not just a different place to run WinOMS;
    • your monitors are on the Criticare list, or you are prepared to change them;
    • you have checked every integration you rely on against its own requirements.

For the general money question of buying a new server versus moving to the cloud, our guide to dental server replacement vs cloud migration has the worksheet; this page does not repeat it.

What does "Hosted" mean for WinOMS?

WinOMS Hosted is the same WinOMS software running on Carestream Dental's servers, which your staff reach through Citrix Workspace, a remote-application client. The vendor calls the Hosted workstation a "modestly configured computer" for scheduling, billing and payments, and says it "is not suitable for image acquisition." Budget at least 2 Mbps for each simultaneous user, with latency of 50 ms or less.

Is Sensei Cloud the same as WinOMS in the cloud?

No. Sensei Cloud is a separate, browser-based practice management product from the same company, not WinOMS on a remote server. Sensei's own support page says there is "no immediate requirement to change systems" and that "Migration is optional and can be planned over time." Before you move, check these five things with the vendor in writing:

Check before you move to Sensei Cloud

  • Imaging: local imaging runs on CS Imaging version 8 with Imaging Suite 3.3.0.4, Windows only; confirm how your existing images move.
  • Integrations: "you must meet the system requirements of that product or service in addition" to Sensei Cloud's own.
  • Monitors: the vitals integration "is currently only available for Criticare Technologies, Inc. monitors"; list your models.
  • Data conversion: which records, letters and reports convert, and which stay behind.
  • Exit: how you get a full export of your data if you ever leave.

For cloud dental software more broadly, see our piece on cloud dental software (general dentistry).

Do you still need a server in the office if WinOMS is hosted or you move to Sensei Cloud?

Usually you still need something local. Imaging capture, the monitor workstation, TWAIN scanners, signature pads and card terminals stay in the building with either option. The Hosted document says the Hosted workstation is not for image acquisition, and Sensei Cloud imaging runs on locally installed CS Imaging 8. Whether you need a local imaging server is a question for your imaging vendor.

What server does WinOMS 10.1 need?

WinOMS 10.1 recommends a dedicated server with a quad-core CPU, 16 GB of RAM and 100 GB of free disk, on Windows Server 2025 or 2022 (64-bit). The minimum is a dual-core CPU and 8 GB of RAM, and Windows Server 2019 and 2016 are still supported. Remote Desktop Services is not supported, and virtual machines are not certified.

Hand this spec sheet to whoever buys the server.

ItemRecommendedMinimumWhat it means for you
CPUx86 or x64 quad-coredual-coreBuy above minimum; the server will run for years
RAM16 GB8 GB16 GB is the floor worth paying for
Free disk100 GB100 GBSize for 3 to 4 times your database at conversion, not just 100 GB
Windows Server2025 or 2022, 64-bit2019 or 2016, 64-bit (supported)2016 loses Microsoft support on 12 January 2027
DatabaseMicrosoft SQL Server 2019 (Express or Standard licence)sameLicence depends on database size (next section)
Network cardEthernet 100/1000sameWire it; no Wi-Fi for the server
Ports and drivesDVD drive, two or more powered USB 2.0 portssameCheck before you buy a compact server
Role"strongly recommends running the WinOMS database on a dedicated server"sameNo file server, print server or other software on the same box

Source: WinOMS 10.1.x System Requirements, pages 1 and 7; Tech Pack OL700-03, pages 8 and 9. Checked 26 October 2026.

Before you buy the WinOMS server

  • It will do one job: run the WinOMS database.
  • Windows Server 2022 or 2025, so it is not another 2016 problem in a year.
  • No plan to run WinOMS through Remote Desktop Services.
  • If it will be a virtual machine, the owner accepts in writing that WinOMS is "not certified for use on virtual machines".
  • A UPS "with shutdown software installed with the server machine", as the vendor recommends.
  • Wired network only.
  • Disk sized for 3 to 4 times the database during the conversion.

The vendor also says "all operating systems must be kept up to date". If you are planning the hardware, our dental server setup page covers what we look at, and UPS and safe server shutdown explains why the shutdown software matters.

Is Windows Server 2016 still OK for WinOMS?

For now, but not for long. The WinOMS 10.1.x requirements still list Windows Server 2016 as supported. Microsoft's Windows Server 2016 lifecycle page shows extended support ending on 12 January 2027, and the vendor asks for operating systems to be kept up to date. Plan the server replacement and the v10 conversion as one project. The other technology dates for the year are in the pillar guide's calendar.

What about the workstations and the monitor station?

Each WinOMS workstation needs a dual-core CPU, 4 GB of RAM, 40 GB of free disk, a 3D-accelerated video card and Microsoft Edge. Windows 11 Pro is recommended; Windows 10 Pro is still on the vendor's supported list.

Workstation itemRecommendedMinimum
WindowsWindows 11 ProfessionalWindows 10 Professional (supported)
CPU and RAMDual-core, 4 GBDual-core, 4 GB
Disk40 GB free40 GB free
Screen1440×900 or better (1920×1080 monitor recommended)1280×1024
NetworkEthernet 100/1000, wiredsame
Monitor stationDB9 serial port for the anesthesia vitals monitorsame

Source: WinOMS 10.1.x System Requirements, pages 1 and 2. Checked 26 October 2026.

Windows 10 Pro is on the vendor list, but Microsoft's Windows 10 lifecycle page shows support ended in October 2025. Both facts are true; plan the move with our guide to Windows 10 end of life for dental practices. The older Tech Pack says the v10.0 client "only runs on Windows 8.1 and Windows 10"; the current 10.1.x requirements replace that, so buy to the current document.

The monitor station needs the DB9 serial port, and the vendor says "Wireless networking is not recommended for Anesthesia." Cabling and network placement for that PC are in the guide to connecting the sedation monitor station. Vitals monitors are medical devices. Change nothing on the monitor itself without the manufacturer or your biomedical service.

SQL Server Express or Standard: which licence does your WinOMS database need?

It depends on the database size. The WinOMS Tech Pack says a database of 7.5 GB or smaller can use a SQL Server 2019 Express licence, 8.5 GB or larger prompts an upgrade to Standard, and 10 GB or larger requires Standard. Separately, Microsoft caps any Express database at 10 GB.

Keep the two kinds of number apart. The 7.5 GB and 8.5 GB figures are WinOMS licensing thresholds. The 10 GB figure is also Microsoft's hard limit for Express.

Your database sizeWhat WinOMS saysMicrosoft's Express limit
7.5 GB or smallerCan be assigned a SQL Server 2019 Express licenceWithin the 10 GB cap
8.5 GB or largerYou "will be prompted" to upgrade to SQL Server 2019 StandardApproaching the 10 GB cap
10 GB or larger"Microsoft SQL 2019 Standard is required"Over the Express maximum

Source: Tech Pack OL700-03, page 8; Microsoft, SQL Server 2019 editions. Checked 26 October 2026.

Microsoft's editions table also limits Express to the lesser of 1 socket or 4 cores and 1,410 MB of buffer-pool memory, and Express has no SQL Server Agent, the built-in job scheduler. That last point matters for backups: on an Express server, a scheduled WinOMS backup has to be started by a Windows scheduled task or your IT team's backup tool.

What happens if an Express database outgrows its limit? The Tech Pack's troubleshooting section describes it: "A message is displayed stating the database is too large for the current version of SQL when logging into WinOMS." The screenshot on that page (p.27) shows the dialog: "Your WinOMS database has reached its maximum size and requires an upgrade," and "You are unable to log into WinOMS at this time." Its resolution is to call WinOMS support. Find out where you stand before it happens.

To find your size, the System Requirements point to the vendor's v10 Readiness Check utility, which determines "whether your database is eligible for Microsoft SQL Express or Standard licenses." Your IT team runs it on the server, or you ask WinOMS support. SQL Server 2019 itself has extended support into January 2030, per Microsoft's SQL Server 2019 lifecycle page.

How long does the WinOMS v10 SQL conversion take, and what must happen first?

The vendor estimates about 1 hour per 10 GB of database for the conversion and server update, so a 40 GB database takes about 4 hours. That excludes workstation updates. You need free disk of at least 3 times the database size (3 to 4 times recommended), a SQL licence bought beforehand, and no WinOMS use during the window.

Worked example (use your own size):

StepExample: 25 GB database
Conversion and server update (1 hour per 10 GB)About 2.5 hours
Free disk needed on the server (3 to 4 times)75 to 100 GB
Workstation updatesExtra, after the server; they "can be run simultaneously"
Slack for problemsAdd it: the vendor documents a freeze at "Step 4 of 28" and a rollback to v9 as "a last resort option"

Source: Tech Pack OL700-03, pages 7, 8, 9 and the troubleshooting section. Checked 26 October 2026.

The documented failure and rollback path is the reason a conversion window needs a quiet evening or weekend, not a lunch hour. If you are also replacing the server, the vendor asks to keep the new server's name and IP address the same as the old one where possible. For the general order of a software cutover, see our dental PMS migration cutover plan.

What your IT technician does during the conversion window

  • Licensing: the MSSQL licence is bought and the activation code is to hand; the PWSvr licence folder is copied before anything is removed from an old server.
  • Backup first: the whole WinOMSCS folder, including the Sybase files mdsdb.db and mdsdb.log, is copied before starting.
  • Disk: free space of 3 to 4 times the database is confirmed.
  • Windows: no pending Windows Updates; .NET Framework 3.5 is confirmed on the server.
  • Security tools paused for the window only: the vendor lists real-time antivirus, real-time backups and firewalls among the pre-checks, plus the domain controller if one exists.
  • Access: everyone logged out; the technician signs in as admin and works at the server, because the vendor says "Do not use RDP to run any update."
  • Old server isolated: on a new-server move, the old WinOMS server is off the new server's network and its Sybase service is disabled.
  • Third-party check: every service you use is checked against the Tech Pack's list of services compatible with v10.
  • Pearl: if installed, its services are stopped in the vendor's order and restarted in reverse.

What gets switched back on afterwards

  • Real-time antivirus back on.
  • Firewalls back on, with the documented WinOMS exceptions.
  • Real-time backup back on.
  • First cstoolkit backup run and its log checked.
  • Users reset their passwords through the admin's Restore User Access step.
  • WinOMS registered within the seven days the vendor allows.
  • Every integration tested with a real record.
  • The old server retired, with no copy of the Sybase database left on the network.

These are your technician's steps, not a list for the front desk. Nobody in the practice should switch off security tools on their own.

What if you are on WinOMS Hosted?

The Carestream Dental Cloud team performs Hosted conversions and updates on weekends. The Tech Pack asks the office to offer "three (3) optional weekends" and warns that "The office will not be able to use WinOMS during the update and conversion process." Your IT work is the office side: workstations, printers, signature pads and card terminals checked against the Hosted requirements.

The pre-flight sheet

Print this and fill it in before you book the date.

ItemYour answer
Database size (Readiness Check or WinOMS support)___ GB
SQL licence: Express or Standard, bought on___
Free disk on the server (need 3 to 4 times the database)___ GB
Estimated server time (1 hour per 10 GB)___ hours
Third-party services checked against the v10 listyes / no
Conversion date and backup date___
Who switches security tools back on, and when___
First verified backup after the conversion___

How do you back up WinOMS properly?

Back up WinOMS with the database stopped, never live. The vendor says WinOMS "does not support live backups as it can interfere with auto-lock features." On v10 your IT team uses the cstoolkit/backup command, which writes mdsdb.bak into a dated folder and restarts the database. Back up the whole WinOMSCS folder daily and keep a copy off-site.

That instruction is from the WinOMS MSSQL Tech Pack (OL700-03, June 2024) and the 10.1.x System Requirements, checked 26 October 2026. Advice that stops at copying the WinOMSCS Data folder comes from the Sybase-era (v9) Tech Pack; on v10 the folder copy goes alongside the stopped-database mdsdb.bak, not instead of it.

The nightly routine your IT team schedules

  1. 1Everyone outAll users are logged out of WinOMS, as the vendor requires before a backup.
  2. 2Run the backupA scheduled task runs cstoolkit/backup with a backup path, for example d:\data\WOMSbak, with no quotes or double spaces in the path.
  3. 3Check the logbackup.log should show a line such as "BACKUP DATABASE successfully processed".
  4. 4Copy it off the serverThe dated folder and the whole WinOMSCS folder go to a second location.
  5. 5Keep one copy off-siteThe vendor suggests a nightly copy kept off-site; your IT team can do this with an encrypted off-site copy.
  6. 6Alert on failureIf the log is missing or shows an error, someone hears about it the next morning.

Monthly: book a test restore with WinOMS support onto a spare machine at a quiet time. The vendor warns that restoring the .bak file through SQL Server Management Studio "would not allow users to log in WinOMS" and asks offices to contact support for restores. So the test is vendor-assisted, never a do-it-yourself restore over the live database.

Quarterly: compare the size of mdsdb.bak with the SQL licence thresholds above, so an Express database never surprises you.

For the wider checklist, see our restorable dental backup checklist and our backup and disaster recovery service page. What to do if the server fails during a case is in the surgery-day downtime plan.

How much internet does WinOMS Hosted or Sensei Cloud need?

WinOMS Hosted needs 10 Mbps for 1 to 5 users, 20 Mbps for 6 to 10, 40 Mbps for 11 to 20 and more above that, with at least 2 Mbps per simultaneous user and latency of 50 ms or less. Sensei Cloud lists 10 Mbps down and 10 up as its minimum, with 25 down and 10 up recommended.

Users at one locationWinOMS Hosted (down/up)Sensei Cloud
1 to 510 Mbps10/10 Mbps minimum, 25/10 recommended
6 to 1020 Mbpsas above
11 to 2040 Mbpsas above
20 or more40+ Mbpsas above
Rule of thumbAt least 2 Mbps per simultaneous userNot stated per user
Latency50 ms or lessNot stated

Source: WinOMS 10.1.x Hosted System Requirements, page 2; Sensei Cloud System Requirements. Checked 26 October 2026.

The Sensei Cloud document lists its speeds under the workstation and does not say whether they are per computer or per office, so ask the vendor how they scale with users. The Hosted document also warns that "Sharing bandwidth with other internet-intensive services such as video streaming or VOIP could affect WinOMS Hosted performance," and suggests imaging users consider a faster service, both download and upload.

Worked example: eight simultaneous Hosted users (example; use your own numbers):

    1. The vendor's band for 6 to 10 users is 20 Mbps.
    1. The per-user rule gives 8 × 2 Mbps = 16 Mbps, so the 20 Mbps band is the larger figure.
    1. Add your phone system's needs and your imaging uploads. Get both numbers from your phone and imaging vendors; there is no standard figure.
    1. Choose a circuit comfortably above the total, and test that latency to the Hosted service stays at 50 ms or less at busy times.
    1. Add a second internet line so the office is not stuck on one connection. Our guide to when the office internet goes down covers the options.

How should satellite offices and remote surgeons reach WinOMS?

On-premises WinOMS is reached over the office network or a VPN, with firewall exceptions for mdcs.exe and SQLserver.exe. Remote Desktop Services is not supported. WinOMS Hosted is reached through Citrix Workspace from each site, with the same bandwidth rule per site. Sensei Cloud runs in a supported browser.

SetupHow a second site or a surgeon at home connectsWhat your IT team sets up
On-premises WinOMSOffice network or VPN to the serverVPN; firewall exceptions for mdcs.exe and SQLserver.exe; internal ports 1434 to 1436 for SQL
WinOMS HostedCitrix Workspace at each siteA circuit sized to the Hosted bands at every site; wired PCs
Sensei CloudChrome or Edge on Windows, Chrome on macOSInternet at each site to the Sensei Cloud figures; supported Windows

Source: WinOMS 10.1.x System Requirements, pages 1, 2 and 7; Tech Pack OL700-03, page 6; WinOMS 10.1.x Hosted System Requirements. Checked 26 October 2026.

What not to do:

    • publish Remote Desktop to the internet so someone can reach the server from home;
    • run WinOMS over Remote Desktop Services, which the vendor does not support;
    • put the anesthesia module on Wi-Fi.

How a multi-office group connects satellites and rotating surgeons is covered in the pillar guide. For groups of ten or more offices, see our DSO IT support page.

What to ask your IT provider about a WinOMS server or cloud move

Before you replace the server or move to the cloud, ask questions that show whether someone has read the vendor's documents. Each one below comes with what a good answer sounds like. For a general list, see our 20 questions to ask before signing with a dental IT provider.

To your IT provider

  1. How will you size the new server? A good answer: from the 10.1.x System Requirements, with disk for 3 to 4 times the database at conversion.
  2. Which Windows Server version will you install? A good answer: 2022 or 2025, not 2016.
  3. Have you run a Sybase to SQL Server conversion before? A good answer: yes, with the vendor's pre-checklist and time for the documented rollback path.
  4. What do you switch back on after the conversion? A good answer: antivirus, firewall, real-time backup and a first verified backup, named in writing.
  5. How do you back up WinOMS? A good answer: cstoolkit/backup with users logged out, the log checked, and a copy off-site.
  6. How do you test a restore? A good answer: with WinOMS support, onto a spare machine, never through SQL Server Management Studio onto the live server.
  7. How will remote staff connect? A good answer: VPN with the documented firewall exceptions, never Remote Desktop Services.
  8. If we go Hosted, what changes for you? A good answer: circuit sizing, a second line, wired PCs, and checks on printers and signature pads.

To the software vendor

  1. Is our database eligible for SQL Express or does it need Standard? A good answer: a figure from the Readiness Check.
  2. Do all our third-party services work with v10, Hosted or Sensei Cloud? A good answer: checked against the current compatibility list.
  3. How are our images moved if we change setup? A good answer: a written scope.
  4. Which of our vitals monitors are supported in the setup we are choosing? A good answer: model by model.
  5. What do you back up in Hosted or Sensei Cloud, and how do we get a copy? A good answer: a written description of the copy and how to request it.
  6. How do we export our data if we leave? A good answer: a format and a process.

The bottom line

Decide the software first. Then size the server and the SQL licence from the current documents, book the conversion with a switch-back-on plan, and prove the backup with a vendor-assisted test restore. If Windows Server 2016 runs your WinOMS today, 12 January 2027 sets the deadline.

Legend Networking has served over 3,500 practices since 2004 and holds a 4.8 rating from 173 Google reviews. Our oral surgery IT support covers the computers, network, server, backups and accounts around the software you run; the software vendor supports the application.

Questions

Frequently asked questions

What are the system requirements for WinOMS 10.1?

WinOMS 10.1 recommends a dedicated server with a quad-core CPU, 16 GB of RAM and 100 GB free disk on Windows Server 2025 or 2022; dual-core and 8 GB is the minimum, and Server 2019 or 2016 is supported. Workstations need dual-core, 4 GB, 40 GB and Windows 11 Pro recommended. Remote Desktop Services is not supported (WinOMS 10.1.x System Requirements, checked 26 October 2026).

What is WinOMS, and is it cloud-based?

Sensei describes WinOMS as "a server-based, oral surgery practice management system." It runs on a server in your office or as WinOMS Hosted, where Carestream Dental runs the server and your staff connect through Citrix Workspace. Sensei Cloud is a separate, browser-based product. Sensei's support page says migration to Sensei Cloud "is optional and can be planned over time."

Can WinOMS run on Windows Server 2016 after 12 January 2027?

The WinOMS 10.1.x requirements still list Windows Server 2016 as supported, checked on 26 October 2026. Microsoft's extended support for Windows Server 2016 ends on 12 January 2027, and the vendor asks for every operating system to be kept up to date. Plan the server replacement before that date, and combine it with the v10 conversion if you have not converted yet.

How long does the WinOMS v10 SQL conversion take?

The vendor estimates about 1 hour per 10 GB of database for the conversion and server update; a 40 GB database takes about 4 hours. Workstation updates are extra. The server needs free disk of at least 3 times the database size, with 3 to 4 times recommended, and nobody can use WinOMS during the conversion. Leave slack for the vendor's documented rollback steps.

Do I need SQL Server Standard for WinOMS v10?

Only if your database is large enough. The WinOMS Tech Pack says 7.5 GB or smaller can use a SQL Server 2019 Express licence, 8.5 GB or larger prompts an upgrade to Standard, and 10 GB or larger requires Standard. Microsoft caps Express at 10 GB and gives it no SQL Server Agent. The vendor's Readiness Check utility tells you which licence your database is eligible for.

Can I back up WinOMS while people are using it?

No. The vendor says WinOMS "does not support live backups," and all users must be logged out first. On v10, the cstoolkit/backup command creates mdsdb.bak in a dated folder and restarts the database afterwards. Back up the whole WinOMSCS folder daily, keep a copy off-site, and test restores with WinOMS support rather than through SQL Server Management Studio.

Can WinOMS run on a virtual server, over Remote Desktop, or from home?

The vendor says WinOMS "is not certified for use on virtual machines," though a practice may use one at its own risk, and Remote Desktop Services "is not a supported environment." Staff working from home reach on-premises WinOMS through a VPN with firewall exceptions for mdcs.exe and SQLserver.exe. WinOMS Hosted users connect through Citrix Workspace instead.

How much internet does WinOMS Hosted need?

The WinOMS 10.1.x Hosted requirements list 10 Mbps for 1 to 5 users, 20 Mbps for 6 to 10, 40 Mbps for 11 to 20 and more above that. Allocate at least 2 Mbps for each simultaneous user at a location, and keep latency at 50 ms or less. Phones and video on the same line can slow WinOMS Hosted down.

How do you get WinOMS support, and does it cover our network or backups?

Contact the software vendor through its WinOMS support page, which lists phone, email and chat. WinOMS support covers the application. The vendor's Tech Pack makes the local technician "fully responsible" for the office network, and says WinOMS support does not train offices on configuring backups or restoring a database. Your IT team covers those.

Do we still need a server in the office if WinOMS is hosted or we move to Sensei Cloud?

Usually you still need local equipment. Imaging capture, the monitor workstation, TWAIN scanners, signature pads and card terminals stay in the office with either option. The Hosted workstation is not meant for image acquisition, and Sensei Cloud uses locally installed CS Imaging 8 on Windows. Ask your imaging vendor whether you also need a local imaging server.

The bottom line

A server replacement, a v10 conversion or a move to Hosted is the moment to check the server, disk, internet, backups and security around WinOMS. You are welcome to request a Free Dental IT Assessment: written findings and prioritized recommendations on your computers, software, network security, backups and performance. Or call our helpdesk, staffed 24/7 at 1-800-794-1588, and ask for a review of your WinOMS server plans.

Ian Lynch
About the author

Ian Lynch

Operations Lead, 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

    Dental IT help desk Mon–Sat; emergency line always on

  • 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 Free Dental IT Assessment before you replace the WinOMS server

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

Or call 800-794-1588

Free IT assessment

Tell us what you are running

Your information is secure and will never be shared.