Compliance Manager (Version 1) - Scripting Local Computer Scans for 3rd Party RMM Solutions


Kaseya Rapidfire Tools has now made the Local Data Collection process easier for Compliance Manager customers employing 3rd Party RMM solutions. 


  1. This article was written for users that are still using Compliance Manager version 1. There is a separate article on how to script the data collection for Compliance Manager GRC. 
  2. This article is intended for 3rd party RMM administrators who are familiar with their RMM scripting engine. Kaseya Rapidfire Tools does not support 3rd Party RMM solutions therefore configuring your RMM to run the script provided with this article is outside the scope of Rapidfire Tools Support.


Download: Compliance Manager - Local Computer Scan PowerShell Script


Most RMM tools have the ability to run PowerShell scripts using the RMM agents. The PowerShell script provided in this article (see attached) can be used to perform the Local Computer Scans against any Windows-based machine connected to the internet with an RMM agent installed. 

Each section of the PowerShell script contains a comment detailing what each of the commands in that section of the script is doing. 

If you review the "Run Connector" section of the script you'll notice there is a place holder called [Connector ID]. The Connector ID is a unique identifier for the Compliance Manager site in the portal. Whenever you run this script you must specify an Connector ID so that the script can upload the scan data to the correct site in the portal. 

To obtain the Connector ID for any given site log into the portal and go into a Compliance Manager site. From the left navigation pane, navigate to Compliance Manager  > Settings > IT Complete (see below). You can use the Copy to Connector ID icon to quickly copy the Connector ID and paste it into your script. 

NOTE: Some RMM solutions allow for variables to be used with scripts. If possible, it would be wise to create a variable for the Connector ID in your RMM solution and prompt for that variable whenever you push the script to your RMM agents. This will eliminate the need to create a separate script for each RMM client and allow you to use the same script across all your clients in your RMM.

There are other ways to simplify this piece but we will leave it up to the RMM administrator to determine the best method for their RMM environment. 



During the Compliance Manager Internal Scan To Do step, the compliance manager attempts to  perform a Network Scan as well as a Local Computer Scan against all the machines in the IP range specified in the scan settings. At the completion of the internal scan a new To Do item - Run Local Data Collection (Optional) is created (see below). This To Do item will list all the machines that could not be scanned by the Compliance Manager. These are the machines you can opt to scan using your Local Scan RMM script provided in this document. 


Once your RMM agents have successfully performed a scan you can l use the Import from RMM Connector Scans button shown above to import the scans that you have just performed with your RMM. There will be a list of computers scans if your scans ran successfully. 

Have more questions?

Contact us

Was this article helpful?
0 out of 0 found this helpful

Provide feedback for the Documentation team!

Browse this section