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.
Do you have the ability to filter computer by criteria like client and location?
Honestly, I'm dumping Control anyhow... for me personally, the ridiculous lack of any decent amount of branding (including the fact that you have only two or three options to customize YourNameHere.ScreenConnect.com) is the big deal breaker. But this issue with Access is also ridiculous, and ConnectWise could fix it if they wanted to, but all indications are that the don't care.
My company has set organization filters and we have enforced a proper naming scheme so we have no issues finding computers on either Access or Support. Connect Wise offers quite a bit for the low cost they charge.
As for the customization, there are some you can set, colors, logo, etc. The URL really isn't a bother since we set up our own reroute URL under our domain.
Agreed and as always a company could just make you agree to terms that say if so and so takes control of a PC we are not liable. I hope this gets some attention or at least a response from Connectwise. If this is a security risk in its own right then all I want is for Connectwise to say they are not doing it and this is why.
This is exactly why I don't want this function just flat enabled. It's an extremely slippery slope and the primary reason we left GoToAssist is because end users constantly just kicked us out.
They should give us the option to enable it, or not.
if they implement it they do have to have the ability for it to be turned off and on by the msp. Because if they just implement it that anybody can just kick the host off what about the times that you log into a computer with your admin privilege's and then the guest kicks you off of the computer now they have access to the computer and whatever your user has access to. Now said user starts deleting things or looking at files they should not have access to because said user got wind that they were going to get fired soon. now the company sues you because you gave that person administrator permission to things they should not have access to. You then turn around and sue connectwise because their software caused all this trouble.
So truthfully I can see why Connectwise is so Leary at doing this. You may say oh that would never happen to us or we would not sue connectwise if this happened. But you have to remember this software is used throughout the world not just in one country and their are sleaze balls everywhere that are looking to sue big companies for money.
Just my .02 cents
This is exactly why I don't want this function just flat enabled. It's an extremely slippery slope and the primary reason we left GoToAssist is because end users constantly just kicked us out.
True, but again I could play devil's advocate and say the same goes for the MSP itself. What if an engineer knew they were being let go at the MSP and so they remote into a finance PC and start stealing data and block client input and the client has no way to kick or block the host from connecting.
There are always measure that can be taken, such as if a user does kick you off the PC then the PC itself logs out or locks.
I have quite a few computers running on Support that I use the sessions for unattended access. The only difference is that the end-user can end the session if they chose.
Do you have the ability to filter computer by criteria like client and location?
Honestly, I'm dumping Control anyhow... for me personally, the ridiculous lack of any decent amount of branding (including the fact that you have only two or three options to customize YourNameHere.ScreenConnect.com) is the big deal breaker. But this issue with Access is also ridiculous, and ConnectWise could fix it if they wanted to, but all indications are that the don't care.
That doesn't work at all if you need unattended access, which I often do.
I already have plans to replace Control with Remotely, a relatively new, open-source remote control product that addresses all of my concerns with Control. I'm not just an IT professional, I'm also a developer, and my plans are to contribute code to the project at some point.
I have quite a few computers running on Support that I use the sessions for unattended access. The only difference is that the end-user can end the session if they chose.
That doesn't work at all if you need unattended access, which I often do.
I already have plans to replace Control with Remotely, a relatively new, open-source remote control product that addresses all of my concerns with Control. I'm not just an IT professional, I'm also a developer, and my plans are to contribute code to the project at some point.
if they implement it they do have to have the ability for it to be turned off and on by the msp. Because if they just implement it that anybody can just kick the host off what about the times that you log into a computer with your admin privilege's and then the guest kicks you off of the computer now they have access to the computer and whatever your user has access to. Now said user starts deleting things or looking at files they should not have access to because said user got wind that they were going to get fired soon. now the company sues you because you gave that person administrator permission to things they should not have access to. You then turn around and sue connectwise because their software caused all this trouble.
So truthfully I can see why Connectwise is so Leary at doing this. You may say oh that would never happen to us or we would not sue connectwise if this happened. But you have to remember this software is used throughout the world not just in one country and their are sleaze balls everywhere that are looking to sue big companies for money.
Just my .02 cents
We may have to go that route. This was a consideration, but a lot of times we need to access the system after hours, and the convenience is appreciated by our clients to be able to connect as needed. The issue is that the CEO of the company does not want access installed at all if they have no way to kick a host from a session. To be quite honest I do not understand why this is not a core feature of Access...
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.