Rebuilding QuickBooks Desktop Multi-User Hosting After a Server Reimage

Restore Database Server Manager, regenerate .ND files, re-map workstations, and verify hosting mode across all clients after a server OS wipe.

When a file server is wiped or reimaged, the QuickBooks Database Server Manager installation, folder shares, and .ND configuration files are destroyed along with it. The company file (.QBW) may be intact on a separate volume or restored from backup, but every workstation loses its connection path. This playbook walks through the full rebuild: installing Database Server Manager on the fresh OS, regenerating the .ND network Descriptor files, re-mapping each workstation, and confirming hosting mode so multi-user access is restored cleanly.

Prerequisites and Snapshot

Before touching QuickBooks, confirm the server OS is fully patched and has a static IP address assigned. Locate the company file (.QBW) and verify it is not sitting on the same drive that was wiped. If the file was lost with the OS image, recover it from backup first — our engineers have seen cases where only a damaged or truncated backup survived, and that must be addressed before rebuilding the hosting layer. Record the server's new IP, the exact QuickBooks version year installed on workstations, and the folder path where the .QBW now resides.

Phase 1 — Install Database Server Manager

On the freshly imaged server, install QuickBooks Desktop using the option for a server-only or custom install. Select the option to install only the Database Server Manager component if no one will run QuickBooks interactively on this machine. The version year must match what the workstations run — a 2024 Database Server Manager will not host a 2022 client environment without mismatch errors. After installation, open Database Server Manager from the Start menu and run a scan on the folder containing the .QBW. This scan generates fresh .ND files for each company file it detects.

Phase 2 — Configure Folder Permissions and Sharing

Create a shared folder (commonly QBDATA or QuickBooks) on a drive that persists across future reimages if possible. Grant Full Control to the Windows user group QBDataServiceUserXX (where XX matches the version year — this service account is created during the Database Server Manager install). Also grant Full Control to Everyone at the share-permission level and at least Modify at the NTFS security level for the folder. If the .QBW currently lives elsewhere, move it into this shared folder now and re-run the Database Server Manager scan so the .ND file points to the correct path.

Phase 3 — Regenerate .ND Files

Delete any stale .ND files from the company folder — these still reference the old server name, old IP, or old drive letter and will cause connection failures. On the server, open Database Server Manager, add the company folder path under the Scan Folders tab, and run a full scan. When it completes, confirm that a new .ND file exists alongside each .QBW and that its contents reference the current server name. Open the .ND in Notepad and verify the server name and IP entry match the current machine.

Phase 4 — Re-Map Each Workstation

On every workstation, open QuickBooks while holding the Ctrl key to suppress the automatic open attempt. Once at the No Company Open screen, use File > Open or Restore Company > Open a company file and navigate to the server share via the UNC path (\\ServerName\QBDATA\CompanyFile.QBW) rather than a mapped drive letter. Mapped drives are a common source of multi-user connection failures and should be avoided. After opening the file, immediately switch to single-user mode, then back to multi-user mode to confirm the workstation can toggle modes without error.

Phase 5 — Verify Hosting Mode

Hosting must be turned on only on the server — never on workstations. On the server, open QuickBooks Database Server Manager and confirm the company file appears in the list with a status of Monitored. On each workstation, go to File > Utilities and check that the option reads Stop Hosting Multi-User Access (which means hosting is currently on) or Host Multi-User Access (which means it is off). Workstations should show the latter — hosting off. If any workstation shows hosting on, disable it.

Rollback Points

If a workstation cannot connect after re-mapping, the most common cause is a Windows Firewall rule blocking inbound QuickBooks ports. Database Server Manager configures these automatically, but a Group Policy or third-party security suite can override them. The rollback is to temporarily disable the firewall on the server and test the connection; if it succeeds, re-enable the firewall and manually add inbound rules for the QuickBooks version-specific port range. If the .ND regeneration fails entirely, delete the .ND files, uninstall Database Server Manager, reboot, and reinstall from a fresh download.

Clean Outcome

A successful rebuild shows all workstations opening the company file via UNC path, toggling between single-user and multi-user mode without error, and the server Database Server Manager listing the file as Monitored. Hosting is active only on the server. The F2 Product Information screen on each workstation should display Local Server Name as the server's machine name, not the workstation's own name.