- 2 minutes to read

Step 8: Download and Update Monitoring Agents

Download and install Nodinite 7 Monitoring Agents. Old Windows Service-based agents will be replaced with IIS-hosted agents.

Prerequisites

Option A: Use Default Ports

Steps

  1. In Portal environment modal, verify default ports
  2. Click Download Monitoring Agents
  3. Wait for ZIP generation

Preparing Download
Example of the preparing your download progress screen shown while the ZIP package is being generated.

  1. Extract ZIP to folder on Application Server (e.g., C:\Temp\Nodinite7-Agents)

  2. Open PowerShell 7 as Administrator

  3. Navigate to extracted folder:

    cd C:\Temp\Nodinite7-Agents

  4. Unblock and run script:

    dir -r | unblock-file
.\Core-Services-and-Agents.ps1

    If your service account password contains special characters, pass it as a SecureString to avoid parsing errors:

    $pwd = ConvertTo-SecureString 'P@ssw0rd!' -AsPlainText -Force
.\Core-Services-and-Agents.ps1 -ServiceAccountPassword $pwd

  5. Verify agents in Web Client

  6. In Portal, click Next to exit update process

Option B: Use Custom Ports or Service Accounts

Steps

  1. In Portal, click Next to continue
  2. Click Agents tab
  3. Change ports and service accounts as needed
  4. Click Save
  5. Close Environment modal
  6. Click Actions → Download

Preparing Download
Example of the preparing your download progress screen shown while the ZIP package is being generated.

  1. Extract ZIP to Application Server

  2. Open PowerShell 7 as Administrator

  3. Navigate to extracted folder

  4. Unblock and run script:

    dir -r | unblock-file
.\Core-Services-and-Agents.ps1

    If your service account password contains special characters, pass it as a SecureString to avoid parsing errors:

    $pwd = ConvertTo-SecureString 'P@ssw0rd!' -AsPlainText -Force
.\Core-Services-and-Agents.ps1 -ServiceAccountPassword $pwd

  5. Verify agents in Web Client

Completion Checklist

  • Monitoring Agents ZIP downloaded
  • PowerShell script completed successfully
  • All agents visible in Web Client with correct status
  • Agent ports configured correctly
  • IIS application pools running

Next Step

Troubleshooting

Script Fails with Permission Error

Problem: PowerShell script fails with access denied.

Solution:

  • Run PowerShell as Administrator
  • Verify service account has permissions
  • Check IIS application pool identity

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