QuickBooks Desktop Multi-User on a VPS: Setup and Hosting Costs

QuickBooks Desktop multi-user can be configured on Windows Server, but a self-managed VPS has an important support limitation: Intuit currently lists virtual servers and virtual machines as a network type it does not recommend for QuickBooks Desktop. Intuit’s current Enterprise technical specifications list Windows Server 2016, 2019, and 2022, while its authorized hosting program provides the supported third-party hosting path.

Raff provides Windows VM infrastructure, not Intuit-authorized QuickBooks hosting. This guide is therefore for technical evaluation, existing customer-managed environments, and administrators who understand that a successful lab setup does not change Intuit’s support policy.

In short

For an Intuit-supported hosted QuickBooks Desktop deployment, use an Intuit-authorized hosting provider. If you are evaluating a customer-managed Windows Server environment, QuickBooks Desktop Enterprise is the clearest fit for Terminal Services, Windows Server 2022 is the newest server version currently listed by Intuit, and multi-user operation depends on QBDSM, file permissions, RDS licensing, backups, and real multi-user testing.

Intuit support policy is the first decision

Before configuring QuickBooks on a VPS, separate three questions:

This distinction matters more than whether the installer opens successfully.

A customer-managed Raff VM may be technically useful for testing or for teams that knowingly accept the vendor-support boundary, but it should not be presented as an Intuit-supported QuickBooks hosting service.

If vendor support is mandatory for production accounting, use an Intuit-authorized host or evaluate QuickBooks Online / Intuit’s hosted offering.

The deployment model should stay simple

For a small team evaluating this architecture, the practical model is:

Remote users
  ↓
RDP / RDS Session Host
  ↓
Windows Server
  ├── QuickBooks Desktop
  ├── QuickBooks Database Server Manager
  ├── Company file folder
  ├── Windows permissions
  └── Backup copies

When users work inside the same Windows Server session host, the QuickBooks application and company file remain close to each other. Avoid opening a live .QBW file across an internet VPN or other long-distance file path; Intuit’s network guidance does not recommend WAN, VPN, FTP, NAS, or virtual-server patterns as substitutes for a supported local network/hosting design.

QuickBooks Desktop Enterprise is the safer Desktop choice

For a new multi-user Desktop evaluation, QuickBooks Desktop Enterprise is the clearest product to assess because Intuit’s current guidance explicitly covers Enterprise technical specifications and provides Terminal Services troubleshooting support for Enterprise.

Do not assume every QuickBooks Desktop edition, release, add-on, payroll feature, printer workflow, or third-party integration behaves the same way. Before production, verify:

• the exact QuickBooks Desktop edition and year;
• active licensing and subscription status;
• Intuit support eligibility;
• Windows Server version;
• RDS / Terminal Services use;
• Office and Outlook integrations;
• payroll and bank-feed requirements;
• third-party add-ons;
• printer and PDF workflows;
• backup and restore process.

Windows Server 2022 is the newest version Intuit currently lists

Intuit’s current QuickBooks Desktop Enterprise technical specifications list:

• Windows Server 2016;
• Windows Server 2019;
• Windows Server 2022.

Windows Server 2025 is not currently listed on that technical-specification page.

For a customer-managed evaluation, Windows Server 2022 is therefore the newest listed server version. This does not remove the separate Intuit limitation around virtual servers/VMs.

The two checks are independent:

Server version compatibility
+
Hosting / virtualization support policy

Both should be acceptable for your production support model.

Sizing should follow concurrent users and workload

Intuit’s current Enterprise technical specifications provide this server RAM guidance for multi-user support:

Treat those numbers as vendor minimum guidance, not a full VPS sizing formula. An RDS Session Host also needs memory for Windows, each desktop session, antivirus/EDR, printing, browser tabs, Office apps, backup jobs, and any other business software.

A practical planning range is:

These are planning ranges, not performance guarantees. Size from peak concurrent users and the complete desktop workload.

For broader Windows sizing, see Windows VPS Sizing for Remote Users.

Step 1 — Install QuickBooks Desktop

Download QuickBooks Desktop from your Intuit account or the official installer source and run it as Administrator.

For an RDP-based lab where users will work inside the server, install the QuickBooks application on the server rather than treating the VM only as a remote file share.

After installation, reboot if required and confirm that QuickBooks opens normally before enabling multi-user hosting.

Step 2 — Enable Host Multi-User Access

Open QuickBooks Desktop and go to:

File
  → Utilities
  → Host Multi-User Access

Confirm the prompt.

QuickBooks 2024 uses the QuickBooksDB34 database service. Intuit documents version-specific service names, so check the actual service on your system instead of assuming the number.

Get-Service | Where-Object {
    $_.Name -like "QuickBooksDB*" -or $_.Name -like "*QB*"
} | Format-Table Name, Status, StartType -AutoSize

If this is a dedicated test server and the correct database service is not configured to start automatically, review the service configuration before relying on multi-user access after reboot.

Step 3 — Document the hosting components

Multi-user mode involves more than the QuickBooks menu setting. Document:

• QuickBooks version;
• QuickBooks database service name;
• company-file folder;
• QBDSM scan status;
• .ND network descriptor files;
• dynamic port shown by QBDSM;
• Windows Firewall rules;
• NTFS permissions;
• Windows users;
• QuickBooks internal users;
• backup location.

This makes troubleshooting much faster than changing firewall ports or permissions at random.

Step 4 — Check QuickBooks Database Server Manager

Open QuickBooks Database Server Manager and review the Port Monitor tab.

Use the port shown by your installation. Do not copy a port from an old forum post or another QuickBooks release.

If troubleshooting connectivity, first confirm:

Get-Service | Where-Object {$_.Name -like "QuickBooksDB*"}

Then review QuickBooks-created firewall rules and the QBDSM port shown on the server.

Step 5 — Create a dedicated company-file folder

Use a clear folder rather than storing live company files under Desktop, Downloads, or a personal profile.

Example:

New-Item -ItemType Directory -Path "C:\QuickBooksCompanyFiles" -Force

Keep live .QBW files, backup files, and user downloads logically separated.

Step 6 — Scan the company-file folder with QBDSM

In QuickBooks Database Server Manager, open Scan Folders.

Add the folder and start the scan.

A successful scan prepares the folder for multi-user access and can create/update the .ND network descriptor next to the company file.

Check for .ND files with:

Get-ChildItem "C:\QuickBooksCompanyFiles" -Filter "*.ND"

Do not publish .ND file contents without reviewing them for hostnames or IP information.

Step 7 — Configure Windows file permissions deliberately

Intuit’s multi-user hosting documentation states that the Windows user accessing the company file needs appropriate Windows file permissions and describes Full control as part of the standard requirements for company-file access.

Do not grant Full Control to Everyone or make accounting users local administrators. Use a dedicated group instead.

Example group model:

QB-Users
QB-Admins

Then grant the required company-folder access only to the group that needs it. If your security policy uses tighter permissions than Intuit’s documented model, treat that as a tested exception and validate multi-user operation carefully.

Review shares with:

Get-SmbShare

and, when applicable:

Get-SmbShareAccess -Name "QuickBooksCompanyFiles"

For users working through RDS on the same server, do not expose SMB to the public internet.

Step 8 — Give each person a separate Windows account

Avoid shared Windows credentials.

Example local-user creation:

$password = Read-Host "Password for new user" -AsSecureString
New-LocalUser -Name "jane.doe" -Password $password -FullName "Jane Doe"

For RDS users, access should be granted through the appropriate Remote Desktop / RDS security groups rather than by making users administrators.

A production environment should also have a documented process to disable access promptly when a user leaves the organization.

Step 9 — Create separate QuickBooks users

Windows users and QuickBooks users are different identities.

Inside QuickBooks, create a separate QuickBooks account for each person and assign only the role needed for their accounting work.

The clean audit model is:

One Windows identity
+
One QuickBooks identity

Avoid shared QuickBooks administrator credentials.

Step 10 — License RDS separately from QuickBooks

The built-in Windows Server administrative RDP sessions are for server administration, not for a team using QuickBooks as a daily shared desktop.

For daily multi-user desktop access, deploy Remote Desktop Services correctly and plan RDS CALs.

Microsoft’s current licensing guidance says each user or device connecting to an RD Session Host running Windows Server needs an RDS CAL. It also makes an important distinction:

• Domain-joined RDS deployments: Per User or Per Device CALs can be used.
• Workgroup RDS deployments: Microsoft requires Per Device CALs; Per User CALs are not permitted in that configuration.

This is separate from QuickBooks licensing.

QuickBooks license / seat
≠
Microsoft RDS CAL

For the full access-model explanation, read Multi-User RDP: 2 Admin Sessions vs RDS Session Host and RDS CAL Licensing on Windows Server.

Step 11 — Test with real non-admin users

Do not validate the deployment only as Administrator.

A useful test sequence is:

1. User A signs in through the intended RDP/RDS path.
2. User A opens QuickBooks and the company file.
3. User B signs in separately.
4. User B opens the same company file.
5. Both users perform safe test actions.
6. Confirm reports, printing, and PDF export if those workflows matter.
7. Close and reopen sessions.
8. Reboot the server and repeat the connection test.

If a workflow fails, record the exact error, user, time, file path, QBDSM service state, and whether the issue affects one user or everyone.

Step 12 — Use layered backups

A QuickBooks deployment should have more than one recovery layer.

QuickBooks-aware backups

Use QuickBooks’ own backup workflow where appropriate so the company file has an application-level recovery path.

Server-level backups

Use VM-level backup or snapshot capability for server recovery and before high-risk changes such as Windows updates, QuickBooks upgrades, RDS changes, or major permission changes.

Off-server copies

Keep recovery copies outside the live VM. A backup stored only on the same server does not protect against deletion, ransomware, or VM loss.

Most importantly, test a restore. A successful backup job is not the same as a proven recovery process.

Common QuickBooks multi-user failures have predictable causes

H202 usually points to hosting or connectivity

Check:

• QuickBooks database service state;
• QBDSM folder scan;
• .ND file;
• Windows Firewall rules;
• company-file path;
• permissions.

Get-Service | Where-Object {$_.Name -like "QuickBooksDB*"}

Users can open QuickBooks but not the company file

Review both Windows file permissions and QuickBooks internal user permissions. Confirm the affected user is opening the intended company file and is not relying on an obsolete shortcut.

The setup works until reboot

Verify the QuickBooks database service and any required RDS components return to the expected state after restart.

A damaged company file is not a QBDSM problem

Do not keep changing firewall rules if the file itself is damaged. Restore a known-good QuickBooks backup or use Intuit’s supported repair/support path.

Security controls should protect the accounting system

A QuickBooks company file contains sensitive business and financial data. Treat the server as a production accounting system if real data is present.

Use these controls:

• individual Windows accounts;
• least-privilege administration;
• no public SMB exposure;
• Windows Firewall enabled;
• secure RDP/RDS access;
• Windows updates;
• endpoint protection;
• protected backups;
• access review when staff change;
• logging and monitoring;
• restore testing.

Do not disable antivirus entirely to solve a QuickBooks problem. If vendor-documented exclusions are required, apply only the specific exclusions needed and review them with your security policy.

Raff’s role is the Windows VM infrastructure layer

Raff provides the Windows VM, remote administration path, storage, backup/snapshot options, and VM controls. Raff does not provide an Intuit-authorized QuickBooks hosting service, QuickBooks licensing, company-file repair, or Intuit application support.

That means the buyer decision is straightforward:

The infrastructure can be technically capable while the software vendor still limits support for virtual-server deployments. Both facts can be true at the same time.

What QuickBooks hosting costs in 2026

The two paths price completely differently, and both sit on top of your own QuickBooks licence.

Intuit-authorized hosting is priced per user per month. Published rates checked in August 2026 ranged from about $12 per user at the entry end (Apps4Rent) to roughly $95 to $120 per month at the fuller-service end (Ace Cloud Hosting's 2026 pricing guide). That price buys an Intuit-supported environment where the provider manages the hosting layer.

A customer-managed Windows VM is a flat infrastructure price regardless of user count. A five-user environment on Raff sized to the table above runs about $125/month total: 8 vCPU / 16 GB compute at $70.49, the $15.00 Windows Server licence, and five RDS User SALs at $8.00 each.

The trade is exactly what this article describes: the per-user price includes Intuit-supported hosting and management; the flat price buys infrastructure only, with the vendor-support boundary from the sections above. If production accounting needs Intuit support, the authorized path is the safe answer. The math matters when a team knowingly runs customer-managed and wants to see what each model actually costs.

Lab verification scope

The original screenshots in this article were captured during an April 2026 Raff Windows Server 2022 lab using QuickBooks Desktop Enterprise 2024 trial software. That lab verified installation, Host Multi-User Access, QBDSM service registration, Port Monitor, folder scanning, .ND generation, and company-folder hosting behavior.

Those screenshots are retained as first-hand evidence of that specific lab. They are not a claim that Intuit supports QuickBooks Desktop on Raff VMs, and they are not a fresh August 2026 certification of every QuickBooks version, RDS design, add-on, or production workflow.

Production checklist

Before using real accounting data, confirm:

• Intuit licensing and support path accepted;
• exact QuickBooks edition/version documented;
• Windows Server version verified against current Intuit requirements;
• virtualization support limitation understood;
• RDS model and CAL licensing confirmed;
• QBDSM service running;
• company folder scanned;
• Windows permissions reviewed;
• separate Windows and QuickBooks users created;
• SMB not exposed publicly;
• two-user workflow tested;
• printing/PDF/add-ons tested where needed;
• backups configured;
• off-server copy available;
• restore test completed;
• support/runbook documented.

Next steps

• Windows VPS Sizing for Remote Users
• Multi-User RDP: 2 Admin Sessions vs RDS Session Host
• RDS CAL Licensing on Windows Server
• RDP Performance Tuning for Smooth Remote Desktop
• Windows Server Version Comparison
• ERP on Windows VPS
• Raff Windows VM
• Raff Pricing

Sources

• Intuit — QuickBooks Desktop Enterprise technical specifications
• Intuit — Recommended networks for QuickBooks
• Intuit — Host company data in multi-user mode
• Intuit — Hosting providers authorized by Intuit
• Microsoft Learn — License Remote Desktop Services with CALs
• Microsoft Learn — License Remote Desktop session hosts
• Sources verified: 2026-08-08

QuickBooks, QuickBooks Desktop, QuickBooks Enterprise, and Intuit are trademarks of Intuit Inc. Raff is not affiliated with or endorsed by Intuit and is not an Intuit Authorized Hosting Provider. This article is independent technical documentation for customer-managed Windows Server infrastructure.