RDC bar hides next RDC bar

Question

When connected with RDC to a server and then from that server connects to another or even several servers, the first RDC connection bar completely covers the next session connection bar. That makes it look as you are still working in the first RDC connected server. For some, maybe many, of us this is a frequent scenario that causes irritation to say the least, or even mistakes entering data into the "wrong" session.

How can RDC be made to show which endpoint is active, and not hide subsequent RDC session connection bars?

I can thing of several ways to resolve this chained session situation:

• Translucent connection bars. At least showing that what you see is not where your normal keystrokes ends up. This could be implemented regardless. (When Microsoft?)

• Last connection bar always on top. This too leaves no clue that this is a chained session but what you see is where your keystrokes lands.

• Configurable connection bar height, width and position, in the session configuration (and/or command line). With this option the first bar could be constantly moved (like slided) to an offset position, not hiding the next sessions.

• Remember last connection bar position. This is in part similar to Save Remote Desktop connection bar size and position.

If any solutions already exists, please enlighten me.

P.S. I am not referring to or is interested in the hide connection bar option. That has its own pros and cons.

Answer 1

As already answered, options to control the RDC top bar are limited.

A better approach would be to change the desktop background of the computers you access to show identifying information such as the computer name. Microsoft's BGInfo utility does just this:

If you manage multiple computers you probably need BGInfo. It automatically displays relevant information about a Windows computer on the desktop's background, such as the computer name, IP address, service pack version, and more. You can edit any field as well as the font and background colors, and can place it in your startup folder so that it runs every boot, or even configure it to display as the background for the logon screen.

You can configure it to run on user logon or with Task Scheduler. This can be done using Group Policy so that it's automatically deployed to every system you might remotely access.

Answer 2

It is bad practice to go into a server and from there go to another server, but its not always possible to circumvent this.

You can actually grab the blue bar and move it left or right, which will make it so that both bars are visible.

In addition, you can choose to not connect to the 2nd server full screen, but windowed. That way, anyone will know there is a 2nd server.

There is no other way. You need to train everyone to do this, it can't be forced.

Alternatively, you may want to consider to change the entrance to the first server. For example, if you use Microsoft Remote Desktop Connection Manager, you can set it up so that it fills the entire screen, but not have that blue bar. If you then see the bar, you always know you are in a server in a server situation. Microsoft RDCM is free and a very good tool to manage many servers at once, but can just as easily be used to manage only a few servers.