Team: Huntress Managed Endpoint Detection and Response
Product: Atera (Script), Huntress Agent for macOS
Environment: macOS
Summary: Deploying the Huntress script via with Atera to macOS endpoints.

Installing any product should be a breeze, and that's especially true with Huntress and Atera. This document will walk you through deploying the Huntress Agent for macOS without a reboot.

This only installs the Huntress Agent. It does not install the system extension or the network content filter, which are also needed for full EDR functionality, such as endpoint isolation. Review the complete macOS installation instructions to make the right choice for your environment.

We are not able to offer comprehensive support for Atera RMM. Refer to the Atera documentation for full details regarding the usage of Atera scripts.

In this Article

Retrieve Your Huntress Keys

Creating the Script within Atera

Deploy Agents via Atera

Retrieve Your Huntress Keys

1. Log in to Huntress and go to the Agent Setup page.
2. Get your Account and Organization keys. If you use Agent tags, have those ready as well.

Creating the Script within Atera

1. Log in to your Atera instance and go to Admin > Monitoring and automation > Scripts.
2. Click the Create Script button.
3. Click More script properties to fill out all the fields.

   Field name	Setting
   Description	Use whatever works best for your environment.
   File Name	Your choice, but it must have the .sh extension.
   Category	(Optional)
   Max Script Run Time (minutes)	We recommend setting this to 2, as the default of 10 minutes is excessive for Huntress deployment needs.
   Run As	System
   Arguments	Leave blank

   Suggested values are used in this screenshot.

    

   
4. Download the Huntress Agent for macOS deployment script for Atera.
5. Add the script to the Atera Script Editor.

   

6. On line 45, insert your Huntress Account key over the _ACCOUNT KEY_ text in the script. It should look similar to this:
   

7. On line 49, confirm that {[huntress_orgkey]} exists between the quotes. Atera uses Variables to dynamically fill the Organization Key when you deploy the script to your endpoints. It should appear as:
   Note: If correctly typed in, you should see the variable highlighted within the script, which will appear in the Variables input bar above the Script Editor. They are depicted in green above. 

8. Finally, click Create.

   

The Huntress Agent for macOS script is now ready for deployment.

Deploy Agent via Atera

1. From the Customers page of your Atera instance, select the customer name and go to the Devices tab.
2. Select the endpoints you want, such as all macOS endoints, and click the Run Script icon.
3. In the Run Script on Devices dialog, select an appropriate Automation Expiration option and then click Next.
   (Note: The default Automation Expiration policy will skip offline agents, and you will need to manually re-queue them when they are online.)
4. In the next dialog, you must specify the Huntress Organization Key to replace the variable. Then click Run Script. 
   
   

   If the endpoints don't have the Huntress Agent installed, you can simply type out the customer name for the Organization key exactly as you want it to appear in the Huntress platform; it will create a new entry for them. If you previously deployed Huntress Agents to this organization, you must use the Organization key that matches the Huntress platform to prevent duplicate Agent creation. (If you experience duplicate organization creation, you can move the Huntress Agents to the correct Organization.)

   

5. You should receive a pop-up indicating that the job has been queued. Click View to see the deployment outcome.
6. Expand the customer name pane and click the information icon by the status details to see the logs.
7. The log should contain troubleshooting information if necessary, but in our example below, the Agent was successfully installed.