1. DSK350 Deploying Microsoft Windows XP in a Multilingual Environment Yong Rhee Support Escalation Engineer EPS - Windows Server Microsoft Corporation

2. Agenda The Challenge Meeting the Challenge Implementing the Solution SetupDeploymentAdministration Change and Configuration Tips and Best Practices

3. The Challenge Problems of Multilingual Environments and International Deployments

4. The Challenge: For Admins Multiple platforms required n images x n languages x n regions x n hardware Each platform requires different applications, drivers and updates Testing, roll-out and maintenance Localization scheduled impact deployment Delay of localized Service Packs Expensive (time-consuming, support costs)

5. The Challenge: For Users Multilingual document creation and exchange is painful Incompatible formats, encodings ( (C:¥windows¥system32, ?????, * * * *) No common platform Some users need two PCs, or dual boot Roaming between machines is an adventure Users of certain languages must wait Some languages aren’t supported at all

6. Meeting the Challenge

7. Microsoft Windows XP Language Support

8. What’s New in Microsoft Windows XP? Improvements over Microsoft Windows 2000 9 New Locales (+ 1 Invariant Locale) Punjabi, Gujarati, Telugu, Kannada, Kyrgyz, Mongolian (Cyrillic), Galician, Divehi, Syriac Text Services Framework Advanced text input methods for speech, handwriting, etc. New Regional Options control panel Simplified functions, terminology Simplified language installation New Location, Default User Settings

9. What’s New in Microsoft Windows XP SP2? Improvements over Windows XP Even more locales Bengali, Croatian (Bosnia and Herzegovina), Galician, Sami (7 locales, Malayalam, Maltese, Maori, N. Sotho, Quechua (3 locales), Serbian-Cyrillic, Swahili, Tswana, Welsh, Xhosa, Zulu First (ever) language update in a service pack MUI-friendly SP

10. What’s New in Microsoft Windows XP MUI? Improvements over Windows 2000 Closer parity to localized versions (97%): 9 more ‘MUI-only” languages (33 total) Many more localizations (LIP) Improved SP eXPerience Better documentation Enhanced deployment functionality Better application compatibility

11. Microsoft Windows XP: The benefits Administrators benefit from: Fewer differences between language versions Smaller image matrices Easier configuration and maintenance Lower support costs Users can Enter and read content in any language Run apps in any language

12. Now Now Windows XP MUI Pack Microsoft Windows XP MUI Pack: The benefits Deploy & Maintain n Operating Systems n Service Packs n Release Schedules Deploy & Maintain 1 Operating Systems 1 Service Packs 1 Release Schedules

13. Implementing the Solution SetupDeploymentAdministration Change and Configuration

14. Setup: Things to be aware of Most languages now installed by default Basic Language Collection (always installed) East Asian Language Collection Complex Script Language Collection No changes necessary to answer files: Installing an EA or CS language will install all of the languages in the same collection Winnt, winnt32 /rx:lang or /copysource:lang switches only needed when installing East Asian languages and Complex Script (CS).

15. Implementing the Solution SetupDeploymentAdministration Change and Configuration

16. Deployment: Pre-deployment considerations Determine the right version Localized version or Microsoft Windows XP MUI Pack? Current versions and upgrade paths Determine regional and language needs What languages are needed by users? Documents, e-mail, web sites, etc. How frequently do users roam? What languages are ANSI apps localized into? Region-specific applications? Determine hardware requirements

17. Implementing the Solution SetupDeploymentAdministration Change and Configuration

18. Administration Domain, Machine and User Names Windows XP supports all Unicode characters (UTF-8 for DNS) Reality: limit the characters used Down-level clients require ASCII subset Roaming users may be locked out if input languages are not available at winlogon, or if Language Collections not present

19. Administration Active Directory issues Active Directory supports Unicode for naming of Active Directory objects, but… … in heterogeneous environments, use characters common to codepages of all domain servers and clients for Active Directory objects Trust relationship issues Object name rendering Active Directory supports a single sort order, which may or may not match that specified on other servers or clients Caution: Schema objects created during dcpromo will remain in Default User’s UI – if MUI, change language first

20. Administration Application compatibility Generally, any well-behaved localized application will run on Windows XP World-ready applications (Unicode enabled, etc) will ‘just work’ on any language version of Windows XP ANSI applications (non-Unicode) require the ‘Language for non-Unicode programs’ setting to match the appropriate Note: Overlooking ‘Language for non-Unicode Programs’ #1 cause of localized application problems in Windows 2000

21. Administration Application compatibility: Caveat ‘Language for non-Unicode programs’ is: Per system (not per user) Limited to one language at a time Corporate customers typically run many different ANSI apps in multiple languages Cannot easily run a Japanese ANSI order- tracking app and a Russian ANSI database app Not easy for users of different language version ANSI applications to share computers

22. Administration App compat recommendation Port ANSI applications to Unicode (rewrite from the ground up) or, Use Microsoft Layer for Unicode (MSLU) to port apps to Unicode with minimal effort Recompile components as Unicode Relink to include MSLU library (unicows.lib) Helps run Unicode applications with Windows 95/98/ME

23. Administration Service Pack issues Windows 2000 SP1 & 2 broke MUI Poor test coverage Education issue (MUI not well understood) Resources updated MUI design limitation (V1) Windows XP resolves these problems Design improvements Resource Versioning Check version matching Limit resource change in SP, centralized location for critical resource updates MUI scenarios in place

24. Microsoft Windows XP Language Support

25. Service Packs on MUI

26. Administration Language and MUI Pack installation East Asian support files require 230MB and a reboot MUI languages can be deployed/installed individually using Microsoft Windows Installer packages Saves disk space: install on-demand Current user & default user can be set at command line… …or applied through provided transforms

27. Implementing the Solution SetupDeploymentAdministration Change and Configuration

28. Change and Configuration Group policy: the good… MUI language can be set Group Policy Allows quick and easy configuration Reduces support – keeps users out of trouble Quick way to force all users to another language if update or removal becomes necessary Can be applied to individual users by filtering the effects through Security Groups

29. Change and Configuration Group policy: the bad… MUI language is the only Regional and Language Options setting controllable through Group Policy No Standards and Formats policy No Input Languages policy No Location policy Restricts Users to one language, rather than a subset of those installed

30. Change and Configuration Changing the Default User Settings Default user settings determine the input languages available at winlogon Can now be configured through Regional & Language Options cpl Also through new unattend keywords: [RegionalSettings] InputLocale DefaultUser=“0409:00000409” UserLocale DefaultUser=“0409”

31. Resources Tips & Tricks Best Practices

32. Tips and Tricks Automating a User’s Regional Settings Simple way of automating settings in desktop lockdown scenarios Call rundll32.exe to run the Regional Options control panel silently Pass in answer file containing the desired settings Useful in Group Policy-applied logon scripts, etc. Caution: Don’t use this technique to set the system locale

33. Tips and Tricks Limiting Regional & Language Options Customize available options by binding dialog controls to pre-defined choices Eliminate option paralysis! Simplify user tasks Generate answer file from user selection Call rundll32 with generated answer file Rundll32 shell32,Control_RunDLL intl.cpl,,/f:”c:\unattend.txt”

34. Summary: Best practices Avoid non-ASCII characters in domain, computer, user and network resource names—unless you can guarantee homogeneity of the environment Install all language support on all machines (as space allows) Set the ‘Language for non-Unicode programs’ to match the language of the most widely used ANSI applications

35. Summary: Best practices for Windows XP MUI Pack To match a localized system as closely as possible, ensure that: Language for non-Unicode programs = Language for non-Unicode programs = Standards and formats = Standards and formats = Default User UI and Input Language = Default User UI and Input Language = Current User UI and Input Language = Current User UI and Input Language = Shell UI font setting = (Japanese only)

36. Summary: Best practices for Windows XP MUI Pack (cont’d) Provide user access to MUI languages in the Active Directory Consider creating ‘global’ and ‘regional’ core images, to hold language-neutral and language-specific content Recommendations: If possible, set the UI language to English when deploying SPs, server and tools and apps

37. Resources General guidelines on internationalization: http://www.microsoft.com/globaldevhttp://www.microsoft.com/globaldev General questions: drintl@microsoft.comdrintl@microsoft.com Developing International Software: (Available at the on-site bookstore)

38. Tech-Ed 2005 Break-Out Sessions ARC303: Planning a Global Release: Many countries, Many Languages, One Process BAP347: Microsoft Business Solutions-Axapta: a Truly Global Business Application DAT290: Databases for the World: Designing Multilingual Databases Using SQL Server 2005 DBA319: Databases for the World: Best Practices for Search in Multilingual Data Sets Using SQL Server Collation for Sorting and Indexing DSK350: Deploying Windows XP in a Multilingual Environment DSK345: Deploying Office 2003 in a Multilingual Environment DEV323:.NET Framework: Think Global! Custom Cultures and International Data MSG369: Supporting East Asian Languages in Global Exchange Deployments WEB326: ASP.NET 2.0: Going Global Gets Easier! New Localization Features in ASP.NET 2.0

39. Resources Dr. International’s Clinic Dr. International’s Clinic: Booth in the Community Cabana International Experts available all week long

40. Resources Resource 1: http://www.microsoft.com/GlobalDev http://www.microsoft.com/GlobalDev Resource 2: http://www.microsoft.com/GlobalDev/articles/ winxpintl.asp http://www.microsoft.com/GlobalDev/articles/ winxpintl.asp Resource 3: http://msdn.microsoft.com Resource 4: http://www.unicode.org

41. Your Feedback is Important! Please Fill Out a Survey for This Session on CommNet

42. © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.