Use this article as a guide to create and maintain an RMM integration with Kaseya VSA, which is their RMM solution. This gives you information about CPU, memory, disk usage, last reboot, etc.
To integrate with Kaseya BMS, see Integrating with Kaseya BMS instead.
It should only take about an hour to get up and running with your RMM. This is a rough estimate based on our experience with several partners who integrated with their RMM.
The Kaseya sync described below will do the following:
For more information about the device mappings, see RMM Field Mappings.
Steps to integrate:
- Set up a secure connection & configure RMM
- Enter your RMM credentials
- Wait for the sync to complete
- Organization matching
- Configuration matching
- Enable Access From Kaseya VSA (Optional)
- Manager or Administrator level access to IT Glue
- If you're integrating with a PSA and an RMM, you will want to first sync your RMM to your PSA and your PSA to IT Glue to make sure that the required data is available for matching
- An SSL connection with a valid certificate (not self-signed) to your RMM
- A dedicated Kaseya user account with Master Role and Scope
- A Manager role will only be able to see RMM matched/unmatched data for organizations that they have explicit access to. To grant access to RMM data for all organizations, refer to Step 7 of our Adding and removing users KB article.
Set up a secure connection & configure RMM
IT Glue talks to Kaseya via API to monitor for devices so we can perform our routine sync. The steps for creating an account are below:
- Log in to Kaseya
- In the left hand sidebar, click System, User Security, Users
- Click New
- Complete the fields, ensuring the fields highlighted below are completed as suggested. Click Save.
- Login to VSA again to activate the user account before you carry on with the integration.
Enter your RMM credentials
- Open IT Glue.
- Navigate to Account > Integrations and click +New.
- Click the Kaseya option.
- Enter your Kaseya Fully Qualified Domain Name (kaseya.example.com) and login credentials and then click Connect.
To add a custom port for API traffic, you can add the port to the FQDN. For example, to add port 3000, your FQDN would look something like this: kaseya.example.com:3000.
- After you enter your RMM credentials in IT Glue, you're taken to the following screen:
You will need to choose an option.
Matching on orgs will allow you to match to top-level organizations in IT Glue.
Matching on machine groups allows you to match to organizations and sub-organizations in IT Glue.
You can change this preference at any point. If you change your preference later, existing matches will be reset. For more information about sub-organizations, see Working with sub organizations.
Next, you’ll be taken to the Sync Logs screen.
Note: If the credentials fail for any reason, syncing will stop until you re-enter your credentials.
Start a manual sync by navigating to Account > Integrations, clicking Actions and Start Manual Sync. When the sync is complete, the status column changes from Syncing... to OK.
IT Glue discovers organizations and configurations and tries to match them to data in your account. The matching logic is at the top of this article. Anything that isn't automatically matched will need to be manually actioned.
- From Account > Integrations, find your RMM in the list and click on Actions and then Matching.
- Start with the Unmatched filter to review unmatched organizations.
- If you're happy with the suggested matches, select the checkboxes and click on Accept Suggestion in the Bulk Actions button:
Or, you can search for and choose a different organization using the Match To column. You can also choose to ignore organizations, which means they won't count as unmatched items in subsequent syncs.
Warning. If you don't see an organization, you can choose the Create Organization action to create (import) it. But make sure there is nothing to match first, so that you don't create a duplicate organization.
- Keep going through all your unmatched organizations until they are all matched.
- If you change your mind about any of the matches, click Actions, choose Change Match, and then manually search for and choose a different organization.
Next, go through the same process to match configurations as you did for organizations.
- To begin, click the Matched filter, pick a matched organization, and then choose the Match Devices action.
- You should first review your matched devices to see if everything looks okay.
- Next, click the Unmatched filter and start matching any remaining configurations until all are actioned (matched, ignored, or created).
- Before you create configurations, first match any of the devices that we couldn't match based on MAC addresses or serial number, for example, virtual servers. When you're done matching, you can create (in bulk or individually) any of the remaining devices coming in from your RMM.
Important. We don't recommend that you create configurations from your RMM if you'd like to then have them populate from IT Glue to your PSA. New items created from such data will not sync with your PSA unless you choose to do so manually by editing and saving each and every item. This is absolutely manual and is not recommended.
- Repeat for each organization until all configurations are actioned.
Once everything is matched, the RMM setup is complete. You can come back to these instructions to discover and match new organizations and configurations from your RMM.
Enable Access From Kaseya (Optional)
Enabling access from Kaseya allows Attachments, Passwords, Related Items, Recent Versions and Notes from the corresponding IT Glue asset to be viewed directly in Kaseya.
- From this Kaseya KB, follow the steps listed after Figure 5.
- Click Actions, Sync Settings next to the Kaseya integration
- Check Enable Access From Kaseya, and click Save
IT Glue data should now be visible from Kaseya as described above.
Please see below:
- On Premises - An intermediate / chain certificate likely needs to be installed on the Kaseya server. You can check certificate status by entering the Kaseya server hostname into an SSL checker. Please take a look at the Kaseya article about using an existing SSL certificate for more information on configuring the certificate correctly.
- Cloud Based - Your FQDN needs to be updated by removing -cdn