Why host QuickBooks on an RDP server

QuickBooks Desktop was designed for an office: one company file, on one computer, with everyone walking up to it. Modern businesses don't work that way anymore — the owner is traveling, the bookkeeper works from home, and the CPA is in another city. RDP for QuickBooks recreates that office computer in the cloud: the company file lives on an always-on Windows server, and everyone who needs it logs into the same desktop from wherever they are.

The alternative most small businesses stumble into is emailing backup files back and forth. It works until it doesn't — until someone edits an old copy, until two people make changes to two different files, until nobody knows which backup is current. A hosted company file ends that entirely: there is one file, in one place, and everyone opens the same one.

There's a cost angle too. Official QuickBooks cloud hosting through authorized providers typically costs per user per month and adds up fast for a small team. Hosting it yourself on an RDP server you control is dramatically cheaper — a single server plan covers the whole team — while giving you full admin access to install updates, manage users, and control backups on your own schedule.

QuickBooks one company file Hosted company file (RDP) Owner Bookkeeper CPA One file, one truth, three locations
Fig. 1 — Everyone opens the same company file on the hosted server — no emailed backups, no version confusion.

How QuickBooks on RDP actually works

The setup is straightforward: you rent a Windows RDP server, install QuickBooks Desktop on it (using your own valid license), and place your company file (.QBW) on the server's disk. Each person who needs access gets their own Windows user account on the server and connects with the Remote Desktop client from their own computer. Inside their session, they open QuickBooks exactly as if it were installed locally.

QuickBooks doesn't know — or care — that it's on a remote server. Multi-user mode works the same way it does on an office network: one user hosts the company file, others join it. The difference is that the "office network" is now the server itself, which is always on, so nobody's access depends on someone else's computer being awake.

A practical note on licensing: you need a legitimate QuickBooks Desktop license for the server, and Intuit's licensing terms govern how many users can access it. The RDP server is just the computer it runs on — it doesn't change what Intuit requires. Buy or transfer your license properly; the savings come from the hosting, not from skipping licenses.

Setting up QuickBooks on RDP: the working sequence

Follow these steps in order — skipping ahead is how people end up with a company file nobody can open:

  1. Provision the server and change the password. Sign up, note the IP and credentials from the welcome email, connect once, and immediately change the administrator password (Ctrl+Alt+End → Change a password).
  2. Create one Windows user per person. Don't share a single login. In Computer Management → Local Users and Groups, create an account for the owner, the bookkeeper, and the CPA, and add each to the Remote Desktop Users group. Individual accounts mean individual accountability.
  3. Install QuickBooks Desktop with your license. Log in as administrator, install your licensed copy of QuickBooks Desktop, and apply all updates before anyone touches the company file.
  4. Move the company file to the server. Copy your .QBW file (and its .TLG transaction log) to a dedicated folder like C:\QBData\. Open it once as admin to verify it opens cleanly and the data is current.
  5. Enable multi-user hosting on the server. In QuickBooks, go to File → Switch to Multi-user Mode on the hosting session, and make sure the QuickBooks Database Server Manager is installed and scanning the company-file folder.
  6. Set QuickBooks user permissions. Inside QuickBooks (Company → Users → Set Up Users and Roles), create a QuickBooks user for each person with appropriate roles — the bookkeeper gets full access, the CPA gets the accountant role, and so on.
  7. Test each person's access. Have every user connect with their own credentials, open QuickBooks, and open the company file in multi-user mode. Confirm two people can be in the file simultaneously before you call it done.
  8. Schedule the first backup immediately. Before the first real workday, set up the backup routine described below. A hosted company file without backups is a disaster waiting for a date.

Important: Keep a local copy of your most recent verified backup somewhere off the server — an external drive or cloud storage. The server is reliable, but your books are the business: they should exist in two places, always.

Multi-user mode: you, your bookkeeper, your CPA

Multi-user mode is where hosted QuickBooks earns its keep. The owner can be reviewing reports while the bookkeeper enters bills while the CPA pulls trial balances for tax season — all in the same live file. No "send me the latest backup," no waiting for someone to close the file so you can open it.

A few realities to plan around. QuickBooks locks individual records while someone edits them, so two people can't edit the same invoice simultaneously — but they can work in different parts of the file without conflict. Performance depends on the company file size and the server's resources; a file that has grown for ten years with hundreds of thousands of transactions wants more RAM than a new business's file. And everyone should develop the habit of closing QuickBooks (not just disconnecting) when they're done for the day, so locked records release cleanly.

Tax season deserves special mention: this is when hosted QuickBooks shines brightest. Instead of mailing a backup to your CPA and losing access for two weeks, your accountant logs in, does their work in a copy or in the live file (agree on the workflow in advance), and you keep working. Many firms now expect clients to offer remote access exactly like this.

