Discussion Locked

Win2K Setting Locales in profile/logon s

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have a W2K Citrix Server farm in the UK which German users logon to for a published application. (JDE OneWorld).
They can export Data from OneWorld into Excel 97 (also running on the Citrix servers.) Then save the file onto a network drive. I can manually change their locale to German by running a Terminal Desktop.

Is there any way of automatically setting their Terminal Services Locale to German with a Group policy/Batch file on startup ?

9 replies

by liquidcoolit

In Win2K Server open MMC and add the Snap in "Active Directory and Services". In there there open the properties dialog box for the site , domain, or OU and select the Group Policy TAB.Select the GPO (Group Policy Object) you want to administer andthen select Edit. From there you can edit the policy to set a locale for a group.

Cheers ....

by cmcardell

There are no settings for Locale in Group policies. (except restricting selections in control panel)
A Gp Could be applied on a Site, but this would not help as they are terminal server connections.

by jack republic

1.open a.d users and computers mmc,and edit
the terminal server gpo(asuming you have one)
2.go to user configuration/administrative tamplates/control panel/regional options
and chooze german language.

by cmcardell

Already tried this - When you open a Terminal session and open the Control panel the Locale defaults back to US English (even after I have set the locale as German on the server and rebooted)

The GP May affect Desktop users but not Terminal services users ??

by maxwell edison

Client Connection Manager:

This tool lets administrators and end users set up pre-defined connections to one or several different servers for a single application or full desktop access. Client Connection Manager creates an icon on the client desktop for single-click connectivity to one or more computers running Terminal Services. This way, administrators who want to provide a single line-of-business application across the computing environment can create a connection, export it, and distribute that connection along with the Terminal Services Client software to the PC desktops (for example, Win32? - and Win16-based systems). The connection is automatically made available when the client software is installed.

Maxwell

This discussion is closed to new replies.