Thanks for your quick response ! vidmate instagram video download
If you're referring to a setting in LogMeIn, no, there is not. I have been told by LMI representatives that the auto logoff is built into the application for security so that no one can access the machine under the remote LMI user's session.
If you're asking about Windows switch user, you would just need to have two accounts on the machine, then click on the Windows start icon then click on your currently logged in name which will display other available accounts.
I assume there is a setting that prevents this.
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.
>If you're transferring 200GB over LMI, the service isn't your problem...
Heavens no! Don't give the developers any more ideas! They are sadistic. The fact that this "feature" still exists after a decade should be proof enough!
Rant time...
These transfers were local exports to a NAS on the local LAN. Nobody want's to babysit a long process, but apparently the developers of this software seem to have psychic powers or psychotic motives, maybe both. The slightest network instability can close your session and log off the host forcefully terminating all important running processes. You'd think that a PowerShell window running a long process would be important enough to prevent LMI from crapping on your evening. Nope. LMI happily does a forceful termination of all running processes and logs off your session immediately. Most notably when using the technician console while connected to a mobile hostspot or public WiFi. Don't do this. Really don't.
On a side note...
Anyone else looking for an alternate product not yet gobbled up by LMI Inc, check out ConnectWise Control aka ScreenConnect. The latest version is competitively priced and doesn't need an ongoing subscription if you setup your own server, very easy to do btw. Licensing is a little different than LMI, you can have unlimited unattended computers, but need an additional license for any simultaneous controlled connections,, LMI lets each technician run 10 simultaneous sessions, Control can only do one session per license. I still use LMI for some userland stuff now and then and keep it as part of my kit, but don't rely on it for anything critical. Sad really. All it needs is a simple check box in the configuration that says ( [x] Keep remote sessions active when disconnected from technician.) then actually obey this option. It can't be that hard. If the developer really has psychic powers and knows that it is the user's desire that he wants sessions forcefully logged off, then provide some more granularity with these options such as,:( [x] Do not logout session while tasks are actively running in the foreground. ) { [X] Force log off if remote session disconnected for longer than nnn minutes. ) , I think this would satisfy the psychic developer and the user that had his mind read without permission.
If you're transferring 200GB over LMI, the service isn't your problem...
I have to run a 3 hour long test. Going to try with auto mouse mover. Wish me luck.
Welp, half way through 2019. Preparing a 1TB migration for overnight transfer and cannot keep the server logged in. All processes forcefully termintated. I actually have to use TeamViewer for this one.
This is the dumbest thing I have ever heard of! For professional remote access software to not be configurable by the purchaser of the software is ridiculus. I will look into your competitors and quit this service as soon as I find one without such stupid policies.
If you want to keep my business, let me configure the software I am paying you for.
Hello!It is by design because the average case is when the technician logged on to a locked customer account and finished his job, he should not leave the account logged in. The user don't have to be there, because it was unattended support session.
It's now almost 2016 and this is still an issue. Just got off the phone with support and was told that this was done by design and that there is will likely be no effort made to fix it.
Other than to make the product crappy I can't see why anyone in their right mind would design such a feature.
I'm not sure why this issue hasn't been resolved it. It can't be that hard of a feature to add and is the most annoying thing about LMI rescue.
I would like to add my voice to this issue. Please add an option that allows a LMIRescue technician to end an unattended session WITHOUT logoff. I find myself using LMIFree to manage servers that require a user to be logged on for certain critical processes to run correctly. I would much prefer to use the full-feature set of LMI Rescue.
By the way, I am very impressed with LMI Rescue. It is a very effective tool for my small business IT company. Just need this one flaw fixed. Perhaps replace it with an automatic lock if this is a security issue.
Thank you
This happens with us on servers with unattended access! Very frustrating & lots of angry clients
Nearly two years later and this problem still persists.
I was transfering a 200GB VM over the weekend only to have the session terminated and logged off!
My week is now fscked! I'm going to scream now and go home.
Same issue here. Having major issues with this logging off. I do not want the rescue software doing anything automatically, that's my job.
Please resolve ASAP.
Thanks
Boyd
I'm having the same issue. Very annoying. Especially when I am trying to diagnose a problem with a very long running process.
I assume there is a setting that prevents this, but haven't found it yet.
If you found this discussion useful, why not register/sign-in? It only takes a minute to share your feedback, ask a question, or vote for a new feature!