Daily Auto backup On the server, every night Weekly Verified copy Open it, check it, copy off-server Monthly Archive Month-end snapshot, kept long-term The 3-tier backup routine for hosted books
Fig. 2 — Three backup tiers: automatic daily, verified weekly off-server, and monthly archives.

A backup routine that actually protects you

Most businesses "have backups" in the same way most people "have a will" — theoretically. For financial data on a hosted server, make it concrete with three tiers:

  • Daily automatic backup on the server. Use QuickBooks' scheduled backup (File → Create Backup → Schedule) to write a verified backup to a folder on the server every night. This protects against file corruption and bad edits.
  • Weekly verified copy off the server. Once a week, copy the latest backup to cloud storage or download it locally — and actually open it to confirm it's valid. An untested backup is a hope, not a backup.
  • Monthly archive. After month-end close, keep a snapshot labeled by month. If a problem is discovered quarters later (it happens), you'll be glad the history exists.

Also decide who owns backups. Name one person responsible for checking that the weekly copy happened. "Everyone assumed someone else did it" is the most common cause of backup failure in small businesses.

Security for financial data on a remote server

Financial data deserves more care than a typical RDP workload. Start with the basics done properly: strong unique passwords for every Windows account, no shared logins, Windows updated regularly, and the RDP port not left exposed to the entire internet without reason — consider restricting it or changing it (see our guide on how to change the RDP port).

Inside QuickBooks, use its own user roles to enforce least privilege: the bookkeeper doesn't need the admin role, and former employees' accounts get disabled the day they leave — both the Windows account and the QuickBooks user. Review the user list quarterly; stale accounts are a classic audit finding.

For the truly cautious, add a VPN in front of RDP so the remote desktop port isn't directly reachable at all — users connect to the VPN first, then to the server. Our secure RDP with VPN guide walks through the concept. And remember the compliance angle: if you handle client financial data, your industry may have specific requirements (encryption, access logs, retention) — the server gives you the control to meet them, but the responsibility is yours to configure.

Sizing the server for your company file

QuickBooks Desktop is not a heavy application by modern standards, but company files grow, and multi-user access multiplies the load. Use this as a starting guide:

Your situationWhat to expectSensible starting point
New business, 1–2 usersSmall file, light concurrent useShared plan — plenty for getting started
Established business, 2–4 usersLarger file, daily multi-user accessVirtual plan — the featured tier, comfortable headroom
Many years of data, 5+ usersLarge file, heavy simultaneous useDedicated plan — full resources for peak periods like month-end

All RDP Temple plans — Shared $6/month, Virtual $28/month (featured), Dedicated $165/month — include a dedicated IP, full admin RDP, 24/7 support, and a 3-day money-back guarantee, so you can test QuickBooks performance on a plan before committing. Details are on the plans page.

RDP for QuickBooks: FAQ

Yes. Install your licensed copy of QuickBooks Desktop on the Windows server with full admin access, place the company file on the server's disk, and each user connects via Remote Desktop. QuickBooks runs exactly as it does on a local office computer, including multi-user mode.

Technically, as many Windows user accounts as the server's resources support — but two limits apply: your QuickBooks license's user terms (set by Intuit) and the server's RAM/CPU. For 1–2 users a Shared plan works; 2–4 users fit a Virtual plan; 5+ simultaneous users or very large files want Dedicated.

It depends on what you need. Self-hosting on RDP keeps the full QuickBooks Desktop feature set (which Online doesn't fully match), costs less per month for a team, and gives you control over data and backups. QuickBooks Online wins on zero-maintenance simplicity. Businesses deeply invested in Desktop features usually prefer hosting.

Use three tiers: QuickBooks' scheduled backup writing a verified backup to the server nightly, a weekly copy moved off the server (and actually opened to confirm it's valid), and a monthly archive after close. Name one person responsible for verifying the weekly copy happened.

Yes — that's one of the main benefits. Create a Windows account and a QuickBooks user (with the accountant role) for your CPA, and they log in from their own office. Agree in advance whether they'll work in the live file or a copy, so nobody's surprised.

It's as safe as you configure it to be: strong unique passwords per user, no shared logins, Windows kept updated, RDP access restricted (port change or VPN in front), and off-server backups. The server gives you full control — which means security is your responsibility to set up, not something that happens automatically.

Ready for your own RDP server?

Full admin access, dedicated IP, 24/7 support and a 3-day money-back guarantee on every plan. Pay by credit/debit card, bank transfer, Bitcoin or altcoins.

Shared Servers$6/mo
Dedicated Server$165/mo
Get Started

3-day money-back guarantee · Instant setup · 30+ server locations · 99% uptime SLA