There is an issue when reaching the limit of 200 Remote Viewer sessions. People leave themselves logged onto their session and sometimes come in to another session.
Reaching the 200 Remote Viewer session limit can happen as quickly as a few days because of the number of people pulling up sessions. Is there a way to Administratively kill individual sessions (Con IDs) manually or programmatically?
All Supported Windows Server environments and Windows Client OS environments
The Automation Point Remote Manager component on the server supports up to 200 Remote Viewer connections.
Unfortunately, there is no means of administratively or programmatically killing an active remote viewer session.
The best solution for this would be to recycle the Remote Manager service.
Automation Point users have already posted an IDEA for this enhancement request to the Event Management & Automation User Community.
Please vote for this IDEA on the community if you believe this would be useful, so that our Product Management team will consider adding a story for this feature to the product engineering backlog for implementation in a future release.