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.
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.
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.
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