If an agent is removed from the console, it should check back in if the software has not been removed.
F
Fred Brumm
This happens all the time, customers pull systems off of maintenance, turn them off and put them in a closet.
Then we delete all of our stuff and all is well. - we think -
Then, something happens, they need that system and it's back online.
Our RMM kicks in and sees that huntress is installed and moves on, when actually the system is out of compliance.
Kind of a big operational gap in my opinion that should be easy for you guys to fix.
Canny AI
Merged in a post:
Inactive EDR Agent
J
Jack Hebden
After an inactive agent has been removed from Huntress, when the device comes back online, the device will be left with the Huntress agent but will not check back into the portal.
It would be good to see a feature release where the agent reopens itself in the portal as managing the numbers across thousands of endpoints is quite challenging!
C
Clint Bergman
I believed that the Huntress Agent was uninstalled from the endpoint upon next check-in if the agent was removed from the console. Is that not the case?
R
Ralf Schwerdt
Some change in this would be great.
For us it would also be beneficial, to have a "delete now" button, which is clearing the client in Huntress, but as soon as it is online again it is visible again.
Background is kind of the same: Customers have devices that are offline for a long time, we delete them, but when it comes up is has to be re-registered.
Nice way to solve this would be having the uninstall and delete as separate options.
NW
This is badly needed, we have hit this exact problem this week.
N
Nevada Mullen
This functionality is definitely needed. The current implementation which can leave 'orphaned' agents is difficult to work with when there are a large number of endpoints. As others have stated users often will hang on to a machine as a spare for 6+ months and then put it back into use, and having to manually check for this or set up monitoring in our RMM and then correct the issue isn't efficient. Our RMM system (Kaseya) is able to do this with deactivated endpoints and it's great for keeping the amount of active licenses/seats in line with what is actually being used.
A
Aaron Julian
Bump...it's been a year......
D
Derek Gabriel
I'd love to see this feature, SentinelOne handles this. They have a "decommission" feature, which removes the device from the console, and attempts to uninstall the agent, if the agent doesn't get uninstalled and later tries to check-in, it's reactivated and the device is re-added.
At minimum, if the agent software becomes orphaned, it should self-destruct. Or when the installer is run, it should be able to update the tokens and re-register the existing binaries.
Our RMM has the option to run a script if it has not run in XX days, so we could easily just re-run the Huntress installer when the device is re-added, but as it is now, over-installing is not an option. I guess we could update the installer script to uninstall first, but that might cause a lot of other side effects.
A
Aaron Julian
We 100% need this badly. This is more important than ever as we move to let Huntress control our anti-virus!
Please please please do one of the following:
- Make the Huntress client uninstall itself automatically as soon as it finds out it's orphaned so that our RMM can detect that and reinstall it properly.
- Just let the agent check in and start billing us again (unless we have blacklisted it some how.)
I know you guys can find a proper solution for us, for such a great product this is a huge oversight.
Thanks!
C
Cameron Granger
Hi Fred! Thanks for the feedback.
I put in a note to our development team about this.
_____________________________________________
For anyone following, please see: https://huntress.zendesk.com/hc/en-us/articles/4404004930195#Orphaned_Agent
***Huntress will task an Agent to uninstall for 30 days before abandoning the task. If Huntress does not get a response from the agent within 30 das, it is orphaned, and the Agent's key/token has been revoked by Huntress. When attempting to re-install an orphaned Agent (usually through an RMM), the files will be re-installed. However, the Agent is still using the revoked key/token, making the installation successful, but the Agent will fail to communicate to the Huntress cloud.
For the Agent to show again in the Huntress Dashboard, the Agent must be Uninstalled and Reinstalled. *****