Uninstalling the IBM MQ Monitoring Agent
Easily and safely uninstall the IBM MQ Monitoring Agent for Nodinite by following this step-by-step guide. On this page, you will learn how to:
- ✅ Remove the IBM MQ Monitoring Agent using the installer or Windows Add/Remove Programs
- ✅ Clean up all related Monitoring Agents and Resources to avoid errors
- ✅ Prevent unnecessary alerts and keep your monitoring environment healthy
- ✅ Troubleshoot and resolve common uninstall issues
Nodinite version 7
Preferred Method: Portal-Based PowerShell Script
In Nodinite v7, agent uninstallation is automated through the Portal-based PowerShell scripts. This modern approach:
✅ Automates agent removal via PowerShell commands
✅ Removes multiple agents simultaneously with consistent settings
✅ Eliminates manual uninstallation steps and reduces human error
✅ Centrally manages uninstallation from the Portal
Nodinite version 6 (Add or Remove Programs - Legacy)
Warning
The Add or Remove Programs uninstallation method for Nodinite v6 is deprecated and will be retired. Please upgrade to Nodinite v7 for the modern Portal-based scripted uninstallation experience.
Before You Uninstall
Important
Remove Nodinite configurations BEFORE uninstalling the agent to prevent error alerts and maintain a clean monitoring environment.
Required Configuration Changes
- Remove Resources - Delete all Resources associated with this agent from Monitor Views
- Remove Monitoring Agent Configuration - Delete the Monitoring Agent entry from Administration
- Update Monitor Views - Remove any filters by Category, Application, or specific Resources from this agent
What Happens If You Skip This?
If you uninstall the agent without removing configurations:
- ❌ Users receive continuous error alerts - Monitor Views will show "unavailable" errors for missing resources
- ❌ Monitoring Agent appears broken - Configuration shows as unavailable in Monitoring Agents list
- ❌ Monitor Views display errors - Any view filtering by this agent's resources will fail
- ❌ Cleanup requires manual intervention - You'll need to log into Nodinite to remove orphaned configurations

Example of unavailable Monitoring Agents after uninstalling without removing configurations.
Uninstall Methods
You can uninstall the IBM MQ Monitoring Agent by running the installer directly or by using 'Add or Remove Programs' in Windows.
Add or remove Programs

Open Windows Programs and Features (or Add or Remove Programs), locate the IBM MQ Monitoring Agent, and select it to begin the uninstall process.
Start the installer
Double-click the MSI file to start uninstalling the IBM MQ Monitoring Agent.

Run the MSI installer to begin the uninstall process.
If Windows displays a security warning, click 'Run' or 'Open' to proceed.
Welcome Screen
When you successfully execute the MSI file or start from 'Add or Remove Programs', a Welcome screen appears.

Welcome screen of the IBM MQ Monitoring Agent uninstaller.
Click the 'Next' button to continue the uninstall process or click the 'Cancel' button to quit the installer.
Change, Repair, Remove
In the 'Change, Repair, Remove' dialogue, click the 'Remove' button to uninstall the agent and proceed to the next step.

Choose 'Remove' to uninstall the agent.
Files in Use
If you did not stop the Service before uninstalling, Windows may display a files-in-use dialog. Click 'Ok' or 'Ignore' to continue with the uninstall.
Ready to Remove Program
Click the 'Remove' button to remove the agent and proceed to the next step.

Final confirmation before removing the agent.
Completed setup
The last step of the un-installation gives either a success or a premature exit.
Successful un-installation example
Failed un-installation example: If the uninstall fails, you will see a premature exit.

Example of a failed uninstall with premature exit.
Click the Finish button to exit and quit the installer.
Support
If you fail to resolve the uninstall problem, contact our Support.
Note
Additional information to aid troubleshooting may exist in the Windows Event Logs.
Next Step
Add or manage Monitor View
Add or manage a Monitoring Agent Configuration
