Updating the Nodinite Azure Logic Apps Logging and Monitoring Agent
The Nodinite Azure Logic Apps Logging and Monitoring agent is built on .NET and follows a monthly update release cycle with security patches, performance improvements, and bug fixes. Keep your agent up to date to maintain support and ensure compatibility with Nodinite Core Services.
On this page, you will learn how to:
- ✅ Update agents using the modern Portal-based scripted installation (v7 - recommended)
- ✅ Apply MSI-based updates to remote servers when Portal approach is not available (legacy)
- ✅ Verify compatibility and versioning for seamless upgrades
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, Event Hubs, Logging, and Workflow Monitoring) through Remote Configuration. How you update depends on your Nodinite version.
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 Logic Apps 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 |
| PowerShell script | Installs or updates the agent 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 settings |
| 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
For information about the releases, visit the release notes for the Azure Logic Apps Logging and Monitoring Agent.
Important
Always read the release notes before updating to understand new features, bug fixes, and potential breaking changes.
Prerequisites for Updating
You must have successfully installed the Nodinite Azure Logic Apps Logging and Monitoring agent prior to an update. The Service account credentials to use must have Logon as Service Right. See prerequisites for Azure Logic Apps Logging and Monitoring agent for more information.
Note
You must be a local administrator to have the right to install (and thereby update) Windows Services.
Running Version
The 'Version' text box displays the installed version.
Example of run-time information displayed in the Version text box.
You can also get this information from the file details property on the local installation:
Example of 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 agents are handled in the Agents step. The Portal generates PowerShell scripts that install and configure agents automatically.
Nodinite version 6 (MSI-Based Installation - Legacy)
Use this MSI installation 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
- 5.x -> 5.1 New installation folder (
C:\Program Files\Nodinite\Agent - Logic Apps\) is being used, move 'Settings.json' from the old folder to the new folder and restart - 4.X -> 5.X review Updating from V4 to V5
Update guide
Follow the steps next to update the Azure Logic Apps Logging and Monitoring agent.
Step 1: Start the installer
Double-click on the MSI file to start the update process of the Nodinite Azure Logic Apps Logging and Monitoring agent.
Example of the MSI installer file for the Azure Logic Apps agent.
Step 2: Welcome Screen
On successful execution of the MSI file, the installer presents a Welcome screen.
Example of the Welcome screen in the Azure Logic Apps agent installer.
Click the 'Next' button to continue with the update process or click the 'Cancel' button to quit the installer.
Step 3: Custom Setup
Select features and the location to update.
Example of the Custom Setup screen showing feature selection and installation location.
Note
Default settings are recommended
Note
If you change the location, your old configuration will be lost
Click the 'Next' button to continue with the update process or click the 'Cancel' button to quit the installer.
Step 4: Service Account Information
Enter the credentials for the Account to run Nodinite Azure Logic Apps Logging and Monitoring agent.
Service Account Fields
- Domain: The name of the Domain the Server belongs to. If you use a local account, use the name of the server or a . (dot) as Domain
- User: The name of the account
- Password: The password for the account
Note
The account must have 'Log on as Service Right'
Example of the Service Account Information screen with domain, user, and password fields.
Click the 'Next' button to continue with the update process or click the 'Cancel' button to quit the installer.
Insufficient Privileges
The installer shows this error message when the account information does not meet the Prerequisites.
Example of the Insufficient Privileges error message during installation.
If you get this message, the most common reason is that the account is not allowed to run as a service or is not a local Administrator on the server. Follow the guide How to set Logon as a Service right and click retry. If the problem remains, click cancel and restart. Make sure to enter valid credentials!
Tip
Check the local event log if there are errors (both System and Application)
Step 5: Completed setup
The last step of the update process gives either a success or a premature exit.
Example of the Completed Setup screen showing successful update.
Click the 'Finish' button to Exit and quit the installer (update process).
Post-Update
When the setup has finished, the default text editor opens a file named 'README.txt'. This file contains the agent's connection details needed to manage it as a Monitoring Agent in Nodinite.
Instructions on how to add the Azure Logic Apps Logging and Monitoring agent as a Monitoring Agent are detailed in a shared article, click on the link below to learn more:
Troubleshooting
A failed update will render a premature exit.
Example of the Premature Exit screen indicating a failed update.
For agent startup problems after an update, see the Troubleshooting FAQ.
Support
Contact our Support for additional guidance if you fail to resolve the update problem.
Note
Additional information to aid the troubleshooting may exist in the Windows Event Logs.