Information in this document, including URL and other Internet web site references, is subject to change without notice and is provided for informational purposes only. The entire risk of the use or results of the use of this document remains with the user, and Microsoft Corporation makes no warranties, either express or implied. The example companies, organizations, products, people and events depicted herein are fictitious. No association with any real company, organization, product, person or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
© 1999 Microsoft Corporation. All rights reserved.
Microsoft, MS-DOS, MS, Windows, Windows NT, and Windows 2000 are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A. and/or other countries.
The names of actual companies and products mentioned herein may be the trademarks of their respective owners.
These release notes contain late-breaking information specifically about functionality in Microsoft ® Systems Management Server (SMS) version 2.0, Service Pack 1 (SP1) that is not available in the product documentation or in the general release notes. Please read these release notes thoroughly before installing Internation Client Pack 4 (ICP4) of SMS 2.0 SP1.
The SMS International Client Packs (ICPs) are cumulative. Any client language that exists in a previous ICP will also exist in all subsequent releases. For example, ICP 5 includes all client languages that existed in ICP1, and the languages introduced in ICP4.
Workaround: None.
This readme file might contain notes that apply to languages that are not included in this International Client Pack (ICP). This is because each readme file includes the release notes for previous ICP releases; for example the readme for ICP1 SP1 includes the notes from the initial release of ICP5.
Workaround: Ignore any information regarding languages that are not included in your ICP.
Installation of any ICP on SMS servers running any language other than English is not supported.
Workaround: Install ICPs only on English SMS site servers.
You cannot uninstall ICPs.
Workaround: If you decide you want to return your system to its non-localized version, you must reinstall your English SMS site server.
In SMS 2.0, all client languages contained in an ICP are installed 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 ICP4 which contains all the languages of ICP1 and ICP4.
Workaround: None.
Any files in your SMS site that were provided by Microsoft Product Support to address a specific problem with SMS, including files downloaded on the advice of a Knowledge Base article, are overwritten when an ICP is installed.
Workaround: After installing the ICP, install ICP versions of these special files to regain the functionality those files provided. Microsoft Product Support can provide the ICP versions of these files.
The WMI files bundled in the self-extracting executables WBEMcore.exe and WBEMsdk.exe are not localized. Some WMI-generated messages or dialogs will appear in English.
Workaround: When you install WMI in local language environments, use the /s command line option, which will disable the English messages and dialogs.
Localized WMI utility files are available for French, German, and Japanese Windows NT 4.0 SP4 operating systems. Use these utility files if you require the localized version instead of the English version that is already installed on the client.
These WMI files are located in the \Support\WBEMutil\<processor>\<language ID> directories.
Workaround: None.
To distribute an unattended upgrade of Windows 95 to Windows 98 for Czech, Greek, Hungarian, Polish, Russian, and Turkish using the Win98.sms file, you must modify a command-line parameter.
Workaround: To modify the command-line parameter, perform the following steps:
To change the command line after the package has been created, edit it in the package property page in the SMS Administrators console.
To distribute an unattended upgrade of Windows 95 to Windows 98 for Client Languages using the Win98.sms file, you need to use the files, Cabsrc.inf, W95toW98.EXE and W95toW98.inf. These files are located on the CD at \smssetup\SCRIPTS\<languageID>\win98\I386 and need to be copied to the Package Source Directory.
SMS 2.0 ICP 5 does not support Arabic and Hebrew clients running 16-bit versions of Windows. However, the SMS client will be installed on these systems if they are present in the hierarchy.
Workaround: If Arabic or Hebrew 16-bit clients are added to your site, do not try to maintain or control them with SMS.
To read data collected from or directed to clients using a specific language, you must run the appropriate language version of the SMS Administrator console on a computer that is using that language.
Workaround: For each client language other than Japanese, Korean, Simplified Chinese, or Traditional Chinese, maintain a computer running 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 DBCS language 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 NT language pack to the site server and SMS site database computer in each site where the SMS administrator console will be used to view data in these languages.
To install a language pack:
Localized versions of HealthMon require a localized version of the Microsoft Management Console (MMC) to display fully localized text.
Workaround: To install the localized version of MMC, run the Mmcsetup.exe file from the HealthMon\<proc>\ <langdir>\MMC\ directory in the ICP compact disc, where <proc> is the processor (i386 or Alpha) and <langdir> is the directory for the language you want to use.
You cannot use the ICP5 compact disc to install ICP5 on a secondary site.
Workaround: To install or upgrade ICP5, you must upgrade the secondary site from the parent site by performing the following steps:
If your site hierarchy uses more than one character set, you must specify code page ANSI 1252 or ISO 8859-1 Latin 1 when you install SQL Server for your site databases.
Workaround: None.
If all the following criteria apply to your SMS site, you must manually update the SMS Provider after you apply ICP5:
Workaround: Update the SMS Provider with files from the ICP5 compact disc by performing the following steps:
where <proc> is the processor (i386 or Alpha).
In some language versions of the SMS Administrator console, the types and levels used in the product compliance database might be longer than the permitted string lengths. If this happens, the string will be truncated. This is an inconvenience, but it is not a fatal error.
Workaround: Ensure that the types you use for product compliance are 20 characters or fewer and that the levels are 30 characters or fewer. One way to do so is to use the English language types and levels, which fit within these restrictions.
The general guideline is that the release level (RTM, SP1, SP2, and so on) of the ICP must match the release level of the English site server installation (RTM, SP1, SP2, and so on). Previously released ICPs are not compatible with later versions of the SMS site server software.
If you use SMS 2.0 SP1 to upgrade an SMS 2.0 installation that has an ICP installed, the ICP client bundles the files that are to be overwritten. After these files are overwritten, only English is supported on the clients in that site. For example, if you have an English SMS site server and you have installed ICP3, and then you upgraded to SMS 2.0 SP1, only English clients are supported.
Workaround: After you upgrade the site server to SMS 2.0 SP1, install the SP1 version of the ICP you require. For example, install the SP1 version of ICP3 on your upgraded SMS 2.0 SP1 site server to obtain SMS client local language support for the ICP3 languages.
You must manually add "Administrators," in the client language, to the Permitted Viewers list in order to remotely control Windows NT or Windows 2000 clients that are using any of the following languages:
Workaround: Modify the configuration of the Remote Tools Client Agent by adding the word for "Administrators", in the client's language, to the Permitted Viewers list. Repeat this procedure for each of the listed languages that you want to support when you remotely control the clients.
After these steps are completed, the client can be remotely controlled from any SMS Administrator console in the site.
SQL Server code pages based on OEM character sets, such as the 850 code page for Western European languages, are not supported in SMS 2.0.
Workaround: Do not install SQL Server with an OEM code page on any site. Instead, use code page ANSI 1252 or ISO 8859-1 Latin 1.
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:
Click the Regional Settings tab, select the appropriate setting, and then select the Set as system default locale check box.
-or-
In Windows 2000, click the General tab, click Set default, and then select the appropriate locale.
The following table shows which languages are supported in each ICP. The last four digits of the directory names are the language IDs These directory names will help you locate the language-specific files on your SMS 2.0 CD or on your SMS 2.0 installation.
| Directory Name | Language | First Released |
| 00000409 | English | ICP1 |
| 0000040C | French | ICP1 |
| 00000407 | German | ICP1 |
| 0000040A | Spanish | ICP1 |
| 0000041D | Swedish | ICP4 |
| 00000413 | Dutch | ICP4 |
| 00000410 | Italian | ICP4 |
| 00000414 | Norwegian | ICP4 |
| 00000406 | Danish | ICP4 |
| 0000040B | Finnish | ICP4 |
| 00000416 | Portuguese-Brazilian | ICP4 |
| 00000816 | Portuguese | ICP4 |
| 00000405 | Czech | ICP4 |
| 00000408 | Greek | ICP4 |
| 0000040E | Hungarian | ICP4 |
| 00000415 | Polish | ICP4 |
| 00000419 | Russian | ICP4 |
| 0000041F | Turkish | ICP4 |
| 00000411 | Japanese | ICP5 |
| 00000412 | Korean | ICP5 |
| 00000404 | Traditional Chinese | ICP5 |
| 00000804 | Simplified Chinese | ICP5 |
| 0000040D | Hebrew | ICP5 |
| 00000401 | Arabic | ICP5 |