Unresponsive Agents/Changing Unresponsive Agent Settings
By default, Agents that have not called back in 21 days are marked as unresponsive.
Typically agents are unresponsive because the host is offline, possibly decommissioned or re-imaged, but occasionally is caused by something else. For troubleshooting, see the Troubleshooting section below.
If you know the host has been decommissioned, you can remove the agent from your account by following these instructions.
Additionally, you have the option to automatically remove an agent when it has not called back within a specified number of days. See customize the Unresponsive Agent Settings for more details.
When an agent is automatically removed from an account, it will be tasked to uninstall. Should the agent come back online, the uninstall task instructs the agent to remove itself from the computer.
Configuring the Unresponsive Agent Settings
Huntress gives you the option to update the thresholds at which agents are considered "unresponsive" and, optionally, when to automatically uninstall the agent.
You have the option to customize:
- The number of days until an agent is considered unresponsive (Default: 21 days),
- The number of days an agent is unresponsive before action is taken (Default: 7 days)
- The action to be taken on unresponsive agents (Default: No Action).
These options can be set on the Account Level and the Organization Level:
- Account Level will be the Global Default.
- Organization-level settings will override the Account Level settings for granularity in organizations.
To change the thresholds, follow the steps below:
- Login to the Huntress Web Interface.
- To change the Account Level settings, hover over the Huntress options menu in the upper-right corner of the dashboard.
To change the settings for a specific organization, overriding the Account Level settings, go to Step 5.
- Select the Settings option from the menu.
- On the Settings page, you will see a section labeled Unresponsive Agent Settings.
- Days Until Unresponsive - The number of days an agent has not been seen by Huntress before the Agent is considered unresponsive (Default: 21 days)
- Unresponsive Limit - The number of days an agent is unresponsive before action is taken on the Agent (Default: 7 days).
- Unresponsive Action - Action to be taken after the agent has been unresponsive past the Unresponsive Limit (Default: No Action)
- To change the Organizational Level click the organizations tab at the top menu in the portal.
Find the organization you wish to modify and click the edit "pencil" icon.
- By default all organizations will use the Account Level settings. Any changes you make here will override the account settings. This is helpful if you have a specific organization that may have longer unresponsive times than usual.
- The same options that are available at the global level are also available at the organizational level. Once you've selected the appropriate settings click the save button.
To troubleshoot, first check the Windows Services Manager to ensure the Huntress Agent services are running. If they are not running, start the service(s) and verify that they started and are still running. Sometimes restarting the services fixes an issue. You can see logs related to the agent starting and stopping in the Windows Event Viewer.
Huntress Agent Service (HuntressAgent) Huntress Updater Service (HuntressUpdater)
For further agent troubleshooting, visit the Basic Troubleshooting & Checking Huntress Status page.
If the services have been restarted and the agent is still not checking in, the Huntress Agent log should provide details as to a possible cause. The Huntress Agent log can be found within the following directory:
If you still need help, please use the "Contact Us" button below, or send an email to our help desk at firstname.lastname@example.org. Please attach any logs you may have to help troubleshoot.