How to Hide [or Show] the Remote Desktop Bar
This is an example of the remote desktop [RDP] connection bar:
I always unpinned this remote desktop title bar so that it would automatically hide, BUT it would still get in my way occasionally. For example, when connecting to another RDP session, there will be two title bars overlapping. I could get around the issue by moving one but it was just annoying or confusing at best. The other time it would cause problems was in Chrome, because chrome browser tabs are so high up on the screen that I would get within the pixel limits of opening the hidden…
Remote Desktop Services Shortcut Keys
- Article
- 09/10/2021
- 2 minutes to read
- 4 contributors
Is this page helpful?
Yes No
Any additional feedback?
Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy.
Submit
Thank you.
In this article
The following is a list of the Remote Desktop Services shortcut keys.
A note regarding missing keys: Many compact keyboards do not contain some keys. For example, many laptops do not have a dedicated BREAK key. However, they usually have keyboard shortcuts that replace dedicated keys. These key replacements are specified by the manufacturer of the keyboard, so you may need to look up key replacements in the documentation provided by your keyboard or laptop manufacturer.
There are two different sets of shortcut key combinations you can use on a remote desktop connection: the default Windows shortcut keys, or the shortcut keys originally designed for the remote desktop. You can set which shortcut keys you use on the local and remote machine through the Remote Desktop Connection client [ie, the dialog that appears when you click on the Remote Desktop Connection icon]. From there, click Show Options [if you cannot see the options], and then click the Local Resources tab. In the Apply Windows key combinations drop-down, you have three options:
| On this computer | The default key combinations will work on your local machine only. You must use the alternate combinations on the remote desktop. |
| On the remote computer | The default key combinations will work only on the remote desktop. You must use the alternate combinations on the local machine. Note that once you close down the Remote Desktop Connection, your local machine will once again use the default windows shortcuts. |
| Only when using the full screen | The default key combinations will work on whichever machine has the full desktop; functionally, this means that the default key combinations work for the local machine, unless you have the Remote Desktop Connection window in full-screen mode. |
For more user information about Remote Desktop connection, See How to use Remote Desktop.
| CTRL+ALT+HOME |
Activates the connection bar. |
CTRL+ALT+BREAK or one of these shortcuts:
|
Switches the client between full-screen mode and window mode. If these shortcuts don't work, or the keys aren't available, you can try the following alternative:
|
| CTRL+ALT+END |
Brings up the Windows Security dialog box for the Remote Desktop Session Host [RD Session Host] [provides the same functionality as pressing CTRL+ALT+DEL on the local computer]. |
The following table describes the standard Windows shortcut keys and their equivalent Remote Desktop shortcuts that are different. [For example, Ctrl+Z is generally the 'Undo' shortcut on both standard Windows and Remote Desktop.]
| ALT+TAB |
ALT+PAGE UP |
Switches between programs from left to right. |
| ALT+SHIFT+TAB |
ALT+PAGE DOWN |
Switches between programs from right to left. |
| ALT+INSERT |
Cycles through the programs in the order they were started. |
|
| Windows key or CTRL+ESC |
ALT+HOME |
Displays the Start menu. |
| ALT+SPACE BAR |
ALT+DELETE |
Displays the system menu. |
| ALT+PRINT SCREEN |
CTRL+ALT+MINUS SIGN [-] |
Places a snapshot of the active window, within the client, on the clipboard. |
| PRINT SCREEN |
CTRL+ALT+PLUS SIGN [+] |
Places a snapshot of the entire client windows area on the clipboard . |
25 Replies
· · ·
Chipotle
OP
Dec 9, 2010 at 09:48 UTC
Please, please, please someone reply on this.
I have looked again and again for an answer to this as it is a real thorn in my side.
We use XP clients connecting to 2003 servers.
If I could spice this up more than one I would do ......
0
· · ·
Thai Pepper
OP
Dec 9, 2010 at 09:54 UTC
You can have a maximum disconnect time on the RDP connector on the server. This will auto logout the session after the disconnect timer is up.
Is this what you're looking for?
0
· · ·
Chipotle
OP
Dec 9, 2010 at 09:55 UTC
yeah, what a pain. We used to schedule a server reboot every night to clear down the open sessions left by users.
I wish you could give them a little electric shock when they press it.... muhahhha
1
· · ·
Chipotle
OP
Dec 9, 2010 at 10:04 UTC
JacobP wrote:
You can have a maximum disconnect time on the RDP connector on the server. This will auto logout the session after the disconnect timer is up.
Is this what you're looking for?
No. This is to stop users disconnecting by clicking the X.
0
· · ·
Habanero
OP
Dec 9, 2010 at 13:59 UTC
I repeatedly send them emails instructing use on how to log off correctly, sometimes even cc their boss. As far as I know there is no magic setting to stop a user from hitting the X.
0
· · ·
Serrano
OP
Dec 9, 2010 at 16:35 UTC
I searched for this ad nauseum a few years ago to help with Citrix user disconnects and I couldn't find a reliable way or hack to disappear the x. All I could do was what JacobP described and just force logoff after a certain amount of idle time.
0
· · ·
Serrano
OP
Dec 10, 2010 at 03:06 UTC
Yeah, same as what folks above are saying. I don't know of any way to stop them "logging off" by pressing the X, been telling them for years now, but some of them just don't get it.
Likewise there are users who can't seem to fathom what a thin client is or does, so they insist they've logged off and on again, even rebooted, when actually all they've done is restart their thin client and left their session running on the server.
Eventually, we just implemented the timeout, and settled on 2 hours.
0
· · ·
Chipotle
OP
Dec 10, 2010 at 03:44 UTC
I have the session timeout in anyway, but thats not what I'm aiming for.
Ok, who about this. I change their RDP to turn off "Display connection bar in full screen mode". So now they'll have no X or minimise button.
Some users need to do scanning from their desktop. So I need the minimise the RDPwindow for them. I could add a shortcut to their RDPdesktop, which will launch some code to minimise the window. All I need to do is figure out the code!
0
· · ·
Chipotle
OP
Dec 10, 2010 at 04:01 UTC
Actually, there are two keys I need to run:
CTRL+ALT+BREAK -
Switches the client between full-screen mode and window mode.
WINDOWS KEY + M
Minimise the window
Is there a way I could put these two keys into a batch file?
SendKeys would run from VB, maybe there is a Powershell equivalent.
0
· · ·
Chipotle
OP
Dec 10, 2010 at 06:18 UTC
Got this
Option Explicit
Dim objShell
Set objShell = CreateObject["WScript.Shell"]
objShell.SendKeys ["!{BREAK}"]
objShell.SendKeys ["^{ESC}+M"]
I think I have the keys right, but it doesn't work.
Anyone here able to suggest what I should change?
Thanks
0
· · ·
Datil
OP
Dec 10, 2010 at 07:25 UTC
Had the exact same issue here and I never stops.
Your scanning issue I wasalsoexperiencing here. What I ended up doing was making the scanner scan everything to a central folder on their workstation then created a shortcut to that folder on their terminal server desktop. I turned off all the non-bad notifications for the scanner and told them the only reason you need to check your local machine when scanning is if there is an error. This removed their need to constantly minimize and go back and forth.
0
· · ·
Mace
OP
Dec 10, 2010 at 08:17 UTC
Problem with a VB app sending those key commands and placed on the RDP sessions desktop is that the commands will be received by the RDP computer, not the clients computer, so the key combos won't work. Maybe a third party DRP app might have what you need, here is a comparison of some//4sysops.com/archives/comparison-of-six-free-rdp-client-tools/
0
· · ·
Chipotle
OP
Dec 10, 2010 at 08:25 UTC
Those key commands do work for me, if I run them from the RDP session. And it isthe RDP computer I want to run them. So I think it should work...
Thanks for the list of third party RDPs.
0
· · ·
Mace
OP
Dec 10, 2010 at 09:06 UTC
Yes but you are still on the host when you run them from your keyboard and the host can intercept the keys before they hit the remote machine, if you run them from an application on the remote machine it is running on the remote machine and therefore not intercepted by the host.
0
· · ·
Thai Pepper
OP
Dec 10, 2010 at 09:24 UTC
Alex is correct.
You need a way to launch the script from the local computer via keyboard command. Kinda like a macro of win 3.1.
0
· · ·
Datil
OP
Dec 10, 2010 at 12:05 UTC
I've used this method to great success. It seems like I had an issue with the latest RDP client, but it's worth a shot. You actually change the behavior of the X and create a dialog that tells them to log off [Instead of Clicking OK to disconnect]. The only catch is that you have to be able to put the client on their machine, so you'll need remote access to it at least once.
0
· · ·
Serrano
OP
Dec 10, 2010 at 14:26 UTC
Rob Q wrote:
I've used this method to great success. It seems like I had an issue with the latest RDP client, but it's worth a shot. You actually change the behavior of the X and create a dialog that tells them to log off [Instead of Clicking OK to disconnect]. The only catch is that you have to be able to put the client on their machine, so you'll need remote access to it at least once.
Nice one!
0
· · ·
Chipotle
OP
Dec 14, 2010 at 03:41 UTC
Rob Q - thats excellent. Thanks!
0
· · ·
Chipotle
OP
Dec 16, 2010 at 09:57 UTC
hang on! :]
That didn't work with mstsc in System32 folder. It will work with the version in the i386 folder, but thats not the one I want.
Anyone know of a resource hacker that works with the latest mstsc.exe?
From looking online, there seems to be a problem with disabling the X in RDP6.
0
· · ·
Jalapeno
OP
Jan 11, 2011 at 07:47 UTC
Can you not just use the older mstsc.exe from an older box on your new machines? I've not tried it, just thinking "aloud"...
0
· · ·
Serrano
OP
Feb 8, 2011 at 05:51 UTC
Just change the policy to end disconnected sessions after a discreet time period. 15-30 minutes should do it. If users lost work because they didn't press save before they disconnected the session they will get the message. I will let you choose whether to tell them that you are changing this and why. Realistically there is no way to stop this because RDP is an application running on a remote workstation. Even if you could put a policy on every remote PC to somehow hide the X it wouldn't stop someone ending the application in Task manager. I know you can hide the task manager. But what happens if the internet connection drops at either end or the PC loses power suddenly. That will do the same thing and leave you with a disconnected session on your TS/RDS.
0
· · ·
Pimiento
OP
Oct 2, 2012 at 19:17 UTC
1st Post
Fatbeard wrote:
hang on! :]
That didn't work with mstsc in System32 folder. It will work with the version in the i386 folder, but thats not the one I want.
Anyone know of a resource hacker that works with the latest mstsc.exe?
From looking online, there seems to be a problem with disabling the X in RDP6.
For RDP6 you need to edit the mstsc.exe.mui file located in C:\Windows\system32\en-US directory. I have done that to both the XP and Win 7 versions using Resource Hacker v: 3.6.0.92 and they work fine. Just make sure all PCs are running the newest version of RDP for your OS, mainly so that you only have to edit 2 files, then depeding on OS version, push the edited versions out through the admin shares.
2
· · ·
Sonora
OP
Mar 10, 2016 at 01:27 UTC
I've tried to edit the mstsc.exe.mui file as mentioned above but I can't find the 404 dialog? Should I be looking for something else?
0
· · ·
Pimiento
OP
Sep 4, 2016 at 23:07 UTC
1st Post
Create a batch file withshutdown /l and put it in the Public Profile's Desktop.
0
- 1
- 2
This topic has been locked by an administrator and is no longer open for commenting.
To continue this discussion, please ask a new question.
Set Up Microsoft Remote Desktop Connection
First, you or someone else must physically sign into the PC you want to remotely access. Enable Remote Desktop on this computer by openingSettings > System > Remote Desktop. Turn on the switch next to Enable Remote Desktop. Click Confirm to enable the setting.
By default, the options to keep your PC awake for connections when plugged in and make your PC discoverable on private networks should both be enabled. To view or modify either option, click the appropriate Show settings link. However, you can leave both options enabled at this point. Instead,click the Advanced Settings link.
Check the box next to Require computers to use Network Level Authentication [NLA] to connect. NLA adds tighter security for remote connections over the same network as users must be authenticated before gaining access to the remote PC.
Assuming you're connecting to a computer on the same network, you can ignore the External connections section. The section for Remote Desktop port shows the default port to listen for and accept a remote connection.
By default, any user who has an administrative account on the remote PC can access it.Assuming you're using a Microsoft Account to sign into Windows, and your account has administrative rights, your best bet is to simply use that account to sign in remotely.
If you want to grant remote access to a different account, return to the previous screen and click Select users that can remotely access this PC at the bottom of the screen. Click Add and enter the username for that account.
Finally, make note of the name of this computer as you'll need it to log in remotely. If you wish to change the computer name to something easier to remember, follow these steps. Close the Remote Desktop settings screen when you're finished.