I have an admin user who is actually manually stopping the Screenconnect service. I was just encouraged in a support ticket to put in an enhancement request for this very thing. It's discouraging this has been sitting here for 6 years. My compromise on this would be as follows if the user tries to uninstall through the control panel, require a password but also having a command line utility that allows uninstall without a password. When this happens, it is a big waste of time for us to fix it through LabTech. Usually, the user is unaware that the software was installed by us in order to support them (despite the onboarding package they receive) and they are under the impression that it is some frivolous program installed by one of those commonly used programs that installs junk along with it (not pointing any fingers) and they remove SC from their computer. Furthermore, privileged operating system access for a user should not impede our ability to support that user. For most clients, limited access is transparent but for most users but for some, admin access is necessary. If we did that, we WOULD be using best practices but we also may not keep our clients. However, we cannot revoke administrative access from clients that own their infrastructure. That is normally how things would be done.
0 kommentar(er)
