ReliefPC
Active Contributor
Joined 11 months ago
User Profile
User Widgets
Contributions
Kill Stuck Sessions
There are times when an Unattended session gets "stuck" with GoTo Resolve. There is no way to kill those sessions, meaning you can't otherwise connect again to the machine. This can sometimes happen if you're already connected and the remote machine loses and then regains connectivity. The session remains stuck for hours and you cannot reconnect. Rebooting the remote PC does not help. The only resolution I've found is to start an Instant Support session with a person on the other end, connect to that, uninstall the Unattended access application, reinstall it, re-verify the PC in the Console, and then connect to the newly-added machine. During your new connection, the old session remains stuck for hours and hours. It feels like the "stuck" session is on the GoTo side, in their cloud. We should be able to kill those or report that they are no longer active.Re: Zero trust - prompt frequency
Related -- we should be able to set the Zero Trust to a custom length of time..........and this setting SHOULD be respected. I have mine set to once/week, but I am frequently asked again, much more often than a week later. This setting doesn't seem to mean much, but it should. In our environment, this does not need to be requested as often...once a month would be plenty.138Views0likes0CommentsAdd Option to Remove 5-Minute Countdown After Resolve Session
My team is not sure why there is a 5-minute countdown timer after disconnecting a remote session, but it has caused issues, especially when sessions are connected from Android. For whatever reason, sometimes that 5-minute countdown with the "Close" option does not show up on Android. Because of this, you are not able to reconnect to the PC until the connection times out, which can take a long time (sometimes 30+ minutes). Since we do not use this 5-minute option to add any notes (we have a separate ticketing system where notes are kept), we'd like to be able to have disconnected sessions close immediately, without the additional click. Separately, the "stuck" session should be able to be terminated/killed if there is one that should have been disconnected but was not, for any reason but the above Android reason included.59Views1like1CommentConnect to User Session vs Console Session
TL;DR Unattended access doesn't work if the user you want to monitor/interact with is connected to the unattended PC via RDP. LogMeIn Central has an option after connecting to a remote computer via the "Terminal" dropdown box shown below: Using this dropdown, you can choose either the "Console" terminal session or the "User" terminal session. This is especially useful if the user you are trying to connect with is already connected via RDP and you need to interact with their session to help them with something or install something under their user profile (our users do not have local admin rights).