Install guide

About 20 minutes: two SQL scripts, one settings file and one PowerShell command. Nothing is installed on GP workstations, and GP itself isn't touched.

Watch it first

A 3-minute walkthrough of the steps below, with captions. The voice is computer-generated.

What you need

• SQL Server 2017, 2019, 2022 or 2025 holding your GP databases. 2016 SP1 is expected to work; 2014 and older aren't supported. Express works too, without SQL Agent.
• A Windows server on your domain that can reach that SQL Server. The SQL Server machine itself is fine.
• Permissions: local admin on that Windows server, and sysadmin on SQL Server for the two scripts.
• Your license key from the welcome page after you ordered, and the zip from the download page.

Steps

1. Unzip the download

   Copy the Ledger Doctor folder from the zip to C:\Program Files\Ledger Doctor on the Windows server. It holds the service, the two SQL scripts and a settings example.

   The alpha isn't code-signed yet, so Windows may say "unknown publisher" the first time. Choose More info, then Run anyway.

2. Create the Ledger Doctor database

   In SQL Server Management Studio, signed in as a sysadmin, open ledgerdoctor_install.sql and run it. It creates the LedgerDoctor database, loads the checks, finds your GP companies and, except on Express, adds the SQL Agent job "Ledger Doctor nightly scan" at 5:45 AM.

   Running it again later upgrades in place.

3. Create the Ledger Doctor SQL login

   Open ledgerdoctor_security.sql. Replace CHANGE_ME_PASSWORD with a strong password and save it in your password manager. Run the script. There's nothing else to edit: it finds every GP company on its own.

   The login can read GP, owns only the LedgerDoctor database, and can delete only from the few tables the one-click fixes clean up. When you add a GP company later, Ledger Doctor tells you, and running the script again adds it.

4. Fill in the settings file

   In the Ledger Doctor folder, copy ledgerdoctor.example.json to ledgerdoctor.json and open it in Notepad. Fill in:

   • ConnectionString: your SQL Server name and the password from step 3.
   • Approvers: the Windows users or groups allowed to apply and undo fixes and change settings. Everyone else on the domain can view the dashboard, preview fixes and work the close checklist.
   • LicenseKey under Central: your license key.
   • Smtp: only if you want the daily email report.
   • On SQL Server Express, set RunNightlyScan to true so the service runs the scan instead of SQL Agent.

   "ConnectionString": "Server=GPSQL01;Database=LedgerDoctor;User Id=LedgerDoctor;Password=...;TrustServerCertificate=True",
   "Approvers": [ "YOURDOMAIN\\Ledger Doctor Approvers" ],
   "Central": { "LicenseKey": "LD-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX", ... }

   Backslashes in JSON are doubled, as in YOURDOMAIN\\jsmith.

5. Install the service

   Open PowerShell as administrator in the Ledger Doctor folder and run:

   powershell -ExecutionPolicy Bypass -File .\install-service.ps1

   It installs the "Ledger Doctor" Windows service, locks ledgerdoctor.json down to administrators and the service, opens port 8080 on the domain firewall profile, and checks that the service answers.

6. Open it

   Browse to http://SERVERNAME:8080 and click Scan now. Edge and Chrome sign people in with their Windows account automatically when the server is in the Local intranet zone, which is the default for single-label names like GPAPP01. If a browser asks for a password, add http://SERVERNAME to the Local intranet zone by Group Policy.

Updating

New checks arrive on their own, once a day. For a new version of the service, download the new zip, copy LedgerDoctor.Service.exe and the wwwroot folder over the old ones, run the new ledgerdoctor_install.sql if the zip has one, and run Restart-Service LedgerDoctor.

Removing it

Run Stop-Service LedgerDoctor; sc.exe delete LedgerDoctor, delete the folder, then drop the LedgerDoctor database and login. Removing Ledger Doctor never changes GP data.

Good to know

• The dashboard is served over plain HTTP on your internal network. Windows sign-in never sends passwords, but page contents aren't encrypted on the wire. HTTPS with your own certificate is planned before general release.
• Stuck? Email support@myledgerdoctor.com with the step you're on and any error text.