If I try to connect via RDP from Remote Desktop Manager, pressing a Windows button on the keyboard opens the client start menu.
If I connect using regular remote desktop application, it successfully redirects windows button, so it opens start menu on the server.
This was never a big problem until Windows 2012, where Start button is missing. Now you have to use keyboard shortcuts.
edited by Neolisk on 9/21/2012
Edit your RDP session and in the RDP settings, select the tab page Local Resources. Make sure in the Keyboard combobox that "On the remote computer" is selected.
David Hervieux
Thanks for your reply.
Honestly I did not know "Apply Windows key combinations" option is responsible for the Windows key itself, since it is hardly a combination.
Set it to "Full screen mode only" as this is how it's configured in my RDP client - and it's working.
Now I have a related problem - I have over 50 connections in Remote Desktop Manager that have the same issue (BTW - is there any way to tell how many connections I have? could use current scope vs total).
Any quick way to change them all in one shot, but edit only this setting and do touch others? I recently had bad experience with using batch edit with some other tool, so better not assume it will work for this purpose without your confirmation.
In the long run, it would be nice if you could implement templates for RDP parameters, so you can define 2-3 different sets and make all sessions use either of them, without hard-code per connection. Easier to maintain and troubleshoot this way.
Hi,
The batch edit should work without any problem. However you should create a backup before using it. It's always a good idea to have one. I like your idea. I've already have something similar in mind but not exactly what you suggest. I think that I will be able to add this for the version 8.0
David Hervieux
Anything that can improve current maintenance will be better. If you have some thoughts, we can discuss here, and possibly incorporate into one solution.
Because I have no means to check if it worked as I wanted, I went the more stable way. Here is a Powershell script to change 'KeyboardHook = InFullScreenMode' for all connections.
param($Path,$Key,$Value)
$doc = [xml](gc $Path)
$doc.ArrayOfConnection.ChildNodes | foreach {
$keyHook = $_.SelectSingleNode($Key);
if($keyHook -eq $null) { #KeyboardHook does not exist
$keyHook = $doc.CreateElement($Key);
$keyHook.InnerText = $Value;
$_.AppendChild($keyHook);
} else { #KeyboardHook exists, will be changing it
$keyHook.InnerText = $Value;
}
}
$doc.Save($Path + ".new")
edited by Neolisk on 9/24/2012
Good idea.
David Hervieux
This helps. Thanks a lot.