Streamline deletion of offline Roaming Clients
Use the Clean Up tool to automatically remove inactive agents from your Roaming Client dashboard based on the last time they sent a DNS query. This helps keep your dashboard organized without affecting active devices.
DNSFilter doesn’t currently provide a built-in scheduling tool for this cleanup action, but you can automate it using any standard scheduler (Task Scheduler, cron, CI jobs, or cloud functions) to run the existing API call on a recurring basis. See more scheduling options in this post's comments.
Key Features
- Select inactivity periods ranging from 7 to 365 days
- A custom option lets you enter any number of days (e.g., 200 or 730)
🚨 Important: This tool only removes the agent from the dashboard unless the agent version supports delete & uninstall. If the device is still in use and the Roaming Client isn’t uninstalled, it will reappear the next time it sends DNS traffic.
We recommend uninstalling the Roaming Client before performing a clean up.
How to bulk delete Roaming Clients
- From the DNSFilter dashboard, go to Deployments > Roaming Clients
- Select Clean Up
- Under Select Inactivity Range, select your desired number of days (or enter a custom value)
- Review the agents from the drop down menu or click view clients in table to view this filter outside the Clean Up tool
- Select Delete and confirm the action
For more details, see our article on managing Roaming Client settings.
-
This does not seem automated … Is there a way to do this without having to do the one-time clean up process described in these steps?
0 -
Kevin McGillicuddy Thanks for the comment! We see you've already engaged our Support team and were asked to contact your distributor, Pax8, for assistance with your question. Their team will instruct you on best practices to clean up the Roaming Client dashboard or escalate the request to us on your behalf per our distributor agreement.
We appreciate your understanding!
0 -
I ended up writing an AWS lambda function that calls the DNS filter API and then calls the delete batch endpoint clean up (/user_agent_cleanups) for each org we have, it then emails me every night if it finds anything
0 -
That's awesome; thanks for sharing, Kevin McGillicuddy ! Always cool to see folks using API like a pro 🙌
0 -
Hi Kevin McGillicuddy - we are having a similar issue and are looking for a similar solution! Am wondering if you would be willing to share the code you used? or at least an outline of it - would be amazing not to have to re-invent the wheel ;)
Thanks in advance.
Paul0 -
Sure, the code is part of a larger repo I use to deploy a lot of other code with the amazon CDK kit. So, I copied the code into a gist - some of the secret values you will have to plug in to wherever you're going to run this, honestly could even do a local node js and scheduled task on windows. The code is all TS. Also for the nodemailer you would ideally need a 3rd party email service like SES or sendgrid etc
https://gist.github.com/kevinmcgillicuddy/538419843aef9e3777e73152502581c20 -
thats amazing - thank you for sharing - much appreciated!
0
Please sign in to leave a comment.
Comments
7 comments