-
Why am I unable to view historic device information; telemetry is discarded once a device goes offline, which is commonly the state a device finds itself in before a call is made to the service desk, at which point the RMM is not a useful tool (because no previously-captured and potentially useful data has been retained). I guess you don’t have the storage capacity for seconds-old data?
-
Why is it not possible to search for client devices by IP address, last login, or any of the myriad other details captured for devices while online? I can see why discarding such data as a matter of course (why??) might be problematic, but this information is not searchable even while relevant devices are online. The only searchable information is either arbitrary or inconvenient (I can search for a fabricated ‘user’ or for the host name, which does not necessarily match up with the asset number assigned to a device. I guess this would be redundant as you don’t retain telemetry anyway?
-
Why can I not arbitrarily re-label devices (say, to match their assigned asset number) except for servers? This would make searching an awful lot easier as our clients have been trained into providing their device’s asset identification when calling- this used to be convenient, but now it’s just another piece of information that cannot be conveniently reconciled with the device without referring to manually maintained tables outside of the service (heightening security risk and complicating something that should be childishly simple).
-
Is it possible to protect the agent from uninstallation, say by password or PIN, so that end users who must be provided with local administrative access to their devices cannot easily uninstall it? This is the closest to a feature request I will get with this list, but it’s a fairly obvious one, so I’m including it as a question.
-
Is it possible to amend Connect’s behaviour so that one can share ones screen while already viewing another rather than just sharing the same device’s screen with other parties? At the moment Connect just gets confused and cannot be opened to share while viewing a shared screen elsewhere (this is not complicated- I have at least three other remote control solutions that do this flawlessly, and I still resort to using them regularly when this should not be the case). Also, if I close a Connect window while I have more than one open, it will often close all open windows and disrupt anything I was working on through those (this is not consistent, so I presume it is an irregular hard termination following a crash during app exit). Why can’t I multi-task?
-
Why does the web portal not isolate sessions per tab or window? I can only search and work with a single device at a time unless I use multiple browsers (say Chrome and Firefox or Edge) otherwise each previously-opened tab becomes confused, even going so far as to show I’m working with a completely different machine while commands and data are being exchanged with a machine with which I interacted in a subsequent window/tab. The only other example I can find of a portal that has this weakness is anything Microsoft- until now I thought they were alone in being this awkward). Why can’t I multi-task?
Some of these are such basic and obvious features that I find their absence staggering. They should not need to be feature requests any more than a query about the absence of wheels should be a feature request for a motor vehicle. I have to be honest about this- I feel like a beta tester.
Oh, why not:
- Am I beta tester?

