Automatic Support Sessions End on inactivity

Avatar
  • updated
  • Under Review

Choice after how long an inactive sessions or sessions without connection from Hosts/Guests/Hosts+Guests must be closed (Ended). This leave a clean Screenconnect without many connections unused and administrator check to close long unused sessions.

Duplicates 3
End Session Based on Last Host Connection

For support sessions, we would like to be able to set a maximum time that an idle session can remain active after the host is not connected. Once that threshold is exceeded, it would be ended, and the session will no longer be listed as an available support session.


The scenarios is that, because our systems are impacted by PCI/PA-DSS compliance rules, we cannot permit unattended access in most situations. If an agent begins a support session and disconnects at the end of the day, they are able to regain unattended access the next morning (without getting permission from the customer to reconnect). We would like to set an option that ends the session so it can no longer be used once no host has connected to a session for X minutes.


Even better would be the ability to set this option at the user security level so that you could configure different groups of users to use different timeouts.


Alternatively, we'd like to be able to query the database programatically and send a command to end those sessions that meets this criteria

auto end support session after X days or period of inactivity
Avatar TTS

This could be implemented a few different ways but the basic criteria would be to allow the option to automatically END a support session after a period of time. That could either be a raw amount of time (regardless of activity) or a period of inactivity. The purpose would be to automatically clean out support sessions.

Develop automated way to end sessions that have been idle

Partner would like to have an automated way to automatically end sessions with machines that have been idle for xx days and to have a report included of the activity.

Pinned replies
Avatar
-1
anonymous
  • Answer
  • Planned

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.

Avatar
0
EvdZon

Unfortunately still not a possibility to configure this. Support asked me to create a feature request.

We would like to end/delete the session after xx number of seconds/minutes/days no matter the status.

As support staff doesn't end their sessions they remain open (and guest connected) but would like limit the time a support session is active to eg: 2 days and then end it.


Preferred based on the start date/time but if this can be a maintenance task at the end of the day that would be fine to.

The session should be ended as if you delete it manually so also ending the remote agent process.

Avatar
2
RaymondD

After 4 years and the feature is still not added?  Support just recommended I request this.

Avatar
2
Akira Y

Ending sessions upon exiting isn't flexible and there are conditions where sessions can end up being left open even if that's enabled. Being able to automatically end sessions without hosts after some amount of time is useful both as a complimentary setting to always ending sessions upon exit and as a standalone setting.

Avatar
0
Akira Y
Quote from anonymous

The session will expire after a time period has passed where the host has been disconnected.

This doesn't work, at least in the hosted platform. Sessions seem to disappear but they aren't actually terminated. A reboot of the PC or changing a configuration option that restarts the instance brings back old instances. People end up creating multiple sessions to the same guest. After an instance restart, there are multiple old sessions in the list. Other oddities include sessions that disappear and then reappear. Recent sessions are fine, just old ones are an issue. I'm currently looking at a session that hasn't had a host connection in 11 days. I have another that hasn't had an active host in 4 days.

Avatar
2
Colin Greene

Similar to the posts above it would be amazing for us if we where able to automate the closure of our connections after a specified period of time

Ideally we would want to be able to configure this automation based on user profile / roles as some of our users would need to be able to connect / disconnect to a clients PC over an extended period of time, sometimes this can be up to 1/2 weeks 

In most cases though after a short period of inactivity on the hosts end we would require the session to be closed, something along the lines of 2 hours would suffice. Or as Kent listed above, if no client or host is connect then the session is closed within 30 mins 

Avatar
3
Kent

I support this feature.    I have enabled the option to end a session on closing the last host - yet every day we end up with multiple sessions still working.

ie. This morning I came in to see 20+ sessions still listed from yesterday - some of them the clients had reconnected when they came into work this morning.   This is a huge potential privacy concern if they found out we were still connected.

We tried the force end on last host disconnect,  but this proved to be an annoyance as there were legit times you would disconnect (handing off to someone else, want to close and reconnect due to bad connection, etc).

What I want is to be able to automatically end sessions where no 'host' has been connected for > 2 hours  or where no one is connected (client or host) for > 30 minutes.

Avatar
0
Cody Arnold

Per the email 


" 1. Build an extension that adds a button to the interface for an admin to manually end sessions that meet the criteria set (host disconnection time, guest disconnection time, and host + guest disconnection time). These will be extension settings."

Avatar
2
Dan Scott

I'd like to add my vote for this feature.  Cleaning up the Host admin page is a pain.  I don't want to terminate sessions when the host exits as sometimes we need to come back to a session at a later time, such as if the client agrees a time with us when there machine is available, but we want to get the session established ready for then so we can join.


Ideally we'd be able to set a policy that says when a session has been inactive for 'x' hours, end it automatically, then our host support admin page would look a lot cleaner.

Avatar
0
anonymous
Quote from derekj

I would LOVE to see more customizable Database Maintenance Plan Actions (and schedule options) including more variables similar to what session groups have.  For example, "Support: Delete Host and Guest connections where session name = "Untitled Session" and no host (and or guest) activity for xx minutes/hours/days.  This would be especially important after the version 6.3 was released.  I'm now having to manually delete 20+ support sessions a day named "Untitled Session" because employees aren't scrolling down past the legit existing support sessions to delete them.

Hello,

If you would like us to consider this request please create another submission. This request is for allowing admins to set a time before a session is ended based on how long a host, guest, or host/guest has been disconnected.

Thanks. 

Avatar
0
anonymous
Quote from tatemike

I vote for fixing loophole, too (i.e. AlwaysEndSessionOnExit  being overriden by killing ScreenConnect.WindowsClient.exe, as mentioned by pfp).  I didn't test it myself, so can't vouch for the steps.

Thanks!

Hello,

If you would like us to consider this request please create another submission. This request is for allowing admins to set a time before a session is ended based on how long a host, guest, or host/guest has been disconnected.

Thanks. 



Top contributors

Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar