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.
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.
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.
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.
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.
I was just trying to find a solution for this myself.
Ours isn't necessarily for compliance however this would be a incredibly helpful feature.
Hi Roberto,
Enabling SupportSessionExpireSeconds located in the web.config settings will help clear out disconnected sessions after a period of time.
What mean SupportSessionExpireSecond ? Host disconnected ? Guest Disconnected ? Host and Guest Disconnected ?
What mean SupportSessionExpireSecond ? Host disconnected ? Guest Disconnected ? Host and Guest Disconnected ?
The session will expire after a time period has passed where the host has been disconnected.
Thank you. it would be very useful to can control different expiration for: Host not connected, Guest Not Connected, None connected, so instead of cleaning manually.
Thank you
I've just set to 120, but the support session with no Host connected, does not seem to close after this expiration time
I Think SupportSessionExpireSeconds allow to close support session for which there is not connection. No connection of Hosts and no connection for Guest. My Request is for a new feature, as stated before, to allow automatic management (End Sessions) of disconnected parties situations, so one can End session after specific expiration time for: Only Guest Connected, Only Host Connected, Both Connected, Neither Connetced.
I'm not sure if this is the same issue we have. We don't allow "access" sessions but our techs have gotten into the habit of never ending their "connect" sessions thereby creating backdoor access sessions when these connect sessions are left running indefinitely. There is currently no way to end them automatically and I have to manually end these sessions every day.
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