0
Not a bug

​AlwaysEndSessionOnExit can be defeated

pfp 3 years ago updated 3 years ago 2

If the Host (support tech) ends task on ScreenConnect.WindowsClient.exe they will be disconnected from the session but the session will not be ended. The guest is still connected and the session will remain open indefinitely for a tech to reconnect. This is the same as choosing Disconnect before the AlwaysEndSessionOnExit option was implemented.


How do I know - my techs are doing it.

Version: 6.2.12684.6281

ConnectWise Control Version:
19.3
Server Affected:
Host Client Affected:
Guest Client Affected:

Answer

+1
Answer
Not a bug

Good morning,


What you've described is correct -- if AlwaysEndSessionOnExit is true and a host forcibly kills the WindowsClient process (e.g., via the task manager), they will be disconnected from the session; since the application is forcibly closed, it will not pick up on the form closing event, and the session will not be ended automatically.


As such, I am marking this thread as "not a bug".


Cheers,

Ben

+1
Answer
Not a bug

Good morning,


What you've described is correct -- if AlwaysEndSessionOnExit is true and a host forcibly kills the WindowsClient process (e.g., via the task manager), they will be disconnected from the session; since the application is forcibly closed, it will not pick up on the form closing event, and the session will not be ended automatically.


As such, I am marking this thread as "not a bug".


Cheers,

Ben

Ok, it's working as designed so technically it's not a bug. I get that but it's a bad design.


Below you will find the "Answer" to this request

http://product.screenconnect.com/topics/629-automatic-support-sessions-end-on-inactivity/#comment-2694

"Planned...sort of. We've heard similar requests and we're implementing a configurable option in 6.0 or 6.1. Expected behavior is to not present the option to leave support sessions open and just automatically close once a host exits a session. This will not be permission based as it is being implemented in the spirit of being a compliance measure, which shouldn't have any "loopholes" once set by an admin on the server."


Well, this is a pretty big loophole.