RDP doesn't do MUI

by Michael S. Kaplan, published on 2011/03/04 07:01 -05:00, original URI: http://blogs.msdn.com/b/michkap/archive/2011/03/04/10136788.aspx

The question was easy:


I have installed French and English MUI on the server.

Now when users RDP to the server they get the language as per what is set on the server.

Is there any way to get the same MUI applied for the user depending on the language on the client machine from where they establish the RDP session?

i.e. English MUI when clients have English
i.e. French MUI when clients have French

Is there a way to achieve this functionality over the RDP session ?

Unfortunately the answer is easy, too.

Well, it is not unfortunate that it is easy to formulate an answer. That would be a dumb thing to call unfortunate.

The unfortunateness is in the nature of the answer.

Which is that no, there is no way to achieve that functionality.


The truth is that it is not something RDP supports.

But for what its worth, it would be kind of cool if it did. It just makes sense -- not just as an option but as the default option.

It is what we do with default keyboard layouts, which are often assigned by the default user locale in a per-session way that is not saved. So maybe the user interface language could do the same!

But it doesn't actually do that, unfortunately....

Raymond Chen - MSFT on 4 Mar 2011 8:40 AM:

It would also create havoc if somebody RDP'd in from a French system, then disconnected, then reconnected from a German system. Changing the MUI language requires a logoff, so when the German user connected, they'd be told "This session cannot be resumed because it is running a different language. I will log off now. Please wait for logoff to complete, and then reconnect." Oh, and the message would be in French.

Michael S. Kaplan on 4 Mar 2011 8:51 AM:

Ah, details....but those could all be worked out. Perhaps by keeping the old sessions around by fast user switching? Or if not then by doing the right thing with resources for that in-between state during the "logging off" period. That's a tractable problem....

Cheong on 6 Mar 2011 5:27 PM:

Alternatively, perheps we should set the rules to apply MUI according to RDP langauge preference only if the logon is creating new user session. When attempting to connect to a session already created, the RDP option will be ignored and session not restarted.

Ian Boyd on 6 Mar 2011 7:59 PM:

This is similar to my longstanding wish that the rdp server honor my font/dpi preferences.

And while we're at it, my color scheme preferences.

But mostly my 14pt font preference - 8pt (or 9pt) is so small.

Azarien on 7 Mar 2011 2:48 AM:

Now, having such feature request, what are the odds that it actually gets implemented, in

1. a hotfix

2. Windows 7 Service Pack 2

3. next Windows release?

Mike Dimmick on 7 Mar 2011 6:24 AM:

Azarien: Microsoft's priority for servicing released software is nearly always stability, above all. Changes to behaviour only occur if someone asks for it formally, via support (paying for the incident), and only if in the appropriate time frame for the product (mainstream support, typically first five years). The exceptions have generally been where the product org leaders feel that they're missing a market opportunity if the change was delayed to the next full release. These are, now, more often an R2/R3 release rather than a service pack.

If someone were to submit a Design Change Request via Customer Support Services, they would get a hotfix. My assessment is that the hotfix would not be made generally available, that is, it wouldn't be on Windows Update even as an optional update. However, it would go into the trunk for the next major version of Windows, and into the branch for the next service pack. It would also be in the QFE branch for the component, so anyone who's already on the QFE branch - has installed another hotfix affecting the component - would get it in the next generally-available update for that branch.

If a Program Manager at MS (presumably on the RDP team, or at least part of the Windows organization) felt strongly enough, he could write a spec for a change to RDP, then try to convince the development team to implement it (PMs and devs are peers at Microsoft). That would almost certainly be in the next full release only, though sometimes this kind of change might go in a service pack if this component had a major change anyway. For example, the addition of RemoteFX and Dynamic Memory for Hyper-V in Windows 7/Server 2008 R2 SP1, a 'market opportunity' change (competing virtual server products already had dynamic memory and were adding 3D acceleration).

go to newer or older post, or back to index or month or day