Team: Huntress Managed Endpoint Detection and Response (EDR)
Product: Huntress Agent
Environment: Huntress.io portal
Summary: If the Huntress Agent previously checked in to the portal but has stopped, you'll want to investigate why it is happening.
You have a Huntress Agent that registered but has not checked in.
Last Seen is the last time the Huntress Agent checked in for tasking.
Last Update Request is the last time the Huntress Updater checked for an update.
There are a few common reasons this may be occurring:
- If the agent and updater have failed to check-in, the host is likely offline (or wiped/re-imaged without uninstalling the agent first). If this is the case, you can remove the agent from your account.
- If the host is online, use the Windows Services Manager to verify that the HuntressAgent and HuntressUpdater services are running. If the services are running, try resting the services.
The agent logs should provide additional details and may indicate what the issue could be. The logs can be found in the locations below. If there are no logs it typically indicates the agent/updater have never (the logs are created immediately when the services are started).
%PROGRAMFILES%\Huntress\HuntressAgent.log %PROGRAMFILES%\Huntress\HuntressUpdater.log