- 6 minutes to read

Updating the Azure Monitoring agent

Keep your Nodinite Azure Monitoring Agent up to date and running optimally. This guide helps you update the agent, verify compatibility, and resolve issues—so your monitoring stays secure, reliable, and efficient.

  • ✅ Update your Azure Monitoring Agent with confidence and minimal downtime
  • ✅ Use the Portal-based scripted installation in v7, or the MSI installer for legacy v6
  • ✅ Resolve update issues quickly with actionable troubleshooting and support

Understanding the Update Process

An update replaces the agent binaries on the server. Keep the default installation location so the existing configuration is kept; you manage that configuration (subscriptions, Resource Groups, and the Azure services to monitor) through Remote Configuration as described in Configuration. How you update depends on your Nodinite version.

flowchart TD RN["fa:fa-file-alt Read the release notes"] --> V{"fa:fa-code-branch Nodinite version?"} V -->|"v7"| P["fa:fa-cloud Nodinite Portal
generates PowerShell script"] P --> S["fa:fa-terminal Run script on the
Nodinite Agent Server"] V -->|"v6 (legacy)"| M["fa:fa-box MSI installer
wizard"] M --> R["fa:fa-file-lines README.txt with
connection details"] S --> C["fa:fa-check-double Verify running version
in the Web Client"] R --> C style RN fill:#2678BD style P fill:#93d16d style S fill:#93d16d style M fill:#FFD525 style R fill:#FFD525 style C fill:#2678BD

Update flow for the Azure Monitoring Agent: green nodes show the recommended v7 Portal path, yellow nodes the legacy v6 MSI path, blue nodes the steps shared by both.

Key Components Explained

Component Role Notes
Nodinite Portal Generates the installation and update scripts (v7) Same scripts as in Install Nodinite v7; agents are handled in the Agents step
PowerShell script Installs or updates the agent as an IIS web site on the Agent Server (v7) Run as local administrator
MSI installer Installs or updates the agent as a Windows Service (v6, legacy) Requires a Service Account with Log on as a Service right
Monitoring Service Talks to the agent and shows its Resources in Monitor Views Ports per hop: Prerequisites - Firewall
Monitoring Agent configuration Connects the agent to Nodinite Shows the running version

v7 vs v6 Update Methods

Aspect v7 Portal-based scripted installation v6 MSI-Based Installation
Status ✅ Recommended ⚠️ Legacy, deprecated
Method PowerShell script generated by the Portal Manual MSI wizard per server
Multiple agents ✅ Supported, consistent settings ❌ Not supported, one server at a time
Guide Update Nodinite v7 Update guide on this page

Release notes

Explore the latest features, improvements, and fixes in the release notes for the Azure Monitoring agent.

Important

Always read the release notes before updating to understand new features, bug fixes, and potential breaking changes.

Prerequisites for Updating

Install the Azure Monitoring agent before updating (Install). For v6, the service account needs the Logon as Service Right. See prerequisites for Azure Monitoring agent for more details.

Note

You must log on as a local administrator to install or update the agent.

Running Version

The 'Version' text box shows the installed version.
Monitoring Agent run-time information with the Version text box
Example of the run-time information of the Azure Monitoring Agent, including the Version text box.

You can also find the version in the file details property on the local installation.
File properties dialog showing the Azure Monitoring Agent file version
Example of the file version details in Windows Explorer properties.

Nodinite version 7

Preferred Method: Portal-Based Scripted Installation

In Nodinite v7, the Portal-based scripted installation automates agent updates. This modern approach:

  • ✅ Automates agent installation and updates via PowerShell scripts
  • ✅ Configures multiple agents simultaneously with consistent settings
  • ✅ Eliminates manual MSI installations and reduces human error
  • ✅ Centrally manages all environments from the Portal

Follow the Install Nodinite v7 or Update Nodinite v7 guide to update agents using the Portal-based approach. The Portal generates PowerShell scripts that install and configure agents automatically.

Nodinite version 6 (MSI-Based Installation - Legacy)

Use this MSI workflow only for legacy v6 environments.

Warning

The MSI-based installation method for Nodinite v6 is deprecated and will be retired. Upgrade to Nodinite v7 for the modern Portal-based scripted installation experience.

Compatibility and versioning issues

  • Use version 6.x or later with .NET Framework 4.8 or later
  • Use version 5.3.0.19 or later with .NET Framework 4.6.2 or later; we recommend .NET Framework 4.8.1 for best results
  • If you upgrade from 4.X to 5.X, review Updating from V4 to V5

Update guide

Follow these steps to update the Azure Monitoring agent:

Step 1: Start the installer

Double-click the MSI file to start the update process for the Nodinite Azure Monitoring agent.
MSI installer file for the Azure Monitoring Agent
Example of the MSI installer file for the Azure Monitoring Agent.

Step 2: Welcome Screen

When the MSI file runs, the Welcome screen appears.
Welcome screen of the Azure Monitoring Agent installer
Example of the Welcome screen in the Azure Monitoring Agent installer.

Click 'Next' to continue or 'Cancel' to quit the installer.

Step 3: Custom Setup

Select the features and location to update.
Custom Setup screen with feature selection and installation location
Example of the Custom Setup screen showing feature selection and installation location.

Note

If you change the location, you lose your old configuration. Keep the default location.

Click 'Next' to continue or 'Cancel' to quit the installer.

Step 4: Service Account Information

Enter credentials for the Account that runs the Nodinite Azure Monitoring agent.

  • Domain: Enter the domain name. For a local account, use the server name or a dot (.) as the domain.
  • User: Enter the account name.
  • Password: Enter the account password.

Note

The account must have Log on as Service Right; see Prerequisites - Windows rights.

Service Account Information screen with domain, user, and password fields
Example of the Service Account Information screen with domain, user, and password fields.

Click 'Next' to continue or 'Cancel' to quit the installer.

Insufficient Privileges

If the account information does not meet Prerequisites, the installer shows an error message.
Insufficient Privileges error message in the installer
Example of the Insufficient Privileges error message during the update.

If you see this message, the account likely cannot run as a service or is not a local Administrator. Follow How to set Logon as a Service right and click retry. If the problem remains, click cancel and restart. Enter valid credentials to proceed.

Tip

Check the local event log for errors (both System and Application).

Step 5: Completed setup

The final step shows either a success or a premature exit.
Completed Setup screen after a successful update
Example of the Completed Setup screen after a successful update.

Click 'Finish' to exit the installer.

Post-Update

After setup completes, a README.txt file opens with the connection details needed to manage the agent as a Monitoring Agent in Nodinite. To add or manage the Azure Monitoring agent as a Monitoring Agent, see the shared article below:

Troubleshooting

A failed update results in a premature exit.
Premature Exit screen of the installer
Example of the Premature Exit screen indicating a failed update.

For agent startup problems after an update, see the Troubleshooting FAQ.

Support

If you cannot resolve the update problem, contact our Support.

Note

You may find additional troubleshooting information in the Windows Event Logs.

Next Steps