Skip to content

Commit 3928fac

Browse files
authored
Merge pull request #71 from immense/DattoRMM-Integration
Datto rmm integration
2 parents c709eaa + 50c172b commit 3928fac

File tree

3 files changed

+64
-22
lines changed

3 files changed

+64
-22
lines changed

.vscode/settings.json

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -35,6 +35,7 @@
3535
"cSpell.words": [
3636
"Acronis",
3737
"Autotask",
38+
"Datto",
3839
"extrafields",
3940
"Filterscript",
4041
"gpupdate",

Documentation/Integrations/dattormm.md

Lines changed: 62 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -3,19 +3,45 @@
33
## Overview
44
This document will detail how to deploy Datto RMM with ImmyBot.
55

6-
ImmyBot does not currently have an integration with Datto RMM
7-
86
## Prerequisites
97
- An active ImmyBot subscription or trial
108
- Admin access to Datto RMM
119
- Knowledge of creating and managing [Deployments](/Documentation/HowToGuides/creating-managing-deployments)
1210

11+
## Integration Capabilities
12+
13+
- Running scripts on the device
14+
- Agent identification by adding an inventory script to be run against all of your endpoints
15+
- Importing agents from linked clients into ImmyBot
16+
- Mapping clients from the integration to tenants in ImmyBot
17+
- Getting an install token for a specific client
18+
19+
:::info About Running scripts through this integration
20+
We utilize Datto RMM Quick Jobs to run scripts through this provider. This can cause an issue due to the ephemeral agent timing out before the connection can be made.
21+
22+
There is a small delay after adding an agent to Datto RMM where Quick Jobs will queue for some time while Datto RMM gets computer information from that agent. We recommend waiting at least 10 minutes before attempting to run ephemeral agents through this integration
23+
:::
24+
1325
## Process
26+
### Create a Datto RMM Security Group (Optional)
27+
1. Navigate to `Setup` -> `Security Levels`
28+
2. Click `Create Security Level`
29+
3. Name it something obvious like ImmyBot API
30+
1. Add a description if you would like
31+
4. Expand `Permissions`
32+
1. Enable `Sites`
33+
2. Set `Sites`, `Devices`, and `Manage` to the Manage radial button
34+
3. Set the rest of the options to View
35+
5. Expand `Components`
36+
1. Set all of these to View
37+
6. Expand `Remote Control Tools`
38+
1. Disable Toggle All
39+
1440
### Create the Datto RMM API User
15-
1. Navigate to **Setup** > **Global Settings** > **Access Control**.
41+
1. Navigate to `Setup` -> `Global Settings` -> `Access Control`.
1642
2. Turn on the Enable API Access toggle.
1743
![alt text](DattoRMM1.png)
18-
4. Navigate to **Setup** > **Users**, and click the username that you would like to enable API access for.
44+
4. Navigate to `Setup` -> `Users`, and click the username that you would like to enable API access for.
1945
![alt text](DattoRMM2.png)
2046

2147
5. Click Generate API Keys to generate an API Key and an API Secret Key for this user.
@@ -24,28 +50,43 @@ ImmyBot does not currently have an integration with Datto RMM
2450
:::
2551

2652
6. The API Key and the API Secret Key will be displayed. Make a note of these and the API URL somewhere safe.
53+
7. Change the Security Group to the one you created. If you did not create one, set it to Administrator
2754

2855
::: danger Important
29-
The API Secret Key will be hidden for security reasons after navigating away from this page. It will not be possible to retrieve it again. However, you can regenerate API keys at any time by returning to the page and clicking Generate API Keys. This will invalidate any keys previously generated. Similarly, clicking Delete API Keys will revoke access altogether. Regenerating and deleting API keys is irreversible, and you must confirm the action by clicking **Confirm** in the confirmation dialog box.
56+
The API Secret Key will be hidden for security reasons after navigating away from this page. It will not be possible to retrieve it again. However, you can regenerate API keys at any time by returning to the page and clicking Generate API Keys. This will invalidate any keys previously generated. Similarly, clicking Delete API Keys will revoke access altogether. Regenerating and deleting API keys is irreversible, and you must confirm the action by clicking `Confirm` in the confirmation dialog box.
3057
![alt text](DattoRMM4.png)
3158
:::
32-
3359
7. Click Save User.
3460

35-
### Set up the ImmyBot Deployment
36-
1. Click on **Deployments** and then Click on **New**
37-
2. Select Datto RMM from the Software / Task drop down
38-
3. Select the radial button labeled **Installed** under the **Software should be**
39-
4. Select the **Latest** radial button under **Desired Version**
40-
5. In the parameter box, input the APIKey, the APISecret and the API URL that you made note of.
41-
::: details <font fontsize=20>📷</font>
42-
![alt text](DattoRMM5.png)
43-
:::
44-
6. Select the radial button labeled **Required** under **Target Enforcement**
45-
7. Select the radial button labeled **Cross Tenant** under **Target Scope**
46-
8. Select the radial button labeled **All Computer** under **Target Type**
47-
9. Select the radial button labeled **No Filter** under **Target Filter**
48-
10. Click on **Create** to save your deployment.
61+
### Add the Ad Hoc PowerShell Component
62+
63+
You need to add the Ad Hoc PowerShell component to your instance if you plan on running scripts from ImmyBot through DattoRMM.
64+
65+
1. Navigate to `Automation` -> `ComStore`
66+
2. Search for `Run Ad Hoc Command (PowerShell 2-5) [WIN]`
67+
3. Click Add on the right hand side of the item
68+
69+
### Set up the integration
70+
71+
1. Navigate to `Show More` -> `Integrations`
72+
2. Click on `Add Integration`
73+
3. Select `Datto RMM`
74+
4. Change the URL to your instance API URL.
75+
5. Update the APIKey and APISecret
76+
6. Click Update
77+
7. Enable the integration
78+
8. Link your clients in the client tab
79+
80+
### Set up the Deployment
81+
1. Click on `Deployments` and then Click on `New`
82+
2. Select `Datto RMM - Integration `from the Software / Task drop down
83+
3. Select the radial button labeled `Installed` under the `Software should be`
84+
4. Select the `Latest` radial button under `Desired Version`
85+
5. Select the radial button labeled `Required` under `Target Enforcement`
86+
6. Select the radial button labeled `Cross Tenant` under `Target Scope`
87+
7. Select the radial button labeled `All Computer` under `Target Type`
88+
8. Select the radial button labeled `No Filter` under `Target Filter`
89+
9. Click on `Create` to save your deployment.
4990
::: details <font fontsize=20>📷</font>
5091
![alt text](DattoRMM6.png)
5192
:::
@@ -57,6 +98,6 @@ Now the next time a session is run against a targeted computer, Datto RMM will g
5798
<br>
5899
>Date Published: 09/19/2025
59100
><br>
60-
>Date Revised: N/A
101+
>Date Revised: 12/19/2025
61102
><br>
62103
>Version Number: 1.0

Documentation/Integrations/ninjarmm-integration-setup.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,7 @@ Add the required parameters and authenticate the OAuthInfo parameter with a Ninj
8080

8181
- Name: NinjaRMM
8282
- ClientID: Provided to you by NinjaRMM
83-
::: note
83+
::: info
8484
Special characters are not supported. If your Ninja instance give you a client ID with a special character you will need to recreate it.
8585
:::
8686
- ClientSecret: Provided to you by NinjaRMM

0 commit comments

Comments
 (0)