Endpoint Administration 1:1 Correlation with Secondary Resource
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.