TEAM: Huntress Managed Endpoint Detection and Response (EDR)

PRODUCT: N-Able N-Central (Script), Huntress Agent for macOS
ENVIRONMENT: macOS
SUMMARY: Deploying the Huntress Agent script via N-Able N-Central(Script) to macOS endpoints.

Installing any product should be a breeze and that's especially true with Huntress. We've created a deployment procedure for N-Able N-Central that will install the Huntress Agent on macOS (10.15+).

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 N-able N-Central RMM. Refer to the N-Central RMM documentation for full details regarding the usage of N-Central RMM tools.

Retrieve your Huntress Keys

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

Import the Huntress Agent Script

Download the Huntress Agent for macOS deployment script for N-able N-Central. Save the file as HuntressAgentDeployment-macOS.sh.

Due to requirements within N-Central, it's recommended that the filename have no spaces. This prevents execution problems when you run the script.
From the N-able dashboard at the Service Organization (SO) level, go to Configuration > Scheduled Tasks > Script/Software Repository.
Click Add and select Mac Scripting.
On the Add Script/Software Repository Item page, add the Huntress deployment script file you just downloaded.
Provide command line parameters for the script. The filename must match, and you will want to add the following after the script name:
--organization_key="My Mac Agent" --account_key="YOUR_ACCOUNT_KEY_HERE"
If done correctly, it should look like this:

Your Huntress Account Key is used for all installations, but the Organization Key can be updated each time you run the script to match the customer name where you are deploying the agent. Make sure to keep the customer name within the quotation marks.
Click OK to save your changes.

Schedule the Script to Run

For each customer to appear as a separate organization within Huntress, you must schedule each customer individually.

From the customer view, open the Actions menu and click Run a Mac Script to schedule the Automation Policy.
.
On the MAC SCRIPTING TASK page Details tab, in the Repository Item dropdown select the Huntress macOS Agent Install.
1. Provide a unique identifier for the customer after the --organization_key parameter. The Organization Key associates Huntress Agents with an organization.
2. In the Command Line Parameters field, update your Account Key after --account_key.
  
  Remember to leave the filename as the first parameter, with no spaces in the filename.
On the Targets tab, select the devices you want to deploy Huntress on.
On the Schedule tab, choose when the task should run (Now will run immediately). Optionally, set the number of days the task remains active, so that any offline endpoints will run the task when they come back online.
Finally, save your changes.

The task will be queued and start executing. The policy itself does error checking to ensure that the Account Key was set and other validation to verify the installer was downloaded from the Huntress website and installed properly.

Troubleshooting

If the task fails or runs but the Huntress Agent was not installed, the N-central logs might provide additional details.

On the Scheduled Tasks page in the Status column, click the link to get more details.

The Status Details page should provide additional information and a zip file containing logs.

Need something else?

If you need any assistance from Huntress, or if you notice a step that's missing, please contact us at support@huntress.io.

Install via N-Able N-Central

In this Article