I was using an older RDC and today found a new 8.0.7 version of Microsoft Remote Desktop which looked pretty impressive. Only problem is, when I log into Windows 7 machines, my shift key and other modifier keys don't seem to work right. How can i configure cpanel email on an outlook for mac.
If Cmd ⌘ Ctrl ⌃ Shift ⇧ 3 would work to capture the entire screen to clipboard. That the key commands are on & set to defaults in System Prefs > Keyboard > Shortcuts > Screen Shots & also that resetting to defaults doesn't generate an orange warning triangle that another shortcut is using the same key command.
Connecting with the older Remote Desktop Connection Client for Mac 2.1.1, all those keys work fine. I found something that said, yeah, you have to use the onscreen keyboard. But that isn't an option and why did it work with the older product but not now with this new one? Hi Jeremy and thanks for the response.
I've been using Windows 7 and 8 under Parallels on the Mac and am quite familiar with getting the Mac keyboards, both extended USB and standard BT, to work under Windows. I'm also used to using RDC and RDP (Mac and Windows Remote Desktops) and this is the first time I've ever seen a SHIFT key not work across a remote session. I know about some of the quirks of the Command vs Control, using the FN key, etc.
But this is really quite beyond all that. If I remote into a Windows 7 machine from a Windows VM and RDP, it works.
If I remote into a Windows 7 machine from OSX and the older RDC, it works. If I remote into a Windows 7 machine with this new product, it doesn't work. To me, that seems to indicate something in the new product is broken. I should not have to make any changes to keyboard layout on either the system I am coming from or the system I am remoting to, in order for everything to work, including the SHIFT key. You may tell me the product is re-developed and working as intended, but I will tell you it is not working as this user intends it and it is 'broken' to me. The new version should not require any special steps to achieve basic functionality.
It's not useable as is for me. I have to keep using the older product. Hi, This product is re-developed. Mac and Windows Keyboard Layouts ： Mac keyboard layouts differ from the Windows keyboard layouts.
The OS keyboard locale is suggested to the remote PC. If the OS keyboard locale is not used, we recommend checking the keyboard setting on the remote PC and changing the setting manually. L The Command key on the Mac keyboard equals the Windows key. L To perform actions that use the Command button on the Mac, you will need to use the control button in Windows (e.g.: Copy = Ctrl + C). L The function keys can be activated in the session by pressing additionally the FN key (e.g.: FN + F1).
L The Alt key to the right of the space bar on the Mac keyboard equals the Alt Gr/right Alt key in Windows. In addition, besides the On-Screen Keyboard, you may need to find some Keyboard mapping tool for Mac. Jeremy Wu TechNet Community Support.
Hi Jeremy and thanks for the response. I've been using Windows 7 and 8 under Parallels on the Mac and am quite familiar with getting the Mac keyboards, both extended USB and standard BT, to work under Windows. I'm also used to using RDC and RDP (Mac and Windows Remote Desktops) and this is the first time I've ever seen a SHIFT key not work across a remote session. I know about some of the quirks of the Command vs Control, using the FN key, etc. But this is really quite beyond all that. If I remote into a Windows 7 machine from a Windows VM and RDP, it works. If I remote into a Windows 7 machine from OSX and the older RDC, it works.
If I remote into a Windows 7 machine with this new product, it doesn't work. To me, that seems to indicate something in the new product is broken. I should not have to make any changes to keyboard layout on either the system I am coming from or the system I am remoting to, in order for everything to work, including the SHIFT key. You may tell me the product is re-developed and working as intended, but I will tell you it is not working as this user intends it and it is 'broken' to me. The new version should not require any special steps to achieve basic functionality. It's not useable as is for me. I have to keep using the older product.