The Nodinite Message Queueing Server 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
- ✅ Troubleshoot and resolve common update issues
Release notes
For detailed information about the latest releases, visit the Release Notes for the Message Queueing Monitoring Agent.
Important
Always read the release notes before updating to understand new features, bug fixes, and potential breaking changes.
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.
Prerequisites for Updating
Before updating, ensure you have successfully installed the Nodinite Message Queueing Server Agent. The service account must have Logon as Service Right. See Prerequisites for Message Queueing Monitoring Agent for more details. You must be a local administrator to install or update Windows Services.
Running Version
The installed version is displayed in the 'Version' text box.
Example of the Version text box displaying the installed Message Queueing Monitoring Agent version.
You can also find version details in the file properties of the local installation.
Example of the file version details property for the Message Queueing Monitoring Agent.
Compatibility and versioning issues
- If you are updating from version 4.X to 5.X, review Updating from V4 to V5 for important changes.
Update guide
Step 1: Start the installer
Double-click the MSI file to begin updating the Nodinite Message Queueing Server Agent.
Example of the MSI installer file for the Message Queueing Monitoring Agent.
Step 2: Welcome Screen
After launching the MSI file, a Welcome screen appears.
Example of the Welcome screen in the Message Queueing Monitoring Agent installer.
Click 'Next' to continue or 'Cancel' to exit the installer.
Step 3: Change, Repair, Remove
If a previous installation exists, you will see options to Change, Repair, or Remove the Agent.
Example of the Change, Repair, or Remove options screen during update.
Step 4: Custom Setup
Select the components and installation location. Default settings are recommended.
Example of the Custom Setup screen showing component and location selection.
Note
If you change the location, your old configuration will be lost
Click 'Next' to continue or 'Cancel' to exit the installer.
Step 5: Service Account Information
Enter the credentials for the Account that will run the Nodinite Message Queueing Server Agent.
Service Account Fields
Domain: The name of the domain the server belongs to. For a local account, use the server name or a dot (.) as the domain.
User: The account name.
Password: The account password.
Note
The account must have 'Log on as Service Right'
Example of the service account credentials dialog for the Message Queueing Monitoring Agent.
Click 'Next' to continue or 'Cancel' to exit the installer.
Insufficient Privileges
If the account information does not meet Prerequisites, you will see an error message.
Example of the Insufficient Privileges error message during installation.
The most common reasons are that the account is not allowed to run as a service or is not a local administrator. Follow the How to set Logon as a Service right guide and click retry. If the problem persists, click cancel and restart. Make sure to enter valid credentials!
Tip
Check the local event log for errors (both System and Application)
Example of the Files in use warning dialog during update.
Step 6: Completed setup
The final step shows either a success or a premature exit.
Example of the Completed setup screen after a successful update.
If the update fails, you will see a premature exit.
Example of the premature exit screen indicating a failed update.
Click 'Finish' to exit the installer.
When setup finishes, the default text editor opens a file named 'README.txt' with additional information for managing the agent as a Monitoring Agents.
Example of the README.txt file opened in the default text editor after installation.
Support
If you need help resolving update issues, contact our Support.
Note
Additional troubleshooting information may be available in the Windows Event Logs.
Next Step
Configuration of the Message Queueing Monitoring Agent
Related Topics
Prerequisites for Message Queueing Monitoring Agent
Add or manage a Monitoring Agent Configuration
Monitoring Agents
Install Message Queueing Monitoring Agent
Uninstall