Your comments
This fix is in the 6.0 update scheduled to be released this week for On Premise and Cloud. The enhancement is done and tested so I'm closing this issue. We'll announce the release in the forum output stream: http://forum.screenconnect.com/yaf_topics9_Output-Stream.aspx .
The two issues are unrelated. Role based permission controls which machines have consent. We are putting in an option to make the consent reprompt after a host has been disconnected after "x" amount of time. It will be included in a 6.0 update to be released soon. This is the issue tied to it: http://product.screenconnect.com/topics/547-allow-for-a-choice-between-legacy-consent-method-and-the-newest-one-time-consent-until-restart/ . We'll update the post when it's ready.
Sounds more like you're wishing to issue a Host Login with view only creds. Are you an on premise customer? Does access have to be set to time interval?
The UAC Prompt has a 2 minute timeout after which the operation is cancelled automatically without user interaction.
After 2 minutes you should regain control of the session, if this is not the case please submit a ticket to support, but that is the behavior from our testing..
We are looking at ways to notify hosts that a guest is not an admin: http://product.screenconnect.com/topics/126-notify-host-on-connection-when-support-session-not-running-in-service-mode/ in a 6.x release.
Making the option configurable in this manner doesn't address the overall issue. There were a lot of requests to make consent survive a reboot of the machine. Dev is currently looking at alternatives that should work for both use cases. I'll try to update this post when I have new information.
This request did not make it into 6.0. Where still working with some UI elements, but it should make 6.1.
Customer support service by UserEcho