2023-Mar-14 Agent Deployment Resulting in Unintended Artifact (Resolved)

On March 14th Huntress updated our Windows agent deployment script (InstallHuntress.powershellv2.ps1) to address Active Directory status checks and introduce additional error handling. Unfortunately, we have discovered that the updated script introduced an issue affecting a small number of our partners who deployed agents utilizing the script from March 14th until April 7th.

The script exited prematurely when it was run against any Active Directory Domain Controller (DC), and also any machine with an existing “trust relationship” error. This early termination caused an unintended artifact to be placed in the normal installation directory for the Huntress agent causing the agent installation to fail. This artifact also prevented future attempts to reinstall.

Our current production deployment script has been updated and this error has been addressed for installations moving forward. However, affected environments will be unable to properly install the Huntress agent if the underlying issue is not addressed. We have provided information below to determine if your environment is currently affected, and steps to take to resolve this issue.

Affected partners and systems: 

Only Partners who used our deployment script that was released on March 14th could have been affected by this. This is true regardless of how Huntress was deployed (RMMS, GPO deployment, directly via PowerShell).

If an agent is showing in your Huntress dashboard that device has NOT been affected by this issue.

Resolution steps

Remove any instances of the InstallHuntress.powershellv2.ps1 from your environment and deployment tools. This will prevent re-introducing this issue.

The file “Huntress” (no extension) must be deleted from any device prior to attempting to redeploy. This can be done manually. We are also providing the following PowerShell script to check for and remove the Huntress file. If you have installed Huntress on a drive other than C: please update the script accordingly.

if (test-path "c:\program files\Huntress"){

 if (!((Get-Item "c:\program files\Huntress") -is [System.IO.DirectoryInfo])){

  Remove-Item "c:\program files\Huntress"

 }

}

if (test-path "c:\program files (x86)\Huntress"){

 if (!((Get-Item "c:\program files (x86)\Huntress") -is [System.IO.DirectoryInfo])){

  Remove-Item "c:\program files (x86)\Huntress"

 }

}

Once this file has been removed, you may then redeploy Huntress. You’ll know the installation has been successful when you see the agent in your Huntress Dashboard.