International Client Pack

International Client Pack Setup Does Not Prevent Installation on Non-English Language Secondary Site Servers

Although it is possible to run International Client Pack (ICP) Setup on non-English language secondary site servers, this type of installation is not supported. ICP setup is supported only on English SMS site server on English operating system.

Note

ICP Setup prevents installation on non-English language primary site servers.

WORKAROUND:   Do not install an ICP on non-English language site servers.

SMS International Client Packs Are Cumulative

The SMS ICPs are cumulative. Any client language that exists in a previous ICP also exists in all subsequent releases. For example, ICP2 includes all client languages that existed in ICP1.

WORKAROUND:   None.

Upgrading SMS 2003 International Client Pack Installations

Site configurations that mix release levels of the English language site server and an installed ICP are not supported. Previously released ICPs are not compatible with later versions of the SMS site server software.

WORKAROUND:   After you upgrade the site server, immediately install the matching version of the ICP that you are using or a higher-numbered ICP. Do not upgrade a site server that supports localized clients until you are ready to install the matching version of the ICP that you are using, or a higher-numbered ICP.

For example, if you have a site server that is using SMS 2.0 SP5 ICP1, and you upgrade that site server to SMS 2003, you must immediately install SMS 2003 with an ICP level equal or greater than ICP1.

Note

The ICP naming scheme in SMS 2003 has the following changes:

SMS 2003 ICP1 is equivalent to SMS 2.0 ICP1

SMS 2003 ICP2 was previously named SMS 2.0 ICP4

ICP5 is no longer available in SMS 2003

International Client Packs Cannot Be Uninstalled

You cannot uninstall ICPs.

WORKAROUND:    If you decide that you want to return your system to its non-localized version, you must reinstall your English SMS site server or restore your backup.

All Client Languages Install at the Same Time

In SMS 2003, all client languages contained in an ICP are installed on the site server at the same time. You cannot install the client languages individually. For example, if you want to install an Italian SMS client, you must use ICP2, which contains all of the languages in ICP1 and ICP2.

WORKAROUND:   None.

Viewing Data in Multiple Languages

To view data collected from or directed to clients that are using a specific language, you must run the appropriate language version of the SMS Administrator console on a computer running an operating system of that same language.

WORKAROUND:   For each client language other than Japanese, Korean, Simplified Chinese, or Traditional Chinese, maintain a computer running an operating system in that language. On that computer, install the English language SMS Administrator console (or localized version for German and French). The system default locale setting and operating system language of the computer running the SMS Administrator console must match the language of the data you want to view or enter.

To view data in Japanese, Korean, Simplified Chinese, or Traditional Chinese, maintain a computer running that language. On that computer, install the appropriate localized version of the SMS Administrator console. For example, because the English-language server does not support display of these double-byte character set characters, an administrator in Vancouver who wants to view data from Tokyo should set up a Japanese-localized computer running the Japanese version of the SMS Administrator console in order to view the data in the Japanese language.

In addition, you must apply a Windows language pack to the computer where the SMS Provider is installed. The SMS Provider resides on either the site server or on the computer where the SMS site database is installed. The SMS Provider is accessed by the SMS Administrator console to view data in these languages.

SQL Server OEM Code Pages

SQL Server code pages based on OEM character sets, such as the 850 code page for Western European languages, are not supported in SMS 2003.

WORKAROUND:   Do not install SQL Server with an OEM code page on any site. Instead, use Windows code page ANSI 1252 or ISO 8859-1 Latin 1.

System Default Locale Setting Must Match Operating System Code Page

SMS clients and servers must have a system default locale setting that matches the operating system language.

WORKAROUND:   Do not change the system default locale setting to any language other than that of the operating system.

To set the system default locale in Windows 2000 or Windows NT

1. In Control Panel, double-click Regional Options.

2. Click the General tab.

3. Click Set default, select the appropriate locale, and then click OK

To set the system default locale in Windows XP or Windows Server 2003

1. In Control Panel, double-click Regional and Language Options.

2. Click the Advanced tab.

3. Under Language for non-Unicode programs, select the desired language, and then click OK.

Installing an English Advanced Client over the International Client Pack Advanced Client Is Not Supported

Installing the English Advanced Client over the International Client Pack (ICP) version of the Advanced Client uninstalls all localized resources. Although the installation succeeds, this procedure is not supported.

WORKAROUND:   To avoid installing the English Advanced Client over the ICP version of the Advanced Client, ensure that after the ICP version is installed, all copies of the English Advanced Client are removed from installation points on site systems.

Languages Supported by ICPs

The following table shows which languages are supported in each ICP. The last four digits of the folder names are the language IDs. These folder names will help you locate the language-specific files on your SMS 2003 CD.

Setting the AutomaticAnsiToOEM Option for SQL Server

The default installations of SQL Server 7.0 enable the AutomaticAnsiToOEM option. However, if the computer running SQL Server will process data from non-U.S. code pages, you need to disable the AutomaticAnsiToOEM option.

WORKAROUND:   Disable the AutomaticAnsiToOEM option.

To disable the AutomaticANsiToOEM option for SQL Server version 7.0

1. In the SQL Server Client Network Utility, click the DB Library Options tab.

2. Clear the Automatic ANSI to OEM conversion check box, and then click OK.