Currently the consent requirement is all-or-nothing when accessing ScreenConnect/Control via LabTech/Automate. We are required to keep this consent in place for accessing end user computers, but this is a huge roadblock for us when trying to access servers. If LabTech were ever able to resolve the known issues RE their RDP tunnels crashing constantly (still an open issue, 6 months now) this would not be such an issue as we would just use RDP. However we have much more faith in the ScreenConnect team to help us out with an integration enhancement that would allow us to apply this consent requirement based on other factors such as whether or not the guest machine is running a server OS, for instance. Right now we have to apply the consent requirement to the default All Sessions group which is what LabTech hits when it connects us to a machine.
Customer support service by UserEcho