Updated Microsoft Remote Desktop Client (universal) coming this week!

Queso

Suspended
Mar 4, 2006
11,824
7
Let me guess. Still only one machine allowed at a time and once again no recognition for non-US Mac keyboards :rolleyes:
 

nadyne

macrumors 6502a
Jan 25, 2004
992
0
Mountain View, CA USA
Let me guess. Still only one machine allowed at a time and once again no recognition for non-US Mac keyboards :rolleyes:
You can connect to multiple machines now. The beta only supports US keyboards (although you might find that non-US ones work, we just haven't thoroughly tested that scenario yet).

You can download RDC v2 beta from Mactopia, and you can submit bugs and suggestions for RDC v2 on Microsoft Connect. Check out the readme for the beta for a list of new features, as well as the known issues with the beta.

Regards,
Nadyne.
 

Queso

Suspended
Mar 4, 2006
11,824
7
You can connect to multiple machines now. The beta only supports US keyboards (although you might find that non-US ones work, we just haven't thoroughly tested that scenario yet).
Thanks, but I would have thought this should be core to the design requirements. The \ character is essential in Windows, yet using the UK keyboard layout for a Mac it is impossible to generate it in an RDC session under the current version. It means you have to remember to flip the Mac onto US keyboard layout before you begin your RDC session, and if you forget you have to close your running Windows programs, log out, restart the RDC program if it's still running (because otherwise it just hangs when you try to reconnect), change the keyboard layout, then reinitiate the session. It's the sort of jumping through hoops to make software work nonsense that should have been eradicated in early testing, and leaves the impression that yourselves at the MacBU didn't consider non-US Mac users at any point.

Anyway, rant over. I'll await judgement on the beta until I have time to properly test it.
 

fuzzy76

macrumors newbie
Apr 24, 2008
13
1
Tromsø, Norway
In what appears to be normal Microsoft fashion, this bug is still present 6 YEARS later. Sometimes I wonder why Microsoft bother doing OS X stuff at all....