Step 8: Download and Update Monitoring Agents
Download the agents CLI bundle from the Portal, deploy Nodinite 7 Monitoring Agents using Nodinite.Installer.Cli.exe, and mark the migration complete in the Portal.
Prerequisites
- Step 7 completed – Monitoring Agents imported to Portal
- Latest PowerShell 7 installed with administrator privileges
Steps
1. Download the Agents Package
The agents package becomes available for download after agents are imported and saved in Step 7. Return to the Portal, open your environment, and navigate to the Review and Download step.
Note
If you have unsaved changes, the Portal will prompt you before generating the package.
Example of the unsaved changes modal — click Save and download to include the latest agent configuration in the package.
The downloaded ZIP is named:
<EnvironmentName>-upgrade-agents-environment.zip
Extract it to a temporary folder on the Nodinite Application Server (e.g., C:\Temp\DEV-upgrade-agents-environment).
Note
You do not need to unblock the ZIP bundle. The CLI installer is signed and trusted by Microsoft Authenticode.
2. Open PowerShell 7 as Administrator
- Start Menu → Search PowerShell 7 → Right-click → Run as administrator
3. Navigate to the Extracted Bundle
cd C:\Temp\DEV-upgrade-agents-environment
(Replace DEV with your environment name.)
The bundle root contains:
Nodinite.Installer.Cli.exeInstallationMediafolder- one folder per configured server (e.g.,
nodinite01) nodinite01\config.cli.json— generated configuration consumed by the CLI
4. Validate the Package
Run validation before deploying. The CLI may prompt for service account passwords.
.\Nodinite.Installer.Cli.exe validate --config .\nodinite01\config.cli.json
Example of CLI validation for the full environment package including Core Services and agents. Enter the service account password when prompted.
Warning
Resolve all validation errors before deploying. Errors are shown in red.
5. Deploy Core Services and Agents
Run the deployment after validation passes:
.\Nodinite.Installer.Cli.exe deploy-environment --config ".\nodinite01\config.cli.json"
Important
When you change agent identities to custom domain accounts, review Service Principal Names (SPN) before rollout. This is especially important when the environment uses Windows authentication or remote SQL Server connections.
Example of a successful full environment deployment. The CLI confirms "Full environment deployment completed successfully" and shows the next step: remove the legacy Nodinite 6 installation.
6. Verify Agents
Check that agents are accessible in the Web Client and that monitoring data is flowing correctly.
7. Mark Migration Complete in Portal
Return to the Portal, open your environment, and navigate to the Review and Download step. At the bottom of the page the Nodinite 6 staged upgrade panel now shows a Mark migration complete button.
Example of the staged upgrade panel showing the Mark migration complete button after agents are deployed.
Click Mark migration complete.
Example of the migration complete toaster: "Nodinite 6 migration marked complete. Save the workspace to continue as a normal Nodinite 7 environment." The staged upgrade panel is replaced by the standard download panel.
Save the workspace. The environment now operates as a standard Nodinite 7 environment.
Completion Checklist
- Agents package downloaded (
<EnvironmentName>-upgrade-agents-environment.zip) - Validation passed without errors
-
deploy-environmentcompleted successfully - Agents visible and working in Web Client
- Migration marked complete in Portal
- Workspace saved
Troubleshooting
Validation Fails with Service Account Error
Problem: CLI reports service account password errors.
Solution:
- Confirm you are running as an account with sufficient rights
- Verify service account names match what was configured in the Portal
Agents Not Visible in Web Client
Problem: After deployment, agents don't appear in the Web Client.
Solution:
- Refresh the browser
- Check IIS application pools are started
- Verify agent ports are not blocked by firewall
- Check Windows Event Viewer for errors
Next Step
Related Topics
Completion Checklist
- Monitoring Agents ZIP downloaded
- CLI validation passed without errors
-
deploy-environmentcompleted successfully - All agents visible in Web Client with correct status
- Agent ports configured correctly
- IIS application pools running
Troubleshooting
CLI Validation or Deployment Fails with Permission Error
Problem: Nodinite.Installer.Cli.exe fails with access denied or service account errors.
Solution:
- Run PowerShell 7 as Administrator
- Verify service account permissions and correct names in the generated
config.cli.json - Check IIS application pool identity and Windows Event Viewer
Agents Not Visible in Web Client
Problem: After installation, agents don't appear in Web Client.
Solution:
- Refresh Web Client browser
- Check IIS application pools are started
- Verify agent ports are not blocked by firewall
- Check Event Viewer for errors