Planning and Deploying International Client Packs

An ICP displays the user interface elements of the SMS client in the language of the client's operating system. An SMS user who has a localized SMS client and a localized operating system can use SMS to install software and participate in remote control sessions using the SMS client user interface in their own language. Users can also read dialog boxes and menus of the Manual Client Installation Wizard, SMSman.exe, Advanced Client Installer, and the Systems Management icon in Control Panel in their own language. ICPs consist of the following localized files:

  • Legacy Client

    • Capinst.exe

    • SMSman.exe

    • A few small supporting files

  • Advanced Client

    • Client.msi

    • Client.mst

    • A few small supporting files, including language resource files

Deploying an SMS ICP in a large environment is a project that requires planning, testing, and then deployment. The phases of the project include design, testing, and installation.

There are a variety of issues you must design and test for while planning an SMS ICP deployment, such as:

SMS site server localization ICPs are installed only on U.S. English site servers.

Client operating system localization ICPs are available for many different localized operating systems, but not all localized operating systems are supported.

Effect on both your LANs and your WANs Legacy Clients receive ICP software from networked resources.

Effect on the end user Users might be negatively affected if your network cannot adequately support their needs when clients are receiving ICP software.

Deploying an ICP is similar to deploying a service pack. For example, newer program files replace older program files. Deploying an ICP updates CAPs and Legacy Clients using the same mechanism. However, deploying an ICP is dissimilar to deploying a service pack because it does not do anything to the site server except update the client source files. Deploying an ICP does not update files for server components, make changes to the database schema, or perform other non-client upgrade functions.

For More Information

Did you find this information useful? Please send your suggestions and comments about the documentation to smsdocs@microsoft.com.