G
Guest
Hi there Windows admins,
I am currently reorganising an Active Directory user and computer hierarchy,
which is relative flat, into one with multiple nested organisational units.
The domain controllers run Windows Server 2003 with AD in native 2003 mode,
and the workstations are a mixture of Windows 2000 Pro SP 4 and Windows XP
Pro RTM and SP1. (Of over 100 workstations, less than 10 are NT 4 SP6a, but
they can stay in the Dark Ages for now.)
I am using cascading Group Policy Objects to apply a whole range of company
policies to the users and their workstations. One thing I cannot apply
through GPOs are the regional and language options. What a pity.
The only option I've found is to use the technology for an unattended
installation where I provide an answer file to a Control Panel applet
('intl.cpl'). I have created logon scripts that call 'rundll32.exe' as
instructed here:
http://support.microsoft.com/default.aspx?scid=kb;en-us;289125
For our workstations in Australia and New Zealand (the vast majority), I
want to set the "default input language" to "English (Australia)" and
"English (New Zealand)", respectively.
As you probably know, Microsoft Office uses this to determine the default
proofing (spelling and grammar) language. If set incorrectly, Office will use
any excuse to start using the incorrect proofing language (e.g. in new
documents).
But, most annoyingly, Microsoft doesn't seem to have created a suitable
"Locale ID:Input Locale" combination for Australia and New Zealand:
http://www.microsoft.com/globaldev/reference/winxp/xp-lcid.mspx
For example, for Australia you'll note that the code is "0c09:00000409". The
"0409" is the input locale for "English (US)". I believe what I need is
"0c09:00000c09", which signifies that GUI strings are localised to Australia
(part before the colon) and that user input is in Australian English (part
after the colon).
Why doesn't Microsoft want Australians to input in 'Strine?
If anyone can suggest a solution for Win2K and WinXP, I'd appreciate it.
Cheers, mate!
desil.
I am currently reorganising an Active Directory user and computer hierarchy,
which is relative flat, into one with multiple nested organisational units.
The domain controllers run Windows Server 2003 with AD in native 2003 mode,
and the workstations are a mixture of Windows 2000 Pro SP 4 and Windows XP
Pro RTM and SP1. (Of over 100 workstations, less than 10 are NT 4 SP6a, but
they can stay in the Dark Ages for now.)
I am using cascading Group Policy Objects to apply a whole range of company
policies to the users and their workstations. One thing I cannot apply
through GPOs are the regional and language options. What a pity.
The only option I've found is to use the technology for an unattended
installation where I provide an answer file to a Control Panel applet
('intl.cpl'). I have created logon scripts that call 'rundll32.exe' as
instructed here:
http://support.microsoft.com/default.aspx?scid=kb;en-us;289125
For our workstations in Australia and New Zealand (the vast majority), I
want to set the "default input language" to "English (Australia)" and
"English (New Zealand)", respectively.
As you probably know, Microsoft Office uses this to determine the default
proofing (spelling and grammar) language. If set incorrectly, Office will use
any excuse to start using the incorrect proofing language (e.g. in new
documents).
But, most annoyingly, Microsoft doesn't seem to have created a suitable
"Locale ID:Input Locale" combination for Australia and New Zealand:
http://www.microsoft.com/globaldev/reference/winxp/xp-lcid.mspx
For example, for Australia you'll note that the code is "0c09:00000409". The
"0409" is the input locale for "English (US)". I believe what I need is
"0c09:00000c09", which signifies that GUI strings are localised to Australia
(part before the colon) and that user input is in Australian English (part
after the colon).
Why doesn't Microsoft want Australians to input in 'Strine?
If anyone can suggest a solution for Win2K and WinXP, I'd appreciate it.
Cheers, mate!
desil.