Backtrack:  
 
by lunarg on September 18th 2008, at 16:35

When you're using a Belgian keyboard (or another) on a Windows 2003 Terminal Server, you might have the same problem we had: characters that are formed with a combination of AltGr and other characters (e.g. the @ sign) don't work as they should.

There are two things you can do to work around this problem.

Use another key combination

Instead of using AltGr, try using CTRL+ALT and the key you want. This circumvents the problem, but may not be what you want.

Change Windows key combination application

You can change the application of Windows key combinations. Rather than applying them to the TS, you can change it so it applies only to the local computer.
This disables the Alt+Tab and Windows key in the TS session, which is probably also not really what you want. On the other hand, it does fix the issue with extended characters.

To change the setting for default RDP sessions, do the following:

  1. Start mstsc (do Start, Run, then mstsc).
  2. Click the Options button, then the Local resources tab.
  3. In the Apply Windows key combinations list, select On the local computer.
  4. Next, select the General tab, click Save as, and save it as Default.rdp in your My Documents.

Source

 
 
« December 2022»
SunMonTueWedThuFriSat
    123
45678910
11121314151617
18192021222324
25262728293031
 
Links
 
Quote
« Debating Windows vs. Linux vs. Mac is pointless: they all have their merits and flaws, and it ultimately comes to down to personal preference. »
Me