Updating the Database Monitoring Agent
The Nodinite Database Monitoring Agent version 7.2.0 and later uses .NET 10 runtime 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.
Important
.NET 10 Runtime Requirement: Version 7.2.0+ requires .NET 10 Hosting Bundle. Monthly updates are recommended to maintain security patches. See Prerequisites for installation requirements.
On this page, you will learn how to:
- ✅ Update agents using the modern Portal-based scripted installation (v7.2.0+ - recommended)
- ✅ Apply MSI-based updates to remote servers when Portal approach is not available (legacy)
- ✅ Verify compatibility and versioning for seamless upgrades
- ✅ Troubleshoot and resolve common update issues
- ✅ Understand breaking changes and new features (gMSA, AI Diagnostics)
Release notes
For information about the releases, please visit the Release Notes for the Database Monitoring Agent.
Important
Always read the release notes before updating to understand new features, bug fixes, and potential breaking changes.
Nodinite v7.2.0 and Later (Recommended)
New 7.2.0
Preferred Method: Portal-Based Scripted Update
In Nodinite v7.2.0 and later, updating agents is automated through the Portal-based scripted installation. This modern approach:
✅ Automates agent updates via PowerShell scripts
✅ Updates multiple agents simultaneously with consistent settings
✅ Eliminates manual MSI installations and reduces human error
✅ Centrally manages all environments from the Portal
✅ Instant response on synchronization - faster monitoring updates
✅ Includes AI Diagnostics New 7.2.0 for intelligent troubleshooting
✅ Group Managed Service Account (gMSA) support for automated password management
Follow the Install Nodinite v7 or Update Nodinite v7 guide to update agents using the Portal-based approach. The Portal generates PowerShell scripts that update agents automatically.
Important Version 7.2.0 Notes
- .NET 10 Runtime - Requires .NET 10 Hosting Bundle (migration from .NET Framework 4.8)
- Connection String Updates - Microsoft.Data.SqlClient requires
Encrypt=true;TrustServerCertificate=true;properties. The agent attempts to update connection strings automatically during first startup, but manual review is recommended. See SQL Server Connection Strings for details. - Monthly Updates Required - .NET 10 runtime requires monthly security patches. Plan for regular agent updates.
- SQL Script Injection Prevention - Enhanced code security (#18472)
Legacy Update Method (Remote Servers Only - Not Recommended)
Warning
Deprecated: The MSI-based update method is legacy and intended only for remote server updates where the Portal-based approach cannot be used. This method is not recommended for new deployments and will be retired in future versions.
Important
Version 7.2.0+ Users: If you are updating Database Monitoring Agent to v7.2.0 or later, use the Portal-based update method instead. The MSI approach below is for legacy v6 installations or remote servers only.
Running Version
The installed version is displayed in the 'Version' text box.
Example of the Version text box showing the installed agent version.
You can also get this information from the file details property on the local installation:
Example of file version details in Windows Explorer properties.
Prerequisites for Updating
You must have successfully installed the Nodinite Database Monitoring Agent prior to an update. The Service account credentials to use must have Logon as Service Right. See Prerequisites for Database Monitoring Agent for more information. You must be a local administrator to have the right to install (and thereby update) Windows Services.
Compatibility and versioning issues
- 5.0 -> 5.1
- New installation folder is being used, move 'Settings.json' from old folder to new folder and restart
- New Service URL due to changed name of the agent: http://SERVERNAME:8000/Nodinite/Monitor/Agent/Database/
- All Specific categories have been removed, review your Monitor Views after the update
- 4.X -> 5.X review Updating from V4 to V5
- 4.1.0.x -> 4.1.0.y
- Additional features have been added, make sure to review settings and affected Monitor Views after an update
- LogText for Resources written by the Monitoring Agents have been modified to never change unless the state does.
- 4.0 -> 4.1
- Update from older XML configuration based versions requires a manual re-configuration (open old configuration file using notepad and then copy paste applicable settings).
Update guide
Follow the steps next to update the Database Monitoring Agent.
Step 1: Start the installer
Double-click on the MSI file to start the update of the Nodinite Database Monitoring Agent.
Example of the MSI installer file for the Database Monitoring Agent.
Step 2: Welcome Screen
On successful execution of the MSI file, a Welcome screen is presented.
Example of the Welcome screen in the Database Monitoring Agent installer.
Click the 'Next' button to continue with the update process or 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 the 'Cancel' button to quit the installer.
Step 4: Service Account Information
Enter the credentials for the Account to run Nodinite Database Monitoring Agent.
Note
Depending on the connection string used in remote configuration different accounts may be used when monitoring different databases
Service Account Fields
Domain: The name of the Domain the Server belongs to. If a local account is being used, use the name of the server or a . (dot) as Domain
User: The name of the account
Password: The password for the account
Example of the Service Account Information screen with domain, user, and password fields.
Note
The account must have 'Log on as Service Right'
Click the 'Next' button to continue with the update process or the 'Cancel' button to quit the installer.
Insufficient Privileges
Error message when account information does not meet 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 Agents.
Troubleshooting
A failed update will render a premature exit.
Example of the Premature Exit screen indicating a failed update.
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.
Next Step
Configuration of the agent
Add or manage a Monitoring Agent Configuration