Our group has wrestled with this for several years. As one commenter wrote, this action of logging off the user after ending a session, even on an unattended device, is by design. Keep in mind that LogMeIn Rescue’s intended purpose is as a help desk service, not for an admin access. As such, it will break and log off each session at end. When I discussed this with the company they mentioned that their was an add-on product available to maintain the session.
A possible, but still unreliable, work-around is as follows:
1) Create two accounts on the unattended access computer.
2) Log into account A, then switch user and log into account B.
3) Start any processes needed.
3) From account B, switch user back to account A.
4) From account A choose to pause the session.
5) Unpause your session first, then switch back to account B and work with the running processes.
On a Windows machine, switching users usually allows any running processes on the switched from account to continue. The above does that using LMI. However, please test this before relying on it. We have found that, for unknown reasons, sometimes it doesn’t work.
