This PowerShell script will install the Huntress Agent. The script will automatically download the installer from the Huntress servers and run it. The script does error checking and logging as well. (It will check to see if the agent is already installed and also verfiy the installation completed.)
You have the option to hard code your Huntress account key, organization key, and tags (optional) in the script, or pass as arguments to the script. Click here for more details regarding the Account Key and Organization Key.
The script supports the following mutually exclusive command-line switches:
-reregister- Force the agent to re-register (useful for clean install)-reinstall- Re-install the agent (useful for "repairing" an agent; this will replace all the files are restart the services)-uninstall- Forces the agent to uninstall itself; useful for corrupted installs
Usage:
powershell -executionpolicy bypass -f ./InstallHuntress.powershellv2.ps1 [-acctkey <account_key>] [-orgkey <organization_key>] [-tags <optional_tags_here>] [-reregister] [-reinstall] [-uninstall]
We have also included a batch file, InstallHuntress.bat, to be used as a wrapper. This is useful if your RMM/SCCM application does not manage the PowerShell executionpolicy.
You'll need to edit the batch file, adding your Huntress account key. Then you can run the batch file as follows:
InstallHuntress.bat <organization_key> <optional tags>
We've had several of our partners use this PowerShell script with a GPO. The "startup script" is the best option because it will install with SYSTEM (local administrator) privileges before any user logs in. The caveat is the system will need to be rebooted before the install will occur.
The startup script is located in Computer Configuration | Policies | Windows Settings | Scripts | Startup
