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.
Any update on this being on the roadmap, this is sorely needed. Has anyone found a workaround for this?
Why not just not use access? and instead, just use the support function?
Any update on this being on the roadmap, this is sorely needed. Has anyone found a workaround for this?
I'm wondering how many releases there has been in FIVE YEARS of software development as to this not being an option for an administrator by now. NO excuse on this one guys. GET ON IT. Or at least have the courtesy to say why you won't. I can only imagine the response if I told any of my clients to wait 5 years for a fix. (this IS a fix).
Don't get me wrong, you've done a great job with Connectwise overall.
And, if I've missed something, my apologies in advance - but otherwise this is honestly pathetic.
I'm wondering how many releases there has been in FIVE YEARS of software development as to this not being an option for an administrator by now. NO excuse
This, along with the pathetic, complete lack of branding/customization features for people who use ConnectWise Control in the cloud... those are the two primary reasons I'm ditching Control at some point soon (when it's practical to do so).
Don't make a forum available for customer feedback if you're not going to listen, ConnectWise.
From a technical standpoint, Control is pretty awesome, but I can't allow a company that refuses to address security issues to have any kind of access to my computers, or my clients'.
Pathetic.
I'm wondering how many releases there has been in FIVE YEARS of software development as to this not being an option for an administrator by now. NO excuse on this one guys. GET ON IT. Or at least have the courtesy to say why you won't. I can only imagine the response if I told any of my clients to wait 5 years for a fix. (this IS a fix).
Don't get me wrong, you've done a great job with Connectwise overall.
And, if I've missed something, my apologies in advance - but otherwise this is honestly pathetic.
I have a customer who just told me today that I have to uninstall control off of all machines unless he has the ability to kick an agent off. Why is this not an option?
Giving end users on an Access session the ability to kick the host whenever they want should be an available feature. This is a security risk that really should be handled. I strongly request this feature be added.
What I really would like which maybe it is possible and if someone can tell me how to do it. I am the admin in control but I can't seem to figure out how to kick another technician that is remote using the webstie on a computer I can't access and they have a session going and they walk away from the computer. I can't seem to figure out how to disconnect him from the host.
JBody, You can click on the X next to a users active session and end their connection.
What I really would like which maybe it is possible and if someone can tell me how to do it. I am the admin in control but I can't seem to figure out how to kick another technician that is remote using the webstie on a computer I can't access and they have a session going and they walk away from the computer. I can't seem to figure out how to disconnect him from the host.
As far as I know the only way to do that is to reset all open sessions.
Exactly. The part where the user disconnects the supporter with elevated permission is what we currently use as reasoning why the user can't close the session on their own...
What I really would like which maybe it is possible and if someone can tell me how to do it. I am the admin in control but I can't seem to figure out how to kick another technician that is remote using the webstie on a computer I can't access and they have a session going and they walk away from the computer. I can't seem to figure out how to disconnect him from the host.
I believe it should be an option. I also agree with the post above that we should be able to turn it on and off. The reason I say to be able to give or take away that option is because What if you are logged into the person computer with your account which has domain admin rights and the user just disconnects you now they have a computer that now has full access to everything. including changing your password or just creating an admin user for themselves If they are smart enough.
Exactly. The part where the user disconnects the supporter with elevated permission is what we currently use as reasoning why the user can't close the session on their own...
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.