We are finding that Rescue is logging the desktop session out of Windows Server 2008 when we disconnect from remote control. The client needs to have the session remain logged in - is there any way to prevent the forced logout?
We have not fixed this, because this is by design.
We deemed it safer from a security perspective, that when you disconnect from Rescue we will return the User account you connected with to the state it was in prior to the Rescue Connection.
The workaround for this is that when you connect to Rescue with User A, you then need to switch users to User B. Everything you run under User B will continue running whenever User A disconnects.
If you submit your feedback to our ticketing system, we can submit a feature request on your behalf. The development team also does view these forums.
has there been any resolution or fixes to this issue? this seems to be a pretty huge oversight on LMI's end.
btw, the fix you suggested w/locking the server and then exiting DOES NOT WORK. when i log back into the server the session basically kills my batch file thats supposed to be running in the background.
This is on a Windows Server 2008 R2. seriously, LMI hasn't fixed this problem after over a year of it being reported? Do i need to put in a ticket to get this resolved? i'm considering other solutions that can properly do unattended support on a server.
Hi,
I noticed the same thing recently when wanting to leave an app running after I ended my session.
The only work around was to lock the system before ending the rescue session. The app will still run behind the locked screen, but will still need CTRL+ALT+DEL to unlock and carry on.
Hope this helps.
Chris
Has anyone come up with a fix for this? I have a bunch of Windows 2008 servers that I have setup for unattended access. I can log in but when I disconnect the current session logs out. When I reconnect I am asked to press CTRL+ALT+DEL to log in. This will not work for me since my application requires that it be running in order to collect data.
I have only seen this behavior or Windows 2008 servers. I haven't tested this on Server 2008 R2.
Any help would be appreciated.
Thank you.
Yeah they say if you log the pc in with LMIR it will log it off when the support session is closed.
For me on my LAN it happens no matter what. I think this issue has been brought up a few times here you should search for it.
I also find submitting a ticket a lot more helpful than this forum.
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!
