- 5 minutes to read

Step 4: Deploy Core Services with CLI

Deploy the Nodinite 7 Core Services with Nodinite.Installer.Cli.exe from the bundle you downloaded in Step 3. The CLI creates one IIS web site per Core Service, upgrades the existing v6 Configuration Database in place, and leaves the v6 installation running until you remove it in Step 9. The general CLI reference is Step 7: Run the CLI Workflow (Elevated PowerShell 7); this page covers the migration specifics.

Prerequisites

Steps

1. Stop the Pickup Service

If you use it, stop and disable the Nodinite Pickup Log Events Service:

  • Open Services (services.msc)
  • Find Nodinite Pickup Log Events Service
  • Right-click → Stop
  • Right-click → Properties → Startup type: Disabled

2. Open PowerShell 7 as Administrator

  • Start Menu → Search PowerShell 7 → Right-click → Run as administrator

The ZIP is named <EnvironmentName>-upgrade-core-environment.zip. Go to the root of the extracted bundle:

cd C:\Temp\DEV-upgrade-core-environment

(Replace DEV with your environment name.)

The bundle root contains Nodinite.Installer.Cli.exe, the InstallationMedia folder, config.cli.json (the generated configuration that the CLI consumes), and README.txt, which shows Mode: Upgrade from Nodinite 6 and the recommended workflow. This package holds the Core Services only, so you run install, not deploy-environment; the agents follow in Step 7.

4. Review the Bundle Before Running

  • Review config.cli.json for paths, ports, and service account names.
  • Verify the SqlPackage.exe path for your server.
  • Keep the extracted folder structure intact so media paths resolve.
.\Nodinite.Installer.Cli.exe --help
.\Nodinite.Installer.Cli.exe install --help

5. Validate the Package

Validation changes nothing on the machine. The CLI prompts for service account passwords that aren't stored in the configuration.

.\Nodinite.Installer.Cli.exe validate --config .\config.cli.json

CLI validation prompting for the service account password
Example of CLI validation of the Core Services package: one service account runs the Web Client, Web API, Log API, Logging Service, Monitoring Service, and MCP Server, and the CLI asks for its password.

Warning

Fix every error reported during validation before you continue. Errors are shown in red.

CLI validation errors
Example of CLI validation errors; resolve all of them before you run install.

6. Run a Dry-Run 

.\Nodinite.Installer.Cli.exe install --config ".\config.cli.json" --dry-run

7. Deploy Core Services

Deploy when validation and the dry-run are clean:

.\Nodinite.Installer.Cli.exe install --config ".\config.cli.json"

Note

If the Configuration Database has no verified backup state, the CLI asks you to back up now, continue, or abort before it applies schema changes; see Config DB backup confirmation prompt.

During the upgrade, the CLI also asks you to acknowledge that it stops the Nodinite 6 Logging and Monitoring services. Run this step at the console: with --non-interactive, the run aborts at that prompt.

Important

If IIS-hosted v7 services run as custom domain accounts, validate Service Principal Names (SPN) before the first Windows-authenticated sign-in. Missing HTTP SPNs for the Web Client and Web API are the most visible failures; missing SQL Server SPNs can break backend connections.

CLI Core Services deployment success
Example of a successful Core Services deployment. The CLI lists the next migration steps: verify the environment, then return to the Portal to import the Monitoring Agents.

8. Verify

Open the Web Client at http://<server name>:<Web Client port>, using the port from the Portal Servers step, and sign in. HTTPS follows in Step 10. If the browser can't connect, check the Network and Firewall Overview.

Completion Checklist

  • Pickup Service stopped and disabled
  • Validation passed without errors
  • Dry-run output reviewed
  • install completed without errors
  • Web Client reachable, and you can sign in
  • Configuration Database upgraded to the v7 schema

Troubleshooting

"Access Denied" on Database

The CLI fails with a SQL permission error. Check the following:

  • The user running the CLI is sysadmin on the SQL Server instance
  • SQL Server allows integrated authentication (required for Windows auth)
  • The SQL Server service is running

Web Client Shows "500.21" Error

The browser reports "Handler not recognized" after the install. Check the following:

  • The .NET 10.0 Hosting Bundle is installed after the IIS features; see Verify ASP.NET Core Module
  • Restart IIS: iisreset /restart (elevated prompt)

CLI Exits Without Output

The CLI returns immediately without progress. Check the following:

  • PowerShell 7 runs with administrator privileges
  • .\Nodinite.Installer.Cli.exe --version prints a version
  • The Windows Event Log shows no application errors

Next Steps