Install via Addigy.

Team: Huntress EDR
Product: Addigy (Script)
Environment: MacOS 
Summary:Huntress agent deployment via Addigy (Script) RMM

Addigy provides the ability to create Smart Software to deploy third-party software. This document provides the instructions to add Smart Software for Huntress to your Policies to deploy the Huntress Agent to your customer's computers. We are not able to offer comprehensive support for Addigy; please refer to the Addigy documentation for full details regarding the usage of Addigy policies and Smart Software.

If you have feedback or questions about this deployment, please reach out to support@huntress.com.  

1. Retrieve Your Huntress Account Key
2. Create Smart Software for Huntress
3. Granting Full Disk Access
4. Troubleshooting

Retrieve Your Huntress Account Key

1. Login to the Huntress Web Interface.
   
2. Hover over the Huntress options menu in the upper-right corner of the dashboard.
   
3. Select the "Download Agent" option from the menu.
   
4. On the Installer page click the clipboard icon to copy your secret account key to your clipboard; this will come in handy later in the deployment process.

Create Smart Software for Huntress

1. 1. First, view the Huntress Installation Script for Addigy. Leave this browser window open as we will need it later.  
   2. Create a new entry for Smart Software in Addigy by navigating to Catalog > Software > Smart Software. Click "New" to add a new Smart Software entry. 
   3. Add initial details for your Huntress Smart Software and scroll down to </>InstallationScript.  
   4. Go back to your browser window with the Huntress Installation Script for Addigy and copy the contents by clicking on the "Copy raw contents" icon on the right above the script.  
      
   5. Paste this into the </>InstallationScript section of your Addigy Smart Software window
   6. Scroll down to line 52 within the </>InstallationScript section. Replace __ACCOUNT_KEY__ with the Account Key that you copied earlier on this page.  
   7. If you have a preferred Organization, go to line 56 and replace __ORGANIZATION_KEY__  with your preferred Organization Key (can be found in your Huntress portal under Home > Organizations.) Here is what the script looks like before it is edited.   Here is what it should look like after you have added in your Account and Organization Keys
   8. In most Addigy multitenant setups, each client has their own top-level Policy that represents the client name. If you would like to dynamically use the top-level Policy name as the Organization Name for each agent installation, then comment out line 56 and then uncomment lines 68-69. This will pull in the $POLICY_PATH environment variable and extract just the top-level policy name.  NOTE: This will only work as part of normal scheduled deployments. It will not work when deploying from GoLive or Self-Service.  For example, if your Policy hierarchy looks like this:  then the above script will use "First Tier Top Level Policy" as the Organization Name with "first-tier-top-level-policy" as the Organization Key.   To update this script to dynamically use the Second Tier Policy, update the end of Line 68 so that it uses  {print $2}so that it now look like this: 

      topLevelPolicy=$(echo ${POLICY_PATH} | awk -F ' \\| ' '{print $2}')

      For Third Tier, update the line to say {print $3}, etc.  
   9. A Condition Script is available if you would like Addigy to check if Huntress is an installed application, then install Huntress if it is not found on the machine. 
      1. Under Conditions, select "Check for a path"
      2. Set "Failure" if the following exists:
      3. In "Path to file or folder" input /Applications/Huntress.app
      4. Click on "Add to script".  This action to automatically add your condition script into your Smart Software. This script will look like this 
      5. Ensure "Install on success" is checked.  
      6. When installation script is skipped, report as: "Finished"  Here is the generate code for the Condition Script: 

         if [ -e "/Applications/Huntress.app" ]; then
          echo " /Applications/Huntress.app File exists "
          exit 1
         else
          echo "/Applications/Huntress.app File does not exist"
          exit 0
         fi

   10. Lastly, for Removal Steps, if you would like Huntress to be removed when the device is removed from a corresponding policy, then copy and paste this code block into the Remove Script section 

       #!/bin/sh
       
       /bin/sh /Applications/Huntress.app/Contents/MacOS/Uninstall

       
   11. Click Save and Review on the bottom right.  
   12. Navigate to Policies > (Your relevant policy) > Software. Under the Smart Software tab, click the box next to your new Smart Software for Huntress.  Click "Add/Remove" to add this software to your Policy.  

Grant Full Disk Access to the Huntress agent

Once you have completed the above steps to deploy the Huntress agent, ensure you also add an MDM Policy to grant Full Disk Access.  

Instructions for creating a PPPC Payload for Full Disk access can be found here: 

https://support.huntress.io/hc/en-us/articles/9591929170835  

Troubleshooting

If you see a successfully installed message like the example below, and you still don't see the agent in your portal make sure you're searching from your Account-level dashboard, not your Org-level dashboard.

If you're still stuck; email your Huntress log files from the affected machine's /tmp/ and /Library/Application Support/Huntress/HuntressAgent/ directories to support@huntress.io