Hope this helps.

https://forums.mspgeek.org/topic/6856-lock-server-on-connect-lock-server-on-disconnect-triggers/

Please... (THIS)  No more sending the session to another technician. 

For now, the only way to do this is with the RMM+ plugin in control. 

The screenconnect plugin is built by the Automate Team, here's that enhancement request. Help us annoy them.

https://product.connectwise.com/en/communities/5/topics/12580-terminate-control-session-when-automate-agent-is-offboarded-or-retired

Agree, it would be nice if both the screenshot and video recording only took effect on the monitor you are viewing. Right now, viewing the video is not practical when our clients have 4 to 5 HD monitors visible at once.

Just to clarify this part. (personal opinion)

Essentially giving users rights to run scripts on behalf of other users that maybe logged into the system. --> This part is expected since the computer is unlocked but having the ability to run scripts with the screen locked is not preferred. 

Meaning everyone with TransferFilesInSession permission essentially has backstage access. 

I thought i would post an update on this. Last week I had recommended turning off the audio feature but I'm now recommending to leave it enabled but to just disable the select mode. Last week I was too focused on just turning it off and ensuring compliancy.

By doing the following, you will ensure that existing users will be able to mute their microphones while users that use the clickonce run won't have the old settings cached along with the users that not have reinstalled since they will still have the ability to change the microphone settings. This also helps allow the users to mute incase someone bypasses the app.config since it's optional. 

1.) Make sure your default Sound Mode is set to Silent.

2.) Disable the Sound Capture Mode.

3.) Force all users to reinstall the ScreenConnect Client and also clear out their clickonce run app cache. (good luck)

4.) Restart all the screenconnect services at your customers sites to force reset the All Mics to Silent. 

In the end it should look something like this. Select Mode is grayed out but the Microphone Mute button is still clickable. 

Here's a better diagram of what happened.

I guess our biggest concern was not realizing that users did not have to explicitly share their MICs and also not realizing that the toggle switch stays active until someone restarts the screenconnect service at the customers site. In our case, a prior support session had left the MICs active.  

Hope this helps others learn from what we encountered. I'm also hoping that we'll be able to turn this feature back on in the future once there is a setting to mute the microphones on connect (by default). 

I think the part that bothers me the most is that the bitmask settings are optional. Meaning they are controlled on the client end not the server end.. These are not really permissions and seem optional at best. 

What's worse is that a tech savvy user could just reenable the any bitmask settings they want if they found the app.config file..

bingo everyone gets access to the audio and any other features you turned off.. NICE.. 

We just tried changing the bitmask settings and every thing looked fine but users that used the clickoncerun app will have the bitmask settings cached meaning they can still access the microphone and users that have not reinstalled the screenconnect client can still access the microphone... 😕  while other users won't be able see or mute their microphone. 

Here's an example of what most of the redhad systems we connect to look like.... big black nothing. 😥

So, we control into a windows box and then SSH into these machines and or control them from vsphere (if possible). Now once someone has connected to vsphere and pressed the ctrl+alt+F2 then anyone can remote into the server again until its next reboot.

Would be cool if we could go direct and send the CTRL+ALT+FUNC key. 

I know some of you (like me) are just looking for progress or maybe a hint of progress. I wanted to give you some insight on this as CW had posted on a forum a couple months back asking for feedback on setting the resolution from control. I was going to post the URL but it has already expired. 

This may or may not relate to the following post but i hope it helps.