When planning for the support of multiple languages in your site hierarchy, you should consider the following:
To determine which languages are required at which locations in your organization, you need to gather information about the international end-users for both client and administrator areas. In each of your organization’s SMS sites, what languages are the clients localized to? What SMS server language version can support a given mix of languages? In general, it is easiest to think of the site server language support as being freely intermixed and the local-language client support under the servers as being more restrictive (except for the English-language server, which supports all SMS client languages).
For example, because the Tokyo office of our example company has entirely Japanese-language localized clients, the SMS administrators in Tokyo can simply run the Japanese-language server. However, the administrators in Amsterdam must support Dutch, French, and English localized clients, and so choose the English-language version of SMS for their primary site server.
Because ICPs are cumulative and are released as they become available, you might need to plan the deployment of language-specific versions of SMS server and client software when the ICP you need becomes available. ICPs have their own setup program and can be installed sequentially onto a site server without any change to the existing clients. All new clients will be able to install in any of the languages from the most recently installed ICP.
When timing your deployment, you should also consider the size of the ICPs in relation to the available bandwidth of your network. The later versions of ICPs (that is, the higher-numbered ICPs) will be larger because each consecutive version contains the languages of the previous versions. You should plan the deployment of any language client pack for light network usage periods to minimize degradation of network performance for your users.