Component monitor not running as expected

Follow these troubleshooting steps if you experience Component monitor issues:

Verify if the Component monitor works on other devices

This helps determine if the issue occurs on a single device, certain device types, or the component in general.

Verify if it is a custom monitor or ComStore Component monitor

Datto RMM Support is unable to debug custom components.

Verify if the script works outside of Datto RMM

This step helps determine if the script is failing or if Datto RMM fails to run the script. If the script cannot run natively, it may be an environmental issue. Custom components must work outside of Datto RMM for Datto RMM Support to troubleshoot further. You must test custom components as a LocalSystem user. Refer to How do I log in as a LocalSystem user to test scripts?

Verify if the Datto RMM Agent is up to date

Outdated Agents can cause problems when communicating to an updated platform. Additionally, Datto RMM Support cannot test for bugs outside of the latest version.

If it is a ComStore component, make sure it is up to date

Datto RMM Support cannot test for bugs outside of the latest version.

Copy the script and run it as a quick job

This demonstrates how the script runs outside of your environment. Document the script's behavior when run.

Gather information for further troubleshooting with Datto RMM Support

If the issue persists, gather as much of the following information as possible to share with Datto RMM Support in Kaseya Helpdesk:

• Component monitor name
• Export of component (if custom)
• .NET version
• Names of the affected policy and monitors
• Hostnames and UIDs of affected devices
• Any error messages (copied and pasted)
• Datto RMM Agent Process and Datto RMM Agent Service log files (Agent log files)