In terms of the “closing the window, but it doesn't close” situation, I recommend submitting an idea in the Ideas Portal for that.
That being said, you can sort of ease the pain by having a painfully short idle before login time set for your users. That setting can be changed in the /login interface (as an Admin). Go to Management (lower left)>Security (second tab from the left at the top), and then scroll down to the “Representative Console” section (the 3rd section down), and there is a setting for “Log Out Idle Representative After”. Change that to something short, like 5 minutes, and you will probably have less issues with license quotas.
Also, I wonder if the Privileged Remote Access (PRA) may be a better product for you if you have lots of groups needing access at specific times? It may be worth reaching out to your sales/support team to ask about it. You may find it more fitting to your situation.
It sounds like you are already using License pools already which is probably the best way to manage what you’re trying to achieve (https://www.beyondtrust.com/docs/remote-support/getting-started/admin/licensing.htm)
In PRA, the ‘X’ does close the access console fully, whereas in RS, it only minimises the Application, but I think this would be a good Feature Request to submit, if it hasn’t already been submitted.
I also agree with @LayerZeroIssue, using idle timeouts could be a good way around this to free up licenses quicker when they are not actively being used.
<snip>short idle before login time
LayerZ we already use timeout to keep idle sessions short. I also have an email sent anytime someone is denied login. This email goes to the same group with restrictions so they know if one of their co-workers is trying to use a license.
@LayerZeroIssue and @Kenny Lyman the feature request I would make is to only count a license in use when the tech starts a remote session. Or a suspend or logout where the application continues to run but is no longer counted as a license.
Thank you both for the reply.
