RELATED IDEAS
Ability to clear Recast Agents that have not communicated with RMS after a period of time.
We have a situation where the agent drop-down in RMS shows double the amount of recast agents than the devices we have Config Mgr. This is likely due to computer refresh. The agents are still listed even after a certain of idle time, not reporting to RMS. This means we must list all agents and review them individually to remove them from RMS. This isn't very pleasant since you don't have a search device name option. What if you were to add a feature similar to the AD cleanup tool? Instead of querying CM vs. AD, query CM vs. RMS. Then provide the ability to delete the discrepancy from within the results like the AD cleanup tool: just a thought, Thx.
| Product | Recast Management Server |
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +101
16
MERGED
Cleanup inactive recast agents based on inactivity
We deployed the recast agent to our environment to leverage of the agent gateway. However, the old clients are not cleaned up if the devices have been replaced. Would be nice to have an option to clean up agents based on inactivity.
0
Recently shipped
Thanks!
This is much appreciated.
Recast Management Server version 5.9.2505 includes automatic Agent cleanup. By default, Agents will be removed after 90 days of being inactive. You can adjust the number of days in your RMS settings. You can see which agents are nearing the Max Inactive Agent Age on the Agent Management dashboard.
I have to presume thousands of dead agents on a gateway don't have any meaningful effect, because this not already being a base consideration in the design of RMS is surprising. What device management software doesn't time out agents?
Merged ideas together.
this other idea is the same as this one . Both ideas should be sync'd into 1
https://ideas.recastsoftware.com/ideas/RS-I-823
this important to having an efficient RMS, else you accumulate obsolete agents over time. this should not really even be a feature request but fix for upcoming version.