Language Locales

[David Martin]

I have a client running a Win2k Terminal Server that
requires the default Regional Languge setting to be
Australian English. But no matter what you do to set this
and remove US English in Control Panel>Regional Settings
it comes back. What can I do to force this selection,
Group Policy, Logon Script or Registry key ?? please can
you help.

 

[Vera Noest [MVP]]

Check if this applies to your situation (should be fixed in SP4,
though):

322042 - Input Language of Terminal Server Client Does Not Match That
of Terminal Server Session
http://support.microsoft.com/?kbid=322042

 

[Stephen]

David, I had a similar problem in Brisbane and created a makeoz.bat to force
the change at every login (it is a documented bug in W2K).
You will need to download a program called setlocale.exe
This is the whole context of the batch file

SetLocale 00000c09

Stephen

 

[Guest]

Vera,
Checked out the Kbid 322042 and did some tests, now
understand that the input locale comes from the client
computer. If I do whats suggested in the workaround, the
locale of 00000c09 (Aus EN) follows through to the TS
session when opened. All well and good but I cannot do
this on all PC's as some are Thin Client terminals. Where
can I set this value to ensure all TS sessions start up
with the c09 locale instead of the 409 (US EN), or will
the hotfix referenced solve this. As for the server
background, it was built last week with all SP's and
updates.
David

 

[Vera Noest [MVP]]

Can't you set the proper regional settings on the thin clients, in
the setup menu?
If not, I'd go with Stephens solution.
SetLocale is downloadable here:

http://www.spectrodisplay.nl/frames.html

 

[Guest]

Vera,
Checked the Thin Clients this morning and found they are
holding the Language setting, it's only PC's. Also the
work around in kbid 322042 works only on the older TS
client app not Remote Desktop Connection app. I assume the
reg key will need to be in a different reg location for
RDC. I will try Stephens solution and let you know.
David

 

[Guest]

Vera,

Tried the setlocale.exe and it didn't change a thing,
either on the W2k TS or my XP pc running it from the cmd
window.
David

 

[Guest]

Did more digging again and found an exact description of
the issue in kbid 257964 but it relatates to NT4 TS
edition, is this workaround still relavent for W2K ??
David

 

[Vera Noest [MVP]]

Aaah, good of you to find that article! I had seen it before, but
couldn't find it myself.

I would certainly give it a try. If you compare 257964 with
322042, you see that the modifications on the client are exactly
the same (step 1 in 257964 = step 1+2 in 322042).
The step 2 described in 257964 just adds the Australian Keyboard
layout on the TS.
The only thing that makes me doubt if this will work is the fact
that one would expect that this is already fixed in W2K, since the
problem was known in NT 4.0.

Make sure you have a backup of your server before making any
modifications, and please let us know if it works!

 

[Guest]

Vera,
We tested out the Kb 257964 settings and this works, but
only on using the TS client. If we use the Remote Desktop
Client to connect (we prefer using this one), it doesn't
force the Aus Eng language. There must a different Reg Key
location on the client PC, do you know where this would be?
David

 

[Vera Noest [MVP]]

I've done some searching in regedit on my own client (but I don't
have any special keyboard mappings). It seems as if this information
is stored in:

HKLM\Software\Microsoft\Windows NT\CurrentVersion\IniFileMapping
\KeyboardLayout.ini

besides the HKEY_CURRENT_USER\Keyboard Layout\Substitutes
registry key.

I've no idea if this location is used by the rdp client, though.

 

[Guest]

Vera,
I have taken this issue up with the local MS professional
support and they have advised me to apply the reg key to
the server specified in KBid=322042 after the hotfix
paragraph. This then forces the Terminal Server to ignore
the local client settings. Once set in the session it
stays, thanks for your assistance, we seem to have done
full circle on our discussions but a resolution in the end.

Have a good day.

David

 

[Vera Noest [MVP]]

Yes, indeed!
To be honest, I believed that this was the first thing you tried,
and that it didn't work.....
O well, I'm glad that the problem is solved, and we have at least
discussed the topic thoroughly

 

[Guest]

Yes on that artical I had tried the Workaround with some
success but not the top half as I thought this was covered
by SP4, but in fact you needed SP4 plus the
IgnoreKeyboardLayout key.