Install via Datto RMM (ComStore)

Team: Huntress Managed Endpoint Detection and Response
Product: Datto RMM
Environment: Windows (macOS version here)
Summary: Installing the Huntress agent using Datto RMM.

Note: If you previously used an older version of this script that did not use the Datto Site Name to map organizations, you may see duplicate organizations when you switch to this version. To clean this up, move the agents from the old organization into the new one that matches the Datto Site Name, then delete the old organization from the Huntress portal.

Overview

Deployment video

How Datto maps organizations 

Setup steps

1 Huntress: Copy Account Key

2 Datto: Set global variable (HUNTRESS_ACCOUNT_KEY)

3 Datto: Add Huntress component (ComStore)

4 Datto: Create deployment job

5 Huntress: Verify agents appear

6 Datto: Confirm job success

Troubleshooting

Need something else?

Deployment video

(Datto-specific info starts at 07:00)

How Datto maps organizations

This deployment component doesn’t ask for a Huntress Organization Key. Instead, it uses information already in Datto:

• The HUNTRESS_ACCOUNT_KEY global variable for your Huntress Account Key.
• The Datto RMM Site Name as the Huntress Organization Name.

Behind the scenes, Datto exposes the Site Name in an environment variable called CS_PROFILE_NAME. The component reads that value and sends it to Huntress as the organization name.

• If that organization already exists in Huntress, new agents are added to it.
• If it doesn’t exist yet, Huntress automatically creates a new organization with that Site Name and assigns the agents there.

If Datto doesn’t send a Site Name for a device (for example, CS_PROFILE_NAME is missing), the installer can’t tell which organization name to use. In that case, the agent goes into a temporary organization called MISSING_CS_PROFILE_NAME in Huntress.

You can move those agents into the correct organization from the Agents page in the Huntress portal once you’ve confirmed where they belong.

Variable mapping

• Datto RMM HUNTRESS_ACCOUNT_KEY variable → Huntress Account Key (manually retrieved from the Huntress portal).
• Datto RMM Site Name (CS_PROFILE_NAME) → Huntress Organization Name.

Huntress: Copy Account Key

1. In the Huntress Portal, click the "hamburger" menu in the top right corner then select Download Agent
   
2. Click the Copy button beside the Account Secret Key
   

Datto: Set global variable (HUNTRESS_ACCOUNT_KEY)

1. Once copied, log in to Datto RMM. From the main page, click Setup and select Global Settings.
   
2. Scroll down to Variables, then select Add Variable.
   
3. Under Value, paste the Account Key copied from the Huntress portal.
   
4. Under Name, type HUNTRESS_ACCOUNT_KEY.
   
5. Select Save, then OK.
   

Datto: Add Huntress component (ComStore)

1. On the Left Menu, select Automation then ComStore
2. Seach for Huntress by name, then select Add

Datto: Create deployment job

1. Under Automation, Select Jobs
   
2. Type in a name, Select Add Component
3. Search for Huntress, Select Add
4. Leave variables boxes blank, select Add Target
5. Find and Add Target devices
6. Select Deployment Schedule options then Scroll down to Create Job

Huntress: Verify agents appear

1. After the Scheduled Job runs, wait 5-10 minutes then, in Huntress select the home icon and see the number of Total Agents installed.
   

If not all expected machines appear, start by troubleshooting with these articles:

• Checking Agent Status
• Operating System Requirements
• Install Script Error