Installing any product should be a breeze and that's especially true with Huntress. We've created a deployment procedure for Kaseya VSA that will install the Huntress agent on 32 and 64-bit Windows systems (Vista+/Server 2008+) without any user interruptions or reboots.
The procedure will automatically use Kaseya's GroupName (vAgentConfiguration.groupName) to organize the agents within Huntress--the groupName will be used for the Huntress organization name. Since Kaseya's groupName includes the organization (e.g., group.organization) you may end up with Huntress organization names like west.company and east.company. Here are 3 potential fixes:
OPTION 1 (quickest): You can change the organization display name inside your portal and the script will continue to use the same org-key.
OPTION 2 (most robust): The deployment script will split Sub-MachineGroups into separate Huntress Organizations. Some minor modifications can make the script slightly easier to deal with if you want all clients in a Kaseya organization in the same organization in Huntress. From the Kaseya editor insert a new line into line 16 and modify line 17:
executePowershell("", "('#vAgentConfiguration.groupName#').split('.')[('#vAgentConfiguration.groupName#').split('.').count-1]", true, "All Operating Systems", "Halt on Fail")
executeFile("#vagentconfiguration.agenttempdir#\HuntressInstaller.exe", "/ACCT_KEY=<HUNTRESS_ACCT_KEY> /ORG_KEY=#global:psresult# /S", "Execute as System and Wait", "All Operating Systems", "Halt on Fail")
OPTION 3: Create a variable for HUNTRESS_ORG_KEY in each organization that contains the name you'd like to use. Edit line 14 to log the entry to <HUNTRESS_ORG_KEY>\HuntressInstaller.exe and line 16 of the deployment script to assign /ORG_KEY=<HUNTRESS_ORG_KEY>
Download and Import the Huntress Deployment Procedure
The configuration requires two simple steps:
1Download and Import the Huntress Agent Deployment Procedure
2Create a Variable to Store Your Huntress Account Key
- Download the Huntress Agent Deployment Procedure from our GitHub repository and save it as an XML file.
- To import the Procedure into Kaseya, navigate to Agent Procedures > Manage Procedures > Schedule / Create. Select the folder you want to import the procedure to and then click the "Import Folder/Procedure" button.
- In the "Import Procedure/Folder" window, browse to the XML Huntress Agent Deployment Procedure you just saved and then click the "Save" button.
- You should now see the Huntress Agent Deployment procedure.
Create a Variable to Store Your Huntress Account Key
- Obtain your Huntress Account Key. You'll need to create a new variable to store your Huntress Account Key within Kaseya VSA.
- Click the "Manage Variables" button.
- In the new window, create a new variable named HUNTRESS_ACCT_KEY and set the variable value to your Huntress Account Key. Be sure to select the Org/Machine Group the variable applies to and then click the "Apply" button.
You're Ready to Deploy!
Congratulations, your Huntress Agent Deployment Procedure is ready to use. Schedule it to run and watch your agents show up within the Huntress Dashboard!
Note: Depending on VSA configuration, you may need to approve the script before running it.
- Kaseya VSA has detailed agent logs to troubleshoot deployment. If your deployment doesn't appear to be working properly, please consult these logs and have them available for Huntress support to assist with troubleshooting. First, click on the "Agent" menu item and then "Agent Logs"
- Select the agent you wish to review the logs for
- In the tabs at the top select "Agent Admins Logs" and "Procedure History."
- Review the log for clues to why the deployment didn't go as expected. Provide these logs to Huntress support if requested.
Some minor modifications can make the script slightly easier to deal with if you want all clients in a Kaseya organization in the same organization in Huntress. As is the script will split Sub-MachineGroups up into separate orgs.
Change the OrgKey for Huntress to the results of an "executePowershell" procedure step that saves to #global:psresult#. Execute the powershell:
note: that's all one line, web formating might split it up on me.
Obviously the usefulness of this depends entirely on the structure of your Kaseya system.
Gregory Mikesell thanks for the tip. It worked perfectly and made my deployment much smoother.
Please sign in to leave a comment.