How to setup Datto as your RMM
Setup API Access for Datto RMM
Once API Keys are available
You can configure your team on RMMmax as such. Make sure to use the correct API URL as provided to you by Datto in step #5 above…
Now you can browse over to the Dashboard and select RMM Sync to seed the system for the first time or if you log out and log back in this will also force a client/agent sync or you can leave it alone and the automation of RMMmax will cycle around and scan your RMM environment for you. The automation will do this daily if the system is configured to do so.
NOTE:
Configuring access to the RMM environment in the team’s settings area “will not” automatically start any data collections or services on RMMmax. You are required to enable scanning and must enable each client and agent separately for each tool in the RMMmax toolbox.
See RMM Environment settings and enabling of clients and agents’ documentation for more information.
Datto RMM – Importing Datto Components
You should be able to find all 8 components inside the Datto RMM ComStore listed under RMMmax. Import these components into your RMM instance. You do not need to configure or modify the Components; they will ask for data variables to be supplied to operate. This data is provided by RMMmax when job is scheduled.
— No longer required but available if needed —
RMMmax has a Datto RMM Management Package that will need to be downloaded from RMMMax.com and imported into your Datto RMM environment. You will find this downloadable zip file on the RMMmax dashboard under RMM environment control. Once you have this zip file, extract the contents to a folder on your local machine.
Login to your Datto RMM. Using the left navigation menu, drill down to Automation > Components
Select Import from the top navigation menu:
Browse to the folder where you downloaded and extracted the Datto_Components.zip and select one of the .cpt files to import and click Open.
This will open the newly imported component in the Component Library > Create Component screen with all the required data filed completed for you.
Scroll down to the bottom of the screen and select Save Component button.
Repeat process for each of the .cpt files that need to be imported. Please browse your component library searching for RMMmax to validate all the components were properly imported.
If you do not see one of the components, simply go back and import the missing component.
If you see a duplicate of the component due to importing one component one or more times, simply select Edit and Delete one of the components.
Components are (named based) so do not rename the components or the service will not be able to find them when calling out to Datto RMM.
If you are updating the components it is suggested to delete all the current components first, then import the new components. If you do not, you will likely see duplicates or duplicates with similar names and [######] after the component name.
Understanding How RMMmax Communicates with Datto RMM
RMMmax uses APIs to access data and to send jobs to the Datto environment. If we are just asking for some simple data like client and agent names and IDs, then the data is return immediately back to RMMmax. If we need to have an agent preform some function, then we have to request from Datto RMM to schedule a special component that is part of our tool set and allow Datto RMM the time to run the job. This means we do not get back an immediate return to our requests.
How does this effect you?
You should expect delays in the time you ask for a task and the time it gets executed. Here is an example, if you were to ask the Chocolatey tool to install a new application to Agent XX it may sit in a Datto RMM queue for a little while before executing the component. Below is an example of a component still scheduled after 8 minutes, waiting for another component to finish ahead of it.
You will need to allow time for the Datto system to process scheduled components. RMMmax will periodically update its values during a 24-hour period so any changes to environment will be recorded.
Here are the API user permissions we are using currently. You may find that you can reduce the footprint even more.
Downloads: