Currently if a guest wants to remove a host from a session, they will right click the tray icon and end the session.
When a host joins a access session, there is no way of kicking them besides just stopping the services or uninstalling the agent. Feature request is for the ability to kick a host from a session without removing the agent.
It would be nice for the guest to have a button to disconnect the remote session, similar to have Automate's VNC disconnect now.
Currently, the only way to end a session is through the Control server.
Add the ability for a remotely accessed computer user to end the session.
In other words, if I am accessing a remote user's unattended computer, and they sit down in front of it and want to use it, there is no way for them to end my session short of uninstalling the agent or disabling the service--both unnecessarily cumbersome ways to simply be able to kick a remote user off their machine temporarily! Most other RMM services have this feature, seems strange for Screenconnect to lack such a basic feature. Thanks!
We have users that work with confidential data and need to be able to disconnect the support engineer when working with this data. They need to be able to issue a disconnect and have that revoke the permission token that would allow the engineer to reconnect without the user granting permission again.
Can an option be added for the end-user to have a disconnect option? We use Access and push the Agent via SCCM. An option to right-click the screen connect icon and have a Disconnect or Disconnect Remote User - something along these lines as an extra security measure.
Thanks!
This has been implemented as 'Require My Consent' here:
Enable a guest to require consent - ConnectWise
It enables a Guest to right click on the system tray icon to require consent, and in the case where a host is already connected, selecting the option will forcibly remove the Host from the sessions.
This has been implemented as 'Require My Consent' here:
Enable a guest to require consent - ConnectWise
It enables a Guest to right click on the system tray icon to require consent, and in the case where a host is already connected, selecting the option will forcibly remove the Host from the sessions.
As you can see users are desperate to get rid of techs, as they often forget to disconnect.
I see such messages more often than not.
Please finally allow users (guest) to close/terminate any session.
thanks,
Stefan
I too would like to give my clients the option of disconnecting a session if a tech forgets.
I too would like to give my clients the option of diconnecting a session if they feel uncomfortable
I have done this and they end up holding the power button down thinking something is wrong with their keyboard :(
It's not something I use frequently and I'll inform the client that I'm enabling that function so that unware staff don't try and use the computer I'm running maintenance on.
Luckily I've been cautious with my use of it so I haven't had anyone just shut down the computer like that.
There is already a timeout function on sessions if you leave them unattended for too long.
I feel like this conversation is still moot because as the SC user you can just disable end-user inputs which would prevent them from ending the session anyway lol. Admittedly I don't like function however if I'm in the middle of a delicate update and I don't want the end-user just exiting out of what I'm working on I'll enable the disable inputs function.
I have done this and they end up holding the power button down thinking something is wrong with their keyboard :(
It could also give a 10 second wait to actually kick you off so IF you are logged in with admin priv somewhere.. and a user tries to kick you off, you have 10 sec (adjustable in settings) to say no.. but if this still would allow a rogue sesion that you forgot to log off from to be ended remotely...
There is already a timeout function on sessions if you leave them unattended for too long.
I feel like this conversation is still moot because as the SC user you can just disable end-user inputs which would prevent them from ending the session anyway lol. Admittedly I don't like function however if I'm in the middle of a delicate update and I don't want the end-user just exiting out of what I'm working on I'll enable the disable inputs function.
It could also give a 10 second wait to actually kick you off so IF you are logged in with admin priv somewhere.. and a user tries to kick you off, you have 10 sec (adjustable in settings) to say no.. but if this still would allow a rogue sesion that you forgot to log off from to be ended remotely...
The option to close the control session is only enabled for support sessions. With the GDPR it is a requirement for the users to be in full control of their data. This includes remote sessions and our customers need the option to have their end users cancel out of an access session as well.