Self-Host QuickBooks Desktop Multi-User on a Windows Server VPS (2026 Guide)

QuickBooks Desktop multi-user mode on a Windows Server VPS can work well for small accounting teams, but it must be treated as a customer-managed self-hosted setup, not as managed QuickBooks hosting.

The clean workflow is:

Choose a supported Windows Server version
Install QuickBooks Desktop
Enable Host Multi-User Access
Open QuickBooks Database Server Manager
Scan the company file folder
Verify the .ND file and QBDSM service
Create Windows users
Grant folder permissions
Plan RDS CALs
Test with real QuickBooks users
Back up the company file

The most important detail:

Installing QuickBooks is not enough. You must enable multi-user hosting and scan the company file folder with QuickBooks Database Server Manager.

Raff provides the Windows VPS infrastructure layer. You bring your own QuickBooks Desktop license, manage the QuickBooks application, configure users, and remain responsible for Intuit licensing, application support, backups, and data integrity.

Important support and licensing note

Before using QuickBooks Desktop on any VPS, verify your QuickBooks license terms, Intuit support status, and hosting requirements.

Intuit's QuickBooks Desktop 2024 system requirements list supported Windows Server versions such as Windows Server 2022, 2019, and 2016. The same page also says QuickBooks requires Windows to be used natively and that virtual environments are not supported.

That means a VPS deployment should be positioned carefully:

This is a self-managed Windows Server deployment.
Raff is not an Intuit Authorized Hosting Provider.
Raff does not resell QuickBooks licenses.
Raff does not provide QuickBooks application support.

If you need Intuit-authorized commercial QuickBooks hosting, use Intuit's authorized hosting program or an Intuit-authorized provider.

If you choose a self-managed Raff Windows VPS, treat it like a Windows Server you control: install your licensed software, manage your company files, configure security, and test your QuickBooks workflow before production use.

Quick verdict

Simple rule:

QuickBooks license = right to use QuickBooks.
RDS CAL = right to connect to an RDS Session Host.
Windows VPS = infrastructure.
Backups = your recovery path.

How Raff fits QuickBooks self-hosting

Raff gives you a Windows Server VPS with Administrator access, RDP access, NVMe storage, and control over what you install.

That can be useful for teams that want:

• remote access to a Windows Server;
• customer-controlled infrastructure;
• QuickBooks Desktop installed on a centralized server;
• RDP-based access for accounting users;
• self-managed backups and permissions;
• a simpler alternative to running QuickBooks on an office PC.

But Raff is not a managed QuickBooks host.

Raff does not:

• sell QuickBooks licenses;
• activate QuickBooks for you;
• provide Intuit support;
• repair corrupted company files;
• act as an Intuit Authorized Hosting Provider;
• replace your accountant, QuickBooks admin, or Intuit support channel.

This article explains the Windows Server infrastructure setup.

You are responsible for confirming QuickBooks licensing, vendor support, and production suitability.

Who this guide is for

This guide is for:

• accounting firms using QuickBooks Desktop;
• SMBs that already depend on QuickBooks Desktop;
• MSPs helping clients centralize Windows business apps;
• teams moving QuickBooks from an office server to a cloud Windows VPS;
• QuickBooks Desktop Enterprise users who want remote RDP access;
• technical admins who understand RDS, backups, and Windows permissions.

This guide is not for:

• users who want fully managed QuickBooks hosting;
• teams that want Intuit to support the hosting environment end to end;
• users who do not have a valid QuickBooks Desktop license;
• buyers who should be on QuickBooks Online instead;
• teams that cannot manage backups or server security.

What you will build

The target setup looks like this:

Remote users
  ↓
RDP / RDS Session Host
  ↓
Windows Server VPS
  ├── QuickBooks Desktop installed
  ├── QuickBooks Database Server Manager
  ├── Company file folder
  ├── SMB share
  ├── .ND network descriptor file
  ├── Windows users and permissions
  └── Backups / snapshots

For most small deployments, all users RDP into the same Windows Server and open the company file locally on that server.

That is different from having QuickBooks client software on remote desktops connecting across the internet to a database server. For a VPS-based accounting workflow, RDP is usually simpler and safer.

What you'll need

Prepare:

• a Raff Windows VPS or similar Windows Server VPS;
• Windows Server version supported by your QuickBooks version;
• local Administrator access over RDP;
• valid QuickBooks Desktop license;
• QuickBooks installer from Intuit or your product account;
• company file backup;
• RDS CAL planning if multiple users connect;
• Windows user accounts for staff;
• folder permission plan;
• backup and restore plan;
• 60-90 minutes for first setup and testing.

Windows Server version: usually choose 2022

For QuickBooks Desktop 2024, Intuit lists Windows Server 2022, Windows Server 2019, and Windows Server 2016 as supported database server operating systems.

Windows Server 2025 is not listed on that QuickBooks Desktop 2024 system requirements page.

So the practical recommendation is:

Use Windows Server 2022 unless Intuit documentation for your QuickBooks version confirms a newer Windows Server version.

This is important because QuickBooks is not a generic app.

Accounting software depends on:

• database service behavior;
• Windows file permissions;
• SMB sharing;
• printer behavior;
• PDF tools;
• Outlook/Office integration;
• payroll/bank feed support;
• Intuit updates;
• vendor support.

Do not choose Windows Server 2025 just because it is newer.

Choose the newest Windows Server version your QuickBooks version actually supports.

QuickBooks Desktop product direction

QuickBooks Desktop is no longer the default path for every new business.

For many new businesses, Intuit pushes users toward QuickBooks Online. QuickBooks Desktop Enterprise remains the Desktop product line for businesses that need the Desktop model.

Before setting up QuickBooks Desktop on a Windows VPS, ask:

• Are we already committed to QuickBooks Desktop?
• Do we need Desktop-specific features?
• Do we need Enterprise?
• Are users trained on Desktop?
• Are add-ons compatible with Desktop?
• Do we need an authorized hosting provider?
• Would QuickBooks Online be simpler?
• How long do we plan to stay on Desktop?

A VPS deployment makes sense when Desktop is still the right product for the business.

It should not be used to avoid evaluating the future product path.

Sizing the Windows VPS

QuickBooks Desktop multi-user performance depends heavily on RAM, storage, and how users connect.

Intuit's QuickBooks Desktop 2024 requirements list server RAM guidance for multi-user environments:

For a Windows VPS, use this as a minimum planning baseline.

A practical sizing guide:

Do not size only by user count.

Also consider:

• company file size;
• report frequency;
• number of open apps per RDP session;
• Microsoft 365 Apps or Outlook on the same server;
• antivirus/EDR overhead;
• printers and PDF tools;
• backups;
• whether users leave sessions open all day.

Storage should be SSD/NVMe.

QuickBooks company files are sensitive to disk performance, and slow storage creates a poor experience for everyone.

Step 1 — Install QuickBooks Desktop

Download the installer from Intuit or your QuickBooks product portal.

Run it on the Windows Server VPS as Administrator.

Follow the normal QuickBooks installer flow:

1. Accept the license agreement.
2. Choose the install type recommended for your deployment.
3. Use the default install path unless you have a reason to change it.
4. Finish installation.
5. Reboot if prompted.

For an RDP-based self-hosted setup, install QuickBooks on the server where users will sign in.

After installation, you may see several QuickBooks-related services, but the multi-user database service may not be fully ready until hosting is enabled.

Do not stop here.

Step 2 — Enable Host Multi-User Access

This is the step many deployments miss.

Open QuickBooks Desktop on the server.

Then:

File
  → Utilities
  → Host Multi-User Access

QuickBooks displays a confirmation prompt.

Click Yes.

QuickBooks then enables hosting and prepares QuickBooks Database Server Manager for multi-user access.

You may see a second confirmation that the folder still needs to be scanned with Database Server Manager.

Click OK.

Then verify QuickBooks services:

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

You should see the QuickBooks database service for your version.

For QuickBooks Desktop 2024, the service name may be:

QuickBooksDB34

The number changes by QuickBooks year.

If you use a different QuickBooks version, do not hardcode QuickBooksDB34.

Check the real service name on your server.

For a dedicated QuickBooks server, set the database service to start automatically:

Set-Service -Name "QuickBooksDB34" -StartupType Automatic

Replace QuickBooksDB34 with your actual service name if different.

Step 3 — Understand what hosting changes

When Host Multi-User Access is enabled, QuickBooks may change several things:

• starts or registers QuickBooks Database Server Manager;
• enables database service access;
• creates or updates firewall rules;
• prepares QuickBooks to host company files;
• allows company files to be scanned;
• can create or update Windows file sharing;
• creates .ND files during scanning.

Important:

Multi-user mode is not only an app setting.
It also involves Windows services, firewall rules, SMB sharing, and file permissions.

For audits, document:

• company file folder path;
• SMB share name;
• NTFS permissions;
• QuickBooks database service name;
• dynamic port shown in Port Monitor;
• firewall rules;
• backup path;
• users with access.

Step 4 — Open QuickBooks Database Server Manager

Open QuickBooks Database Server Manager from the Start menu.

Go to the Port Monitor tab.

Use this screen to identify the port QuickBooks is actually using.

Do not rely blindly on old blog posts or static port ranges.

QuickBooks versions can use version-specific or dynamically assigned ports.

Your server may not use the same port as another guide.

Document the port from your own QBDSM Port Monitor.

If needed, use the Renew option in QBDSM to regenerate the port.

Step 5 — Create a company file folder

Create a dedicated folder for company files.

Recommended:

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

Store .QBW files there.

Avoid scattering company files across:

• Desktop;
• Downloads;
• user profile folders;
• random shared folders;
• temporary paths.

A clear folder path makes permissions, backups, scans, and support much easier.

Step 6 — Scan the company file folder

In QuickBooks Database Server Manager, go to the Scan Folders tab.

Then:

1. Click Browse.
2. Select:

C:\QuickBooksCompanyFiles

3. Click OK.
4. Click Start Scan.

QBDSM scans the folder and prepares company files for multi-user access.

A successful scan may show network diagnostics repair status.

After scan, QuickBooks should create an .ND file next to each .QBW company file.

Example:

YourCompany.QBW
YourCompany.QBW.ND

Check it:

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

You can inspect the file:

Get-Content "C:\QuickBooksCompanyFiles\YourCompany.QBW.ND"

Look for:

ServerMode=1

That confirms the file is marked for multi-user server mode.

Do not share .ND files publicly without removing server IP or hostname details.

Step 7 — Review SMB sharing and permissions

QBDSM may create or update a Windows SMB share for the company file folder.

Check shares:

Get-SmbShare

Check share permissions:

Get-SmbShareAccess -Name "QuickBooksCompanyFiles"

If your share has a different name, use that name.

For most RDP-based deployments where users sign into the same server, you can keep access narrow.

The safest model:

• only QuickBooks users can access the folder;
• only admins can change permissions;
• users are not local administrators;
• backups run with a dedicated admin/service account;
• SMB is not exposed publicly;
• company files are not stored in personal user profiles.

QuickBooks access depends on both:

NTFS permissions
+
QuickBooks internal user permissions

A Windows user with file access is not automatically a QuickBooks admin.

Step 8 — Create Windows users for accounting staff

Each person should have their own Windows login.

Do not share one Windows account across the team.

Create a local user:

$password = Read-Host "Password for new user" -AsSecureString

New-LocalUser `
    -Name "jane.doe" `
    -Password $password `
    -FullName "Jane Doe" `
    -Description "QuickBooks user"

Grant RDP access:

Add-LocalGroupMember -Group "Remote Desktop Users" -Member "jane.doe"

Grant access to the company file folder:

$Path = "C:\QuickBooksCompanyFiles"
$User = "jane.doe"

$Acl = Get-Acl $Path
$Rule = New-Object System.Security.AccessControl.FileSystemAccessRule(
    $User,
    "Modify",
    "ContainerInherit,ObjectInherit",
    "None",
    "Allow"
)
$Acl.SetAccessRule($Rule)
Set-Acl -Path $Path -AclObject $Acl

Use Modify instead of FullControl unless the user genuinely needs permission to change folder security.

For domain environments, use domain groups instead:

QB-Users
QB-Admins

Then assign permissions to groups, not individuals.

Step 9 — Create QuickBooks internal users

Windows users and QuickBooks users are separate.

Inside QuickBooks:

Company
  → Users
  → Set Up Users and Roles

Create a QuickBooks user for each accountant.

Assign only the roles they need.

Examples:

• Full Access for the QuickBooks admin;
• Accounts Payable;
• Accounts Receivable;
• Payroll;
• Reporting;
• Inventory;
• External Accountant.

Do not give everyone QuickBooks admin rights.

For auditability, each person should have:

One Windows user
+
One QuickBooks user

Avoid shared QuickBooks logins.

Step 10 — Plan RDS CALs

Windows Server allows limited Remote Desktop access for administration.

That is not the same as a licensed multi-user desktop environment.

If users will sign in regularly to use QuickBooks, plan Remote Desktop Services.

Microsoft requires an RDS CAL for each user or device that connects to a Remote Desktop Session Host.

For accounting firms, the practical options are:

Do not confuse:

QuickBooks user license

with:

Microsoft RDS CAL

They are separate.

A user may need both.

Step 11 — Test multi-user workflow

Before production, test with at least two real users.

Test:

1. User A signs in by RDP.
2. User A opens QuickBooks.
3. User A opens the company file.
4. User B signs in by RDP.
5. User B opens QuickBooks.
6. User B opens the same company file.
7. Both users perform safe test actions.
8. Confirm the file is in multi-user mode.
9. Confirm reports open.
10. Confirm printing or PDF export works if needed.

Do not assume the setup works because QuickBooks launches for Administrator.

The real test is multi-user access with non-admin users.

Step 12 — Back up QuickBooks properly

QuickBooks company file backups are critical.

Use multiple layers:

QuickBooks internal backups

Use QuickBooks' own backup process where appropriate.

Create scheduled backups if supported by your edition and workflow.

Store backups outside the live company file folder.

Server backups

Use VM backups or snapshots for server-level recovery.

Snapshots are useful before:

• QuickBooks updates;
• Windows updates;
• major file migration;
• permission changes;
• RDS changes;
• company file upgrades.

But snapshots are not a replacement for QuickBooks-aware backups.

Off-server copies

Keep backup copies outside the same server.

If the server is lost, encrypted, deleted, or corrupted, a backup on the same disk may not help.

For production accounting data, test restore.

A backup plan is not complete until a restore works.

Common errors and fixes

Error 1 — "QuickBooks Database Server Manager is not available"

Usually QuickBooks hosting was not enabled yet.

Fix:

1. Open QuickBooks Desktop on the server.
2. Go to File → Utilities → Host Multi-User Access.
3. Confirm.
4. Open QBDSM again.
5. Scan the company file folder.

Error 2 — Error H202

H202 usually means QuickBooks cannot reach the company file host.

For RDP-based deployments where everyone works on the same server, this should be rare.

Check:

• QuickBooks database service is running;
• QBDSM scan completed;
• .ND file exists;
• ServerMode=1 is present;
• folder permissions are correct;
• firewall rules were not tightened;
• users are opening the correct file path.

PowerShell:

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

Check .ND file:

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

Error 3 — Error -6123, 0

This usually indicates a problem connecting to the company file.

Check:

• company file path;
• QBDSM service;
• .ND file;
• firewall rules;
• whether another QuickBooks instance has the file open incorrectly;
• file damage;
• backup restore path.

If the file is damaged, do not keep retrying random fixes.

Restore from a known-good QuickBooks backup or contact Intuit/QuickBooks support.

Error 4 — Error -6150, -1006

This can indicate company file damage or file access conflict.

First:

1. Close all QuickBooks sessions.
2. Confirm no stuck RDP sessions are holding the file.
3. Reboot the server if safe.
4. Reopen QuickBooks.
5. Try a known-good backup.

If the file is corrupted, QBDSM scanning does not repair the company file.

Use QuickBooks repair tools or restore from backup.

Error 5 — Users can open QuickBooks but cannot open the company file

This is usually permissions.

Check:

• Windows user has NTFS Modify permission;
• Windows user can read/write the folder;
• SMB share permissions allow access if using network path;
• QuickBooks internal user exists;
• QuickBooks role permissions allow file access;
• the company file is not in a user-only folder.

Test with:

Test-Path "C:\QuickBooksCompanyFiles"

as the affected user.

Error 6 — QuickBooks works after setup but breaks after reboot

The QuickBooks database service may not start automatically.

Check:

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

If StartType is Manual, set it to Automatic:

Set-Service -Name "QuickBooksDB34" -StartupType Automatic

Replace service name if your version uses another number.

Error 7 — QBDSM firewall warning but users can connect

QBDSM may report firewall warnings even when the correct program-based firewall rules exist.

Check actual behavior:

• can users open the company file?
• is QBDSM service running?
• does .ND exist?
• does Port Monitor show a port?
• are Windows Firewall rules present for QuickBooks executables?

If the workflow works, document the warning and verify it is not blocking production.

Security considerations

QuickBooks company files contain sensitive financial data.

Treat the Windows VPS as a production accounting system.

1. Do not expose SMB publicly

Do not expose Windows file sharing to the public internet.

If users connect by RDP to the same server, SMB should not need to be public.

Restrict firewall rules to the minimum required.

2. Use individual Windows accounts

Every user should have their own Windows account.

Avoid:

• shared Administrator login;
• shared QuickBooks login;
• everyone as local admin;
• password reuse;
• no audit trail.

3. Review the SMB share

Check:

Get-SmbShare
Get-SmbShareAccess -Name "QuickBooksCompanyFiles"

Remove broad access if unnecessary.

4. Secure RDP

Use:

• strong passwords;
• RDS licensing for real users;
• firewall restrictions where possible;
• VPN or RD Gateway for stricter environments;
• no shared admin accounts;
• regular Windows Updates.

5. Protect backups

Backups should be encrypted or access-controlled.

Do not leave accounting backups in a folder every user can delete.

6. Be careful with antivirus exclusions

QuickBooks may require antivirus tuning.

Do not disable antivirus entirely.

If exclusions are needed, document the exact folders and executables and review them with your security policy.

Recommended production checklist

Before go-live:

• Windows Server version matches QuickBooks support;
• QuickBooks license confirmed;
• RDS CAL plan confirmed;
• QuickBooks installed;
• Host Multi-User Access enabled;
• QBDSM scans company file folder;
• QuickBooks database service running;
• database service startup set to Automatic;
• .ND file exists;
• company folder permissions verified;
• SMB share reviewed;
• at least two non-admin users tested;
• QuickBooks internal users created;
• backups configured;
• restore tested;
• RDP access secured;
• printers and PDF export tested;
• support/runbook documented.

How Raff fits this setup

Raff Windows VPS is the infrastructure layer.

A practical Raff QuickBooks architecture:

Raff Windows VPS
  ↓
RDP / RDS access
  ↓
QuickBooks Desktop
  ↓
Company file folder
  ↓
QBDSM + backups

For a small accounting team, one Windows VPS can be enough.

For a larger or more security-sensitive setup, consider:

RDS app server
  ↓
Private network
  ↓
File/database server
  ↓
Backups

Most teams should start simple, test carefully, and expand only when the workload proves it needs separation.

What Raff recommends

For QuickBooks Desktop on a Windows VPS:

1. Verify Intuit support and licensing before deployment.
2. Use Windows Server 2022 unless your QuickBooks version confirms another server OS.
3. Use QuickBooks Desktop Enterprise for serious new multi-user Desktop deployments.
4. Enable Host Multi-User Access after install.
5. Use QBDSM Port Monitor instead of assuming static ports.
6. Scan the company file folder with QBDSM.
7. Set the QuickBooks database service to Automatic.
8. Create separate Windows users and QuickBooks users.
9. Plan RDS CALs separately from QuickBooks licensing.
10. Keep company file backups outside the live folder and test restore.

The goal is not just to install QuickBooks.

The goal is to make the accounting workflow stable, licensed, secure, and recoverable.

Tested on Raff

Tested on Raff Windows Server 2022 with QuickBooks Desktop Enterprise 2024 trial edition using the original screenshots in this article. The earlier test verified QuickBooks installation, Host Multi-User Access, QBDSM service registration, Port Monitor, folder scan, .ND file generation, and company file folder sharing. Before republishing as a current "tested" claim, retest the exact QuickBooks version, Windows Server build, RDS role, number of users, file path, dynamic port, and backup/restore workflow.

Suggested verified note after retesting:

Tested on Raff Windows VPS running Windows Server 2022, QuickBooks Desktop Enterprise 2024, QuickBooks Database Server Manager, Host Multi-User Access, dynamic QBDSM port from Port Monitor, company file folder scan, .ND file with ServerMode=1, two non-admin RDP users, and successful multi-user company file access.

Do not publish that exact claim until retesting is complete.

What's next

• Connect to a Windows VPS via RDP
• 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 2019 vs 2022 vs 2025: Which Version to Choose
• ERP on Windows VPS: Hosting, Sizing, and Migration
• Cloud Server Backup Strategies
• Raff Windows VPS

Sources

• Intuit QuickBooks Support — System requirements for QuickBooks Desktop 2024
• Intuit QuickBooks Support — Install, update, and set up QuickBooks Database Server Manager
• Intuit — QuickBooks Remote Hosting Program
• Microsoft Learn — License Remote Desktop Services with Client Access Licenses
• Microsoft Learn — Remote Desktop Services overview
• Date last verified: 2026-07-07

QuickBooks, QuickBooks Desktop, QuickBooks Enterprise, and Intuit are trademarks of Intuit Inc. Raff Technologies 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, self-hosted Windows Server infrastructure.