Servers logging out instead of locking when ending Rescue session

[dotbat]

For certain servers running 2003 and 2008, instead of locking the computer like it is supposed to when ending a session, it logs out. This is a problems because we have a few little applications that only run in an active session. If we have to remote into one of these servers, we cannot end the session or we will kill those applications. Once again, this is through LogMeIn Rescue. Thanks!

[w0mbat]

We had a similar issue happen with a couple of machines. The machine sessions were open be fore we logged in. We LMIR into the box and then disconnect. The disconnect would cause the session to lock instead of maintaining the session.

Ended up calling support who logged into the machines an sorted it by using another remote app to keep the session open when LMIR closed.

So I would recommend calling support.

Cheers

--Steve

[samebrian]

Do you have any group/local policy settings being pushed to the station regarding shutdown/logoff/reset/etc. I know you can set things to "disable install updates and shut down" or "make logoff the default action", etc., so I'm wondering if it's possible that using the method LMI does to "lock" the screen, perhaps a logoff is being initiated instead.

Also, what are the settings in LMI set to? If you un-tick the locking check boxes, does that resolve your issue? If you go to the Advanced settings and turn on logging, does it show anything around the time this is happening to you?

Also, what happens if you lock the station and then disconnect? Does that resolve it?

**EDIT**

(sorry I just realized this is LMI Rescue, not regular LMI - I would suggest you call support, although you could also try removing the plug-in and redownloading it. Not sure where the LMI stuff installs to, though.)