1
After connecting to a remote session via RDP, windows keyboard shortcuts appear to be sent to both the local machine and to the remote machine.
As an example, pressing the Windows key opens up the start menu on both the local and the remote machines. Pressing a combination such as Win+R (on the remote desktop) opens up the Run dialogue box on the local desktop.
Within the Remote Desktop Connection (mstsc) settings, the Windows key combinations are set to, "Only when using the full screen" (keyboardhook:i:2). The RDP session is full screen and Ctrl+Alt+Pause/Break properly changes between full screen and windowed modes.
I have read about people having (possibly) related issues with locking their machines via Win+L while a remote client is currently focused. I have followed their various fixes to no avail.
Any ideas or pointers are greatly appreciated.
Thanks,
I've been using the windows key via rdp (mstsc) for many years. I cannot imagine that it would suddenly just stop working without an explanation. For what it's worth, the majority of those commands are not working in my rdp session. The only one that is working is CTRL+ALT+BREAK – Kris Powell – 2014-09-23T15:29:02.583
Is this a new local machine your using or are you connecting to a new remote machine? I have found previously that my version of mstsc.exe can hugely affect how my remote desktop session is handled. I recently copied and replaced my local mstsc.exe file with one from a Server 2008 R2 windows install and found it to be more reliable than my Windows 7 copy (different version). – CharlesH – 2014-09-23T15:35:21.020
They're both not new machines. I've been using these specific machines for over 6 months with no hitch. This issue just suddenly started yesterday. I've tested this by rdp'ing into other machine from my local workstation, as well as rdp'ing into those same machines from another workstation. So far, everything points to some change on my local workstation. All machines are up-to-date with updates, and no updates have been applied around the time that this started happening. I'll try copying over mstsc.exe from a Server 2008R2 and see if that provides any more insight. – Kris Powell – 2014-09-23T15:42:10.960
Unfortunately, it didn't help to replace the mstsc.exe. I'm still running into the same wall. I appreciate your time and assistance though. This issue has really got me perplexed. – Kris Powell – 2014-09-23T15:59:37.363
Hmm that is really strange.. I will have a further dig around and run some testing from a few workstations I have to see if I can try to find out what scenario's (local OS, remote desktop OS, etc.) causes a similar problem. – CharlesH – 2014-09-23T16:02:11.277
Thanks again for your help. I really appreciate the second pair of eyes. I figured out what my problem was and I've answered it for anybody to see. – Kris Powell – 2014-09-23T22:03:00.083
@KrisPowell How strange is that, well done for finding out the root cause. – CharlesH – 2014-09-24T09:39:40.287