+88
Pending Review

Access session guest ability to kick host from session

Larry 5 years ago updated by Markus88 1 month ago 26 4 duplicates

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.

Available in Version:

Duplicates 4

Pending Review
+7

Guest can kick host from a "Access" session is exactly what we need.

We need it for german law and concerne compliance against staff monitoring.

Our end user don't have permission to end or deinstall the service, so the "End" option in the tray icon is the only way for us.

+3

It is required that the EXIT option is enabled in user sessions, this is imperative for sessions for security reasons

+1

We are currently unable to deploy the client as the business demands they be able to have control over the session. We are trying to stop the practice of sending links to users. Access sessions take care of this part as we can also require consent. We just need them to be able to opt out of a session at any time if the need arises without killing services or uninstalling the client. Would be of great help if this could be added. 


Thanks,

Oliver Walker 

Yes there needs to be an option for the customer to kick out the session.  I chatted with these guys and they said there's an option to make it so that the customer has to let someone in to the session.  But this wouldn't work if access is needed all the time.  So how about a way for a customer to be able to kick out the session for a certain number of minutes, so if someone is working they can be sure nobody will gain access for that amount of time?

+1

Ideally it would be best for the Admin to be able to turn this feature on or off. The guests ability to not end a session is part of the reason we moved to SC. Previously when we were with GoToAssist the guest could kick us out at any time and they would even when we were running maintenance on the computer.  People have a tendency to believe what they are doing is far more important that what we are doing so they kick the technicians out of the session. So having them not able to end the session is helpful for what we are doing. 

+1

We are migrating to ConnectWise Automate and realized the user does not have the ability to disconnect the tech in ConnectWise control.  This appears to be an important feature which was missed and we hope it will be implemented soon.

+2

This feature is greatly needed and could prohibit the use of this product for many customers. I highly recommend adding this in as an enhancement and allow the administrator to decide whether it gets enabled or not. It should at least be an option.

We need this feature too and we need a date for the feature !!

Logmein - Teamviewer have already this feature. It's not a big deal for to implement this feature.

Thanks

+1

Hello...  Yes this should be a must have as it poses a security issue with management.  Please give the end users the ability to close the session once connected if

+3

This is a need. Original submission for this was 3 years ago and it is pending review. What is the timeline for review?

+3

There are many reasons why the host may not have disconnected, the client has very little recourse to drop the connection, Task manager to kill the session is not acceptable method for a client to disconnect.

+1

Kick host from session, but leaves the guest alive on the host page. We need this feature too. Is this on your road map? When can the community expect the introduction of this feature? (Now since three years unter pending review.)

+1

This is a requirement for us for compliance for some customers. They work with data only they are allowed to see. This is an absolute must for us to have.

For us it is a requirement as well, also based on german labor and dataprotection laws.Please add the functionality for the end-user to disconnect a technician from his or her computer.

+1

This is exactly what we need. We work in Switzerland and need this feature by law. Also it common sense... How can it be that an end-user working on a Terminal Server is not able to kick out the support person at the other end???!!

We were about to commit to Connectwise but the lack of this necessary feature may well be a deal breaker for us.


We will now have to consider other options such as TeamViewer or GoToMyPC.
+1

Our EU company is also now in this as well..Previous because our customers were outside EU it wasnt a concern with permission but not the case now.. Please can this be made a feature? It doesnt need to END the Access Session but just be able to kick off the technician.

+3

Maybe it helps others here. We have for now declared it as a security feature, since it prevents users from kicking out a technician while the technician has for example an admin-prompt open over remote.

If the user were to kick them out in that time, they could do whatever they want and get access to sensitive information or systems. Without that option its in the responsibility of the technician.

Nevertheless it would be great to have the option to enable it upon request.

+1

Hi, Is this in development yet?

+1

4 years and not implemented? This seems so basic to have.  Once in a Zoom meeting, I am not beholden to the meeting organizer to leave it, or stop sharing my screen.  Even having the ability to blank out the screen on the host-side would be a good half-measure to hide private information while on a support session.

+2

This is what I'm paying for?

I'm supposed to be able to connect up to three simultaneous remote-control sessions and I only have two open sessions, so this shouldn't even matter - but I have no free sessions left, and the only way I can get in to end the existing Control sessions right now is to... launch Control. Except that that doesn't work because I allegedly have no licenses left. I was the person who kicked off the original sessions when I was at the client's place, 30 minutes from here (one way); I can't go out there now, I'm not going to ask the client to go to his office at almost 10pm, and I'm irritated. 

Yeah, this situation was my fault; guilty as charged - but the fact that FOR YEARS, you've basically ignored requests to create a feature that would ALLOW ME TO FIX IT MYSELF, is a huge problem. And *that* ISN'T my fault.

Why hasn't this been implemented yet, and why should I continue to pay ConnectWise for this service?

+1

I don't think any ConnectWise employee will ever read this forum. How else can a feature request after FOUR YEARS! still have the status "pending review". There are also never any statements from any ConnectWiese Admins to this request.
That's really sad, because I truly like ConnectWise Control.

I agree. ConnectWise should be embarrassed. Such a basic function which we shouldn't even have to talk about. Every other player in the remote control market has this functionality. I can't understand why CW doesn't do anything about this, at least explain why they aren't implemeting it, but as David G. said, most probably they aren't paying any attention to the community and/or their users.....

So, it turns out you CAN kill live sessions. This isn't really documented anywhere useful. And I don't know if my "I pay for three concurrent sessions but can only use two" problem was fixed. I should probably check.

I know that guest sessions can kill the session, but how can a host kill an access session?

There is no option to end the session when right clicking on the tray icon (when the Control Agent has been installed on the host) except by uninstalling the Agent (which requires admin privileges which our users do not have and which leaves the end-user (host) without an agent and therefore no more remote support is possible!)