How do I automate which PCT Template to use based on the computer locale?

Article:HOWTO2899  |  Created: 2006-03-23  |  Updated: 2006-04-05  |  Article URL
Article Type
How To

In one site I have computers using a variety of locales. The PCT templates I have built are built in the corresponding languages and seem to work when deployedto a computer using the same language as the template. So now that those things work, how can I automate which PCT template to use based on the computer locale?

PC Transplant 6.1

PC Transplant was not designed to check the locale a computer is running on and determine which template to use to capture that computer. This functionality may be included in a future release of PCT, but as of now this must be determined by the users.


There are two possible solutions to this issue:

  1. Altiris has come up with a tool that is attached to this article. The instructions for the tool are also attached. This codepage tool will return values to Deployment Server so users can perform additional jobs based on the value we get from the tool.  The value varies depending on the locale of the computer. Please see the attachments on this ticket for additional help.
  2. Another solution to this issue is to build a script which looks at a key in the registry and based on the value of the registry selects which template to use.


The Key this information is stored in is HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\Language\Default

The Values are:

080a—Spanish (Mexico)

0409—English (United States)

040c—French (France)

0407—German (Germany)


0804—Simplified Chinese


If you do a search for LCID and a language online you should be able to find a longer list. These are the languages we support with one possible value for the language, but you may have varying versions of these languages depending on where you are in the world.

Note:  On Simplified Chinese, Japanese, and English, the 0 was removed on some pages and on others the 0 was there.

Attachments (108 kBytes)
How to use codepage.doc (60 kBytes)

Legacy ID


Article URL

Terms of use for this information are found in Legal Notices