- 4 minutes to read

Step 4: Deploy Core Services with CLI

Deploy Nodinite Core Services to v7 using Nodinite.Installer.Cli.exe — the CLI installer extracted from the bundle downloaded in Step 3.

Prerequisites

Steps

1. Stop the Pickup Service

If applicable, 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 downloaded ZIP is named <EnvironmentName>-upgrade-core-environment.zip. Extract it and navigate to the bundle root:

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

(Replace DEV with your environment name.)

The bundle root contains:

  • Nodinite.Installer.Cli.exe
  • InstallationMedia folder
  • config.cli.json — generated configuration consumed by the CLI

4. Review the Bundle Before Running

Before executing install commands:

  • Review config.cli.json values for paths, ports, and service account names.
  • Verify the SQL package path (SqlPackage.exe) is correct for your server.
  • Keep the extracted folder structure intact so media paths resolve correctly.

Use CLI help to inspect available commands:

.\Nodinite.Installer.Cli.exe --help
.\Nodinite.Installer.Cli.exe deploy-environment --help

5. Validate the Package

Run validation first without making any changes to the machine. The CLI may prompt for service account passwords if they were not stored in the configuration.

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

CLI validation of core services package
Example of CLI validation for the core services package. Enter the service account password when prompted.

Warning

Fix any errors reported during validation before proceeding. Errors are shown in red.

CLI validation errors example
Example of CLI validation errors — resolve all reported issues before running deploy-environment.

6. Run a Dry-Run

Confirm what the installer would do before applying changes:

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

7. Deploy Core Services

Run the actual deployment after validation and dry-run are clean:

.\Nodinite.Installer.Cli.exe deploy-environment --config ".\config.cli.json"

Important

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

Note

During deploy-environment, if the Configuration Database does not have a verified backup state, the CLI prompts for confirmation before applying schema changes. Confirm the prompt to continue.

CLI core services deployment success
Example of a successful core services deployment. The CLI lists migration next steps: verify the environment, then return to the portal to import agents.

8. Verify

Check that Web Client is accessible at your configured URL (e.g., http://<servername>:40000) and that you can log in.

Completion Checklist

  • Pickup Service stopped and disabled
  • Validation passed without errors
  • Dry-run reviewed and output is as expected
  • deploy-environment completed without errors
  • Web Client accessible at configured URL
  • Can log in to Web Client
  • Database migrated successfully (Core Services v7 schema applied to existing v6 database)

Troubleshooting

"Access Denied" on Database

Problem: CLI fails with SQL permission error.

Solution:

  • Verify the running user is sysadmin on the SQL Server instance
  • Check SQL Server authentication mode (integrated authentication is required for Windows auth)
  • Verify the SQL Server service is running

Web Client Shows "500.21" Error

Problem: "Handler not recognized" error in browser after install.

Solution:

  • Install latest .NET 10.0 Hosting Bundle
  • Restart IIS: iisreset /restart (elevated command prompt)

CLI Exits Without Output

Problem: The CLI prompt returns immediately without progress.

Solution:

  • Confirm PowerShell 7 is running with administrator privileges
  • Run .\Nodinite.Installer.Cli.exe --version to confirm the binary is executable
  • Check Windows Event Log for application errors

Next Step