Prompt to lock remote computer when disconnecting
When leaving a remote session, we would like to have a prompt ask if we want to lock the remote computer or leave it unlocked.
When leaving a remote session, we would like to have a prompt ask if we want to lock the remote computer or leave it unlocked.
In teamviewer there is an option that the remote PC only gets locked after the end of the session, when it was locked at the start of the session. This is super useful if you connect to workstations, where people are working and asking for actual help. At the moment they always have to relogin after I end the remote support session.
Please implement that in screenconnect/control as well.
Partner asks to add more granular control over which machines auto lock on disconnect. Maybe do this off of session group or something to make that work.
This extension is now available in the Extension Browser.
Forum post: http://forum.screenconnect.com/yaf_postst10827_Extension--Selective-Lock-on-Disconnect--6-3.aspx
I say let us choose. Have a setting in app.config that gives options to always lock, never lock, and prompt on exit. Something like that. But we definitely need an override in one of the dropdown menus. Because I would like to have it auto lock, especially if a session times out, but if we've been on the phone with an end-user and disconnect, I'd rather their session not lock on them. This is the way TeamViewer had it set.
We would really like to see this - and YES - as a pop-up on the host session when exiting! It NEEDS to be intrusive. Since you haven't implemented the ability for separate app.config by groups / machine types, I can't set the policy to auto-lock on disconnect because we do NOT want this to happen for workstations; but I NEED it to be persistent and urge the tech to lock servers on disconnect.
I'd like access sessions to prompt the host for lock on disconnect rather than just auto lock at a minimum. What Prodata suggests would be ideal, but in the short term if we could get a compromise that would be great.
The users need to log back in currently when we're done helping them, and we may have to disable the lock on disconnect due to this. I'd like to not rely on technicians locking desktops, but I'd also like to keep end users happy.
This is really a no-brainer and a huge miss for the devs. Automatically locking the system when a control session is ended is obviously needed as a basic security feature. Leaving the remote machine wide open and accessible if a session is ended due to a power or network issue or something exposes us to huge potential for problems.
I am very surprised that this in not built-in like it is with pretty much every other remote control software I have used over the years.