remote desktop windows-key combinations

[timeck]

I'm not sure when this problem started happening unfortunately. I run a windows XP guest in fusion and run it full screen. I can use things like ALT-TAB, etc just fine in that guest (I've configured my default keyboard preferences to make sure the standard shortcuts aren't swallowing anything).

I also tend to use remote desktop to access my work computer (another winXP instance). The problem is that all the special key combos like ALT-TAB or ctrl-ESC aren't being sent to the remote machine it seems. There are preferences in remote desktop to send these always, never or only when full screen. No matter what I can't get those keystrokes to the remote machine. This used to work at some point in time.

I get the same behavior no matter what remote machine I connect to, I've tried three different machines.

I'm up to date everywhere, all apple updates, fusion 3.1.2, all windows updates. the problem isn't new (or fixed for that matter) with 3.1.2 for sure though

Any ideas on what is wrong or how to debug this further? Thanks!

[rcardona2k]

I embarassed to say I had this problem for months before I figured it out. It has nothing to do with Fusion. Start your Remote Desktop client, before you connect, click Options, then Local Resources tab > Keyboard, check your settings for when to apply Windows keyboard combinations.

[WoodyZ]

Did you miss the part where the OP said "There are preferences in remote desktop to send these always, never or only when full screen. No matter what I can't get those keystrokes to the remote machine. This used to work at some point in time."?

[WoodyZ]

Any ideas on what is wrong or how to debug this further? Thanks!

Sorry, I don't have an answer for this particular issue however have you tried using Windows Remote Desktop for Mac? I use it on my Mac vs RDC from within a Windows Virtual Machine. I put it in a separate Space and toggle back and forth with a couple key strokes, it works nice.

[timeck]

Thanks for the suggestion WoodyZ. I did try the native client from microsoft a while back, but it was precisely problems with getting all the key bindings I wanted working that drove me to a windows VM.

In other news I can use tsclient from a linux VM on this same Fusion host and the keys I want seem to be making it to the remote winXP machine. Go figure.

[rcardona2k]

I don't want to give up on this as I use RDP as a primary app to all sorts of Windows (XP, Server 2003, Vista, Win7). You have said you use Fusion in fullscreen and that you changed the Local Resources settings in mstsc to Local Only, Remote Only and or only in (RDP) full screen. What version of the RDP client are you using and what is the OS type of remote system? Also what are your host OS and guest OS keyboard locales to set to.

I checked and there is no TS/RDS policies that can block keyboard mappings so this has to be something originating on the client.

(FWIW, I too have tried the MS RDC OS X client and it suffers from several usability issues around keyboard mappings, mouse support and re-connection behavior which make it less prefereable to the native Windows implementation. Plus I prefer to keep my VPN in the guest).