Installing the Message Queueing Monitoring Agent
Unlock the full potential of your enterprise message queue monitoring with the Nodinite Message Queueing Monitoring Agent. This guide covers both the modern Portal-based installation (recommended) and the legacy MSI-based approach for remote servers.
Nodinite v7.0.4 and Later (Recommended)
New 7.0.4
Message Queueing Monitoring Agent v7.0.4 and later should be installed using the Nodinite Portal-based scripted installation. This modern approach provides automated installation and configuration with minimal manual intervention.
Why Use Portal-Based Installation?
✅ Automated agent installation and configuration 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
✅ Includes AI Diagnostics New 7.0.4 for intelligent error analysis
✅ Supports .NET 10 Hosting Bundle for modern runtime performance
Get Started with Portal-Based Installation
Follow the comprehensive Install Nodinite v7 guide to install the Message Queueing Monitoring Agent using the Portal-based approach. The Portal generates PowerShell scripts that install and configure the agent automatically.
Key Steps:
- Register your environment in the Nodinite Portal
- Select Message Queueing Agent in the Agents configuration tab
- Configure agent settings (port, service account, queue connections)
- Download the installation package with embedded PowerShell scripts
- Run the PowerShell script to install and configure automatically
Complete Portal Installation Guide - Step-by-step instructions with screenshots
Legacy Installation (Remote Servers Only - Not Recommended)
Warning
Deprecated: The MSI-based installation method is legacy and intended only for remote server installations 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.0.4+ Users: If you are installing Message Queueing Monitoring Agent v7.0.4 or later, use the Portal-based installation method instead. The MSI approach below is for legacy v6 installations or remote servers only.
When to Use MSI Installation
Use this method only if:
- You are installing on a remote server that cannot be managed via Portal scripts
- You are maintaining a legacy v6 environment (upgrade to v7 recommended)
- You have specific infrastructure constraints preventing automated installation
MSI Installation Prerequisites
Important
You must be a local administrator to have the right to install Windows Services.
Before you begin
Make sure you comply with the prerequisites for the Message Queueing Monitoring agent.
Step 1: Start the installer
Double-click on the MSI file to start the installation of the Nodinite Message QueuesMonitoring Agent.
The installation begins with the MSI package.
Step 2: Accept End User License Agreement (EULA)
The Licensee is ultimately responsible for making sure Nodinite products are used according to the End User License Agreement. Make sure you have the assigned formal rights to install and perform modifications to the target environment before you continue installing any Nodinite products.
Review and accept the EULA to proceed.
Step 3: Welcome screen
On successful execution of the MSI file, a Welcome screen is presented.
The installer welcomes you to the setup process.
Click the 'Next' button to continue the installation process or click the 'Cancel' button to quit the installer.
Step 4: Custom setup
Select the Components and Location of the installation. Default settings are recommended.
Choose components and installation path as needed.
Click the 'Next' button to continue the installation process or click the 'Cancel' button to quit the installer.
Step 5: Service Account Information
Enter the credentials for the Account to run Nodinite Message QueuesMonitoring 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.
Note
The account must have 'Log on as Service Right'
Enter the service account credentials here.
Click the 'Next' button to continue the installation process or the 'Cancel' button to quit the installer.
Insufficient Privileges
Error message when account information does not meet Prerequisites.
This error appears if the account lacks required permissions.
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 6 Ready to install
Click next to start the installation.
Step 7 Completed setup
The last step of the installation gives either a success or a premature exit.
Successful installation example
Installation completed successfully.
Failed installation example: A failed installation will render a premature exit.
If installation fails, review the error and retry.
Click the Finish button to Exit and quit the installer.
When the setup has finished, the default text editor will open a text file named the 'README.txt'. The README.txt file holds additional information that you need to add the agent as a Monitoring Agents.
Review the README.txt for next steps.
Step 8: Add Agent as a new Monitoring Agent Configuration
The last installation step is to install the Monitoring Agent as a new Monitoring Agents from within the Web Client using the information provided in the README.txt file from the previous step.
Support
Contact our Support for additional guidance if you fail to resolve the installation problem.
Note
Additional information to aid the troubleshooting may exist in the Windows Event Logs.
Frequently asked questions
Additional solutions to common problems and the FAQ for the Nodinite Message Queueing Monitoring Agent exist in the Troubleshooting user guide.
Next Step
Configuration of the agent
Update
Uninstall
Related Topics
Add or manage a Monitoring Agent Configuration
Monitoring Agents
Prerequisites for Message Queueing Monitoring Agent
Web Client