Duplicate Roaming Clients in Dashboard
Minetta Gould
Merged in a post:
Include Public/Private Ip addresses
Jack Taugher
Please include public and private ip address of the roaming client which will help us to differentiate devices which are actually duplicates during cleanups. I see many similar requests, anyway as per support request I am creating a new request for this (Ticket reference 206074).
Minetta Gould
Merged in a post:
Duplicate Roaming Clients in Dashboard Continued
Greg Gelman
Similar to
and the merged post in that thread:
We still see duplicate macOS devices which leads suspicion that agents are not using any unique identifiers tied to a host? I recently uninstalled the package on my own device, reinstalled it and now theres an offline host and an online host in my inventory. How do we ensure that the 'Clean Up Roaming Clients' feature knows which host by hostname to clean up if it only shows 1 host out of the duplicate roaming clients and does not harm the other host which has the same mac address for example?
Jim Luttinen
Not really, this seems like an oversight by the original developers. Why not create a config file and just make a hash of the serial number + MAC address to uniquely identify a system. It would allow easy re-adoption of offline agents while ensuring the values are unique enough to that particular machine that they are extremely unlike to be reproduced.
We've seen this same behavior in our environments.
Ken Tompkins
Maybe this is more of a technical support question.
David
It would prevent a lot of manual clean up being needed if DNSFilter could prevent duplicate devices by MAC address
Ben
the user_agents API endpoint returns attributes.status, which shows a status of "active" for reinstalled duplicated clients.
Mikey @DNSFilter
Merged in a post:
Alerts when Duplicate Device names
Admin DnsFilter
It would be great if you get a duplicate name and mac address show up inside of the Roaming Client portal.