The following sample scenarios represent common Microsoft System Center Configuration Manager 2007 configurations in multilingual environments.
- U.S. English operating systems without
ICPs
In this scenario, an international corporation has all its Configuration Manager 2007 site servers in numerous countries/regions in U.S. English. All Configuration Manager 2007 clients run on localized operating system languages. However, Configuration Manager 2007 ICPs are not applied. All users view the U.S. English Configuration Manager 2007 client. This decision was made to keep all Configuration Manager 2007 sites at the exact same version, to help minimize administrative operating costs, to have fewer versions and deployments, and to minimize managing localized Configuration Manager 2007 updates. This is because Configuration Manager 2007 updates must be requested for each Configuration Manager 2007 localized version. This example company provides translated screenshots of the U.S. English client, when necessary.
- U.S. English operating systems with
ICPs
In this scenario, an international corporation has all its Configuration Manager 2007 site servers in numerous countries/regions in U.S. English. All Configuration Manager 2007 clients are installed on computers running localized operating systems. ICPs provide Configuration Manager 2007 clients with a localized interface.
- Existing site servers in an existing
mixed-language operating system infrastructure
In this scenario, each server operating system and SQL Server code page that it uses presents planning challenges. The servers that are in use now will be used as Configuration Manager 2007 site servers. The servers might not run localized operating systems. For example, you might find that the server you have been given for use in Kyoto, Japan runs a U.S. English operating system. Your server in Beijing runs a Simplified Chinese operating system. In this example, you will install the U.S. English Configuration Manager 2007 server in Kyoto. The server in Beijing will continue to run Simplified Chinese. In this scenario, the SQL Servers involved must use the 1252 code page.
- New servers in a mixed operating system
language infrastructure
In this scenario, you must determine who will administer your computers, and what your corporate policy is regarding operating system language installation. You must consider the language requirements of those that use the Configuration Manager console. Is the current language localized or enabled? Does it make sense to localize Configuration Manager 2007 on that basis? Can you maintain separate versions, service packs, and hotfixes for the U.S. English, localized language, and ICP versions of Configuration Manager 2007? In what languages must you view your clients? If only one language is required, then you can install a localized Configuration Manager 2007 site server. However, if you require multiple client languages, then you must use the U.S. English version of Configuration Manager 2007 and apply an ICP on the site server.
- Single language environment
If a Configuration Manager 2007 site consists of computers running a localized operating system version, such as German, and you want to administer the site in German, and you also want to have all clients display a German client interface, then install the German localized Configuration Manager 2007 version. In this case, there is no need for an ICP. You can add the site to a hierarchy of other Configuration Manager 2007 language versions. If you have other clients with localized operating systems in the site, such as Italian and Chinese, then those clients will use the U.S. English Configuration Manager 2007 client.