Frequently Asked Questions: SCSM 2010 International

How many versions of SCSM 2010 exist?

There are two editions of SCSM 2010: English and International.

Which languages are supported by international version of SCSM?

International version supports English and is localized to 10 more languages:

• Chinese Simplified
• Chinese Traditional
• French
• German
• Japanese
• Italian
• Korean
• Portuguese (Brazil)
• Russian
• Spanish

How can I install SCSM supporting English, German and French?

With the INTL build, you will have single setup experience which installs all 11 languages. You don’t have to install any individual language separately.

Is it possible to upgrade English version of SCSM to International?

It is not possible to upgrade from English to the International version SCSM.

Are you going to merge English and International versions of SCSM in some future?

Starting from SCSM 2010 Service Pack 1, we are going to ship English and International versions of SCSM as one version of the product (sim-shipping)

What are language requirements for Windows Servers used for installing SCSM components?

Windows Server

• Can be in any language (SKU & Display Language) supported by Windows Server
• The language of the server OS (SKU & OS Display Language) doesn’t impact the language of the client (console/browser) UI on the separate client computer.

What are language requirements for SQL Servers used for SCSM databases?

SQL Server

• Language SKUs should be the same for all SQL Servers used for SCSM SM Servers and Data Warehouse
• All SCSM SQL Servers (SMDB and DW) must have the same collation setting from the list of supported SQL Collations. You can register up to five SCSM management servers to a single SM data warehouse but all of the databases must have identical SQL collations. You can see that list in the SCSM Deployment Guide.
• When SCSM Setup creates databases for SM, it uses default collation of the SQL Server.
• Changing the default collations of the SQL Servers and the collation of the SM databases after installation is not supported. Please plan your SCSM / SQL Server and SCSM deployments accordingly.

What are language requirements for Windows computers running SCSM client UI (Console and Web Portal)?

Windows Client can be in any language (SKU & Display Language) supported by Windows Client OS

Which UI language will be shown on the client computer?

SCSM Console and Web Portal UI use a similar, but slightly different logic for deciding which language to show in the UI

• SCMS Console – depends on SCSM Edition (EN/INTL) and on OS Display Language setting of the client computer
• IE/Portal – depends on SCSM Edition (EN/INTL) and on the client browser (IE) encoding setting

* SL stands for “su[pported language” (or one of 10 languages we localized SCSM to)
** NSL stands for “non-supported language”. It is still possible to enter and use data in SCSM in any language supported by Windows. But the UI components in the COnsole and in the Portal will be shown only in one of the supported languages.

Examples

• EN SCSM edition, Client OS Display Language is Italian => shows English UI
• INTL SCSM edition, Client OS Display Language is English   => shows English UI
• INTL SCSM edition, Client OS Display Language is German => shows German UI
• INTL SCSM edition, Client OS Display Language is Japanese   => shows Japanese UI
• INTL SCSM edition, Client OS Display Language is Swedish => shows English UI

User A uses SM console in German and adds a new entry (in German) to a list in the Library area. Where that entry will be stored, in which language and how to translate it to the other supported languages?

The console will save the value entered by the user in the German and in the English language packs.  English users will see the German value unless a user with an English console updates the value to be an English term.  If customers desire to localize the value into additional supported languages they can follow this blog post

Can I localize the management packs I developed myself?

You can localize your own management packs. See the “Localizing Management Packs” blog post for more details.

Other useful blog posts about localization in SCSM are:

• Localizing Forms – Service Request Example
• Grid view configuration and what it means

Can I localize the SCSM self-service portal myself?

You can’t localize the SCSM self-service portal yourself. It takes localized data from the localized resources as well as from the sealed and unsealed management packs. The same management packs are used by the console, and there is a lot of dependencies between them, so for avoiding the “mixed UI language” scenario it is necessary to localize the entire product, not just some its part.

Is SCSM globalized?

Globalization is the ability to work with data in any language supported by Windows, including multi-language scenarios.

• SCSM is a globalized product, so you will be able to enter data in any language supported by Windows, even if that language is not included in the list of 10 languages we are localizing the product to.
• SCMS takes into account regional settings of the client OS. For example, the date/time format displayed by the SCSM Console using US regional settings will be different from EN-UK one.
• The ability to search and sort data in SCSM is defined by SQL Collation. You should select the collation which matches the primary language of data you are expecting in SCSM.
• If your primary language is not in the list of supported collations, the behavior of the sorted lists and search results is defined by behavior of SQL Server. We can’t guarantee that sorting, filtering, querying and search will work correctly in every possible combination of languages. Please see the SQL Server documentation for more details.

If you have questions about the International version of SCSM, feel free to ask them in the SCSM Forum.