Endpoint Administration 1:1 Correlation with Secondary Resource
not pursuing
M
Michael McCool
There is no easy way to correlate the devices in the DNSFilter/Zorus portal vs the devices in our RMM that show the software installed (other sources can be used as well). If our RMM shows 800 devices with the agent installed, and the web portal shows 810 devices, how do we identify and correlate the count discrepancy? Right now, this is a manual task. This doesn't scale. What I would love to see is a free-form "asset" field that we can populate with whatever data we want. This needs to be assignable as part of the install process as part of install command line as well as having the ability to update this value after the fact from the endpoint itself (command line tool or registry entry--something accessible by script). This "asset" field would also be visible in the API.
With this in place, we could populate this asset field with the RMM device identifier, and then run a script against the API and can have a true 1:1 correlation between the devices in our RMM reporting the software installed vs the endpoints in your portal.
Additionally, it would be useful to be able to flag endpoints in the API and then review those flagged endpoints in the web portal. This way, we could review the endpoint status and determine if the endpoint should be deleted or if other actions are more appropriate. FWIW, I performed a variation of this in the Zorus portal by disabling the endpoints in the API for the ones I wanted to review. I was able to review these all at once and it took the administration time for review from 5 hours to about 15 minutes since I didn't have to waste time looking up each and every endpoint individually.
Minetta Gould
marked this post as
not pursuing
M
Michael McCool
From the links you provided to documentation, it appears that multiple tags can be set on the same device, so we could have one tag with the RMM device GUID, and another set via the API so we could review devices of interest. Can we select tags in the web UI so we can see all the devices with a specific tag in a single list and take bulk actions against them? Most of the time, we would be verifying that they are offline and delete them from the portal, but on occasion, there would be an online device that we would then need to determine if our RMM agent is broken or if the device was not offboarded properly.
It's good to know that the DNSFilter product has most of what is needed to support 1:1 correlation, but not all of this same functionality is available on the Zorus side. Since we our a Zorus customer originally, I would need support for this on their side.
Minetta Gould
Michael McCool you’re exactly right! Multiple tags can be set on a single device, and in the Roaming Client dashboard you can filter by those tags to view specific device groups. From there, you can take bulk actions like delete, uninstall (supported on current Windows agent versions, but not macOS or mobile), or update policies—all directly from the UI. There's a ton of other filters available to narrow the search too, like last seen traffic.
It sounds like this workflow may cover what you’re aiming for on the DNSFilter side. Can you confirm if this meets your needs so we can close this request? If not, happy to hear what’s still missing and keep this open for consideration!
M
Michael McCool
Minetta Gould - In the most recent webinar, we were directed here to submit feature request for Zorus and DNSFilter. It seems like DNSFilter has the functionality required to perform 1:1 correlation between itself and the RMM, but not all this functionality is present on the Zorus side of things. That is still needed.
Minetta Gould
Michael McCool Glad to hear DNSFilter will meet your needs once the migration from Zorus is complete, but adding this capability to Zorus isn’t something we’re pursuing. Appreciate you taking the time to clarify your use case and confirm how you’re using these tools!
Minetta Gould
Appreciate you outlining your workflow—this is great context.
The functionality you described is already possible today through the API. You can use either a
friendly name
or a tag
to identify and correlate devices, and both can be updated per Roaming Client via the API. Tags can also be set during installation if that’s easier for your setup.That should achieve the same correlation and automation you’re after, but if this doesn’t fully meet your business need, let us know what’s missing so we can better understand your scenario.
If we don’t hear back within a week, we’ll assume this solution works for you and close the post.