To determine which languages are required at which sites or locations in your organization, you must gather information about:
- Corporate standards for the operating system
language version that Configuration Manager 2007 is installed
- Operating system language versions of the
clients in each site.
- The language skills of operations personnel
at each site location.
- The language skills of end users and
associated organizational standards for application localization at
each site location.
In each of the Configuration Manager 2007 sites in your organization, determine which Configuration Manager 2007 language versions are within your organizational standards. Next, determine what operating system language versions are required by client computers.
- Are there other client operating system
- Who creates and distributes packages?
- Who manages site settings?
- Do your operations personnel require a
particular Configuration Manager 2007 site server language
- In some situations, you must request
exceptions to any corporate standards if the configuration of
Configuration Manager 2007 server and client languages requires
language versions outside your corporate standards.
While planning your Configuration Manager 2007 site hierarchy, plan to name all network resources by using standard ASCII characters, including codes 0 through 127. This includes all computer names, share names, user names, user group names, domain names, and site codes.
After you have fully planned your multilingual Configuration Manager 2007 site hierarchy and established your sites, administrators and users can effectively useConfiguration Manager 2007 . For example, when an Configuration Manager 2007 central site administrator in Vancouver uses an English-language version of the Configuration Manager 2007 console to send an advertisement to an Configuration Manager 2007 client in Amsterdam, the Dutch-speaking user reads Configuration Manager 2007 dialog boxes in her own language because the International Client Pack (ICP) was applied and it provides the localized client software. The administrator of the site sees the Dutch-language computer name and other client data using the correct Dutch-language character display.
Default Collection Names
Any collection, package, or advertisement that is passed down a hierarchy assumes the name it is assigned at the site where it is created, and appears with that same name throughout the hierarchy. The default collections are a special case of this.
As each site is created, the default collections are created at that site, and the name of the collection reflects the language of the site. When the site attaches to a parent site, the collection definitions for the default collections are overwritten with the definitions used at the parent site. If the child and parent use different languages, the collection names are displayed in the language of the parent site. This extends all the way up the hierarchy: default collections are assigned the name used at the central site. The implications of this depend on the code pages used by the affected sites. A code page is a definition of the bit patterns that represent specific letters, numbers, or symbols for character or Unicode data. For additional information about code pages, see the "SQL Server Code Pages" section later in this chapter.
- If the two sites are using the same code
page, the Configuration Manager 2007 console at the child site
displays the collection name correctly, but it is in the language
of the central site.
- If the two sites are using different code
pages, the Configuration Manager 2007 console at the child site
cannot display the collection name correctly. The names of the
default collections are unreadable.
If the two sites use the same code page, administrators at the child site must learn to recognize the names of the default collections when they are in the language of the central site.
If the two sites use different code pages, at the central site, you can rename the default collections using only ASCII characters. The collection names are then displayed correctly at all sites. In addition, assign ASCII-only names to all collections, packages, and advertisements at any site that is or might later become a parent to a site using a different code page.
An alternative method is to maintain an Configuration Manager 2007 console at the child site on a computer that uses the language of the central site.