Keyboard doesn't work when jumping in RDM
After jumping in RDM, the keyboard doesn't work. Keystrokes do not affect the 2nd box. The mouse works fine on the 2nd box, however. It's driving my team members crazy.
Jump Host Settings (defaults otherwise):
* Entry Type: Microsoft Remote Desktop (RDP) -> Configured
* Display: Embedded (tabbed)
2nd Box Settings -- same as Jump Host:
* Entry Type: Microsoft Remote Desktop (RDP) -> Configured
* Display: Embedded (tabbed)
To reproduce the issue:
* Double-click 2nd Box's entry -> connects to Jump Host
* Manually click mouse / press enter at login banner
* RDM automatically opens and connects to 2nd Box
* Double-click to open Windows Explorer
* Keyboard input does nothing on 2nd Box -- arrows don't move the cursor, characters aren't typed, etc
When I manually connect twice, I don't have the problem -- just after jumping. My coworkers, however, do not have jumps configured. They manually connect twice, and the keyboard does not work on the 2nd box.
Workaround:
To "fix" the issue, I right click on the Jump Host's taskbar. Then I click back into the 2nd Box's tab, and the keyboard works! It's very repeatable.
NOTES:
* This only started after updating from v11 to v13. This was never a problem for me or my coworkers before.
* Local and Jump Host RDM Versions: 13.0.6.0
* RDM Versions Before Updating: 11.5.4.0
All Comments (12)
Hello Andrew,
Regarding the keyboard issue I wasn't able to reproduce the issue. If I understand correctly when you mean the "2nd Box" This is the RDP session on the Jump server, right?
Did you try to recreate the two sessions, directly in RDM 13.0.6 to see if it's working?
What OS is the Jump host and does RDM on the Jump host is also RDM 13.0.6 or 11.5.4?
Best regards,
David Grandolfo
Yes, the 2nd box is the RDP session on the jump host.
Yes, I've tried with and without jumping in RDM 13.0.6 -- without meaning two manual RDM connections: local to jump host, then jump host to 2nd box. Results for without jumping are mixed -- the keyboard works fine for me but NOT for my coworkers.
As with any bug report, you may need to ignore some of the data points that are unhelpful for debugging.
Timeline w/ version info:
* All boxes had version 11.5.4 until recently -- local and jump host.
* Jump host was updated first to 13.0.6.
* Keyboard input stopped working on the second RDP connection from the jump host.
* Local versions were updated to 13.0.6, per recommendation of customer support.
* Keyboard input still doesn't work consistently.
OS info:
* Local boxes are all Windows 7
* Jump host is Server 2008 R2 Standard
* 2nd boxes are Server 2012 R2 Standard
Random note:
I have a hunch it is related to the new style of windows UI (typical start orb opens the full-screen tiles menu).
Hi,
On your Windows 7 computer as well as on the remote server, could you try the following;
Go in Control Panel
Select Ease of Access Center
Go in Make the keyboard easier to use
Uncheck the Turn on Filter Keys option
Let me know if that help.
David Grandolfo
I've confirmed "Turn on Filter Keys" was already disabled on many boxes:
* My local box
* 3 or 4 jump hosts
* 5 or 6 remote boxes (the host after jumping)
So that doesn't appear to be related. What other ideas do you have?
Attached is a screenshot of my workaround to "fix" the keyboard not working:
* Right click the jump host's task bar
When you go back to the 2nd host tab, everything works fine.
Hi,
We had a similar issue with another customer "Robert B" and here is the solution that works for him?
Have upgraded my RDP/mstsc to version 8.1 , which has resolved the issue:
KB’s must be installed in the following order: KB2574819, KB2830477, KB2857650, KB2913751, KB2923545
Best regards,
David Grandolfo
Ahhh. That's a start.
Do these need to be installed on all boxes -- local, jump hosts, and remote hosts?
Hi,
Based on the customer information we received, you only need to perform these steps on your local computer.
That being said, it could be a good idea to confirm that the Jump and the remote host have MSTSC 8.1 if the issue is still there.
Best regards,
David Grandolfo