- 4 minutes to read

Step 7: Download and Update Monitoring Agents

Download the agents CLI bundle from the Portal, deploy the Nodinite 7 Monitoring Agents with Nodinite.Installer.Cli.exe, and mark the migration complete. The agents package contains the Core Services and the imported agents; on Windows Server each agent becomes its own IIS web site with its own port.

Prerequisites

Steps

1. Download the Agents Package

The agents package is available after you import and save the agents in Step 6. In the Portal, open your environment and go to the Review and Download step. If you have unsaved changes, the Portal prompts you before it generates the package.

Unsaved changes prompt
Example of the unsaved changes modal; click Save and download to include the latest agent configuration in the package.

The 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). You don't need to unblock it; the CLI is signed with Microsoft Authenticode.

2. Open PowerShell 7 as Administrator

  • Start Menu → Search PowerShell 7 → Right-click → Run as administrator
cd C:\Temp\DEV-upgrade-agents-environment

(Replace DEV with your environment name.)

Unlike the core bundle, this bundle has one folder per configured server (e.g., nodinite01) next to Nodinite.Installer.Cli.exe and InstallationMedia; the generated configuration is nodinite01\config.cli.json.

4. Validate the Package

The CLI may prompt for service account passwords.

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

CLI validation of the agents package
Example of CLI validation of the full environment package with the Core Services and agents. Enter the service account password when prompted.

Warning

Resolve all validation errors before you deploy. Errors are shown in red.

5. Deploy Core Services and Agents 

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

Important

When agents run as custom domain accounts, review Service Principal Names (SPN) before rollout, especially with Windows authentication or remote SQL Server connections.

CLI deployment success for Core Services and agents
Example of a successful full environment deployment. The CLI confirms "Full environment deployment completed successfully" and prints the remove-legacy command that you run in Step 9, after verification.

6. Verify Agents

Check that the agents are listed in the Web Client and that monitoring data flows. Full verification follows in Step 8.

7. Update Agents on Other Servers

The staged import covers only the agents on the Core Services server. Update every agent that runs on another server locally, on that server:

  • Agents hosted in IIS: in the Portal, add the server in the Servers step and the agent under Agents on this server, configure it in the Agents step, save, and download the package. Run the command in that server's folder on the server itself.
  • Agents installed with an MSI, such as the IBM DataPower and Dynamics CRM agents: run the new MSI from Download and Update Agents on the server and point it to the existing installation folder, as with any agent update.

Important

Run each updated agent with the same service account as in v6. Only that account can decrypt the agent's encrypted settings.

8. Mark Migration Complete in the Portal

Mark the migration complete when every agent is updated, including the agents on other servers. In the Portal, open your environment and go to the Review and Download step. The Nodinite 6 staged upgrade panel now shows a Mark migration complete button.

Mark migration complete panel
Example of the staged upgrade panel with the Mark migration complete button after the agents are deployed.

Click Mark migration complete.

Migration complete message
Example of the confirmation: "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 is now a standard Nodinite 7 environment, which you keep current with Update Nodinite v7.

Completion Checklist

  • Agents package downloaded
  • Validation passed without errors
  • deploy-environment completed successfully
  • Agents visible in the Web Client
  • Agents on other servers updated locally, with the same service accounts as in v6
  • Migration marked complete in the Portal and workspace saved

Troubleshooting

Validation Fails with Service Account Error

The CLI reports service account password errors. Check the following:

  • You run the CLI as an account with sufficient rights
  • The service account names match the Portal configuration

Agents Not Visible in Web Client

The agents don't appear after deployment. Check the following:

  • Refresh the browser
  • The agents' IIS application pools are started
  • The agent ports are open; see Network and Firewall Overview
  • The Windows Event Viewer shows no errors

Next Steps