Updating the Monitoring Agent for Windows Server
Keep your Nodinite Windows Server Monitoring Agent up to date for the latest features, security, and compatibility. This guide provides step-by-step instructions, release notes, and troubleshooting tips to ensure a smooth upgrade.
✅ Easy, step-by-step update process
✅ Direct access to release notes and versioning details
✅ Troubleshooting and support for seamless upgrades
This guide teaches you how to update the Windows Server Monitoring Agent.
Release notes
For information about the releases, please visit the Release Notes for the Windows Server Monitoring Agent.
Nodinite version 7
Preferred Method: Portal-Based Scripted Installation
In Nodinite v7, updating agents is automated through the Portal-based scripted installation. 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)
Warning
The MSI-based installation method for Nodinite v6 is deprecated and will be retired. Please upgrade to Nodinite v7 for the modern Portal-based scripted installation experience.
Running Version
The installed version is displayed in the 'Version' text box.
Find the installed version in the README.txt file.
You can also get this information from the file details property on the local installation:
Check the file version in Windows Explorer.
Compatibility and versioning issues
PreReq: You must have successfully installed the Nodinite Windows Server Monitoring Agent prior to an update. The Service account credentials must have Logon as Service Right. See Prerequisites for Windows Server Monitoring Agent for more information. You must be a local administrator to install (and update) Windows Services.
- 4.X -> 5.X: review Updating from V4 to V5.
Update guide
Follow these steps to update the Windows Server Monitoring Agent.
Step 1: Start the installer
Double-click the MSI file to start the update of the Nodinite Windows Server Monitoring Agent.
Start the update by running the MSI file.
Step 2: Welcome Screen
On successful execution of the MSI file, a Welcome screen is presented.
The Welcome screen confirms the update process has started.
Click the 'Next' button to continue with the update process or click the 'Cancel' button to quit the installer.
Step 3: Change, Repair, Remove
A previous installation of the agent will render a model with the option to Change, Repair, or Remove the Agent.
Choose Change, Repair, or Remove as needed.
Step 4: Custom Setup
Select components and the installation location. Default settings are recommended.
Select components and location for the update.
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.
Service Account Information
Enter the credentials for the Account to run Nodinite Windows Server Monitoring Agent. Depending on the connection string settings, this account will be used to log on and query the databases being monitored.
- 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.
Enter the correct service account credentials.
Note
The account must have 'Log on as Service Right'.
Click the 'Next' button to continue with the update process or click the 'Cancel' button to quit the installer.
Insufficient
Error message when account information does not meet Prerequisites.
Error message for insufficient privileges or incorrect account.
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.
Successful update example
Update completed successfully.
Failed update example: A failed update will render a premature exit.
Premature exit indicates a failed update.
Click the 'Finish' button to exit and quit the installer (update process).
When the setup has finished, the default text editor will open a text file named 'README.txt'. The README.txt file holds additional information that you need to manage the agent as a Monitoring Agents.
README.txt provides post-update instructions.
Support
Contact our Support for additional guidance if you fail to resolve the update problem.
Note
Additional information to aid troubleshooting may exist in the Windows Event Logs.
Next Step
Configuration of the Windows Server Monitoring Agent
Related Topics
Prerequisites for Windows Server Monitoring Agent
Add or manage a Monitoring Agent Configuration
Monitoring Agents
Install Windows Server Monitoring Agent
Uninstall