Connecting to a remote desktop session

I found something that seems a little weird, here is the scenario... A user starts a session on a remote desktop from their local machine, we connect to the session inside the remote desktop session and everything works without issue until the user on the local machine minimizes the remote desktop session, we don’t get disconnected our session just goes black, if the user opens the remote desktop session our remote session continues. Has anyone seen this or found a workaround?

Find more posts tagged with

Comments

LeaRob

Oh, and even RDP running in console mode wont help!

LeaRob

Here's the response I received:

Due to the way that Microsoft implements Terminal Services, using it's built-in Remote Desktop feature in conjunction with LogMeIn is not recommended. You may see this message in LogMeIn Rescue when the target user's computer goes into a mode which cannot be accessed while Rescue is running as an application. Examples are if the computer is set to lock itself after a certain period of inactivity, or if someone on the target user's network initiates a Remote Desktop session into the machine. You can prevent this by running Rescue as a service, which is an option you initiate directly before clicking Launch Remote Control. We are trying to proceduralise our Help Desk's (HD) response to third-party requests for access to our servers. And so the simplest solution is as follows: 1. Third-party contacts our HD and asks for remote access to internal server2. HD authenticate the third-party, log the request sort approval then RDC into identified server3. HD navigate to logmein123.com and host the connection with the third-party4. During this time (it maybe a long session, and assuming third-party has pre-approval), HD shrink the RDC window allowing them to continue alternative HD tasks.5. If no pre-approval HD watch the entire session. Any thoughts or improvements on this ? Lea

LeaRob

Ah, I've just sent a post to support about exactly this scenario.

I assume there is still no workaround, although as all our servers have Out of Band console access (iLo) we can use that, mind you it's not always convenient.

Lea

Csaba Jaromi

Hi There,

The workaround is, unfortunately, that there is no workaround. The way Terminal service - remote desktop sessions work in Windows systems is that when they are active, then there is active display driver, when they are minimized or closed, then the display is suspended as well - so, no data of screen contents is captured by the Windows display drivers. Therefore when the TS session is minimized, Rescue (as a matter of fact, even IT Reach or other programs) is unable to show you the screen of the session because at that time there is no such thing.

I hope this explains, the users should keep the TS session not completely minimized, but in a window pushed to the background. this way the TS display is still active while the user does not have to keep focus on the remote desktop.

cheers,

Cs

Quick Links

Join the conversation!

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!