Microsoft Virtual Academy Dean Yamada | Senior Premier Field Engineer, Microsoft Stephen Hall | Cloud Solutions Specialist, District Computers

Course Topics 01 | System Center Configuration Manager (SCCM) Deployment Best Practices 02 | Multi-language Deployment Considerations for Office 365 ProPlus 03 | Office 365 ProPlus with Azure Rights Management Services for IRM/Encryption 04 | Controlling access to Office 365 ProPlus & Services 05 | Office 365 and Exchange Migration Troubleshooting Common Gotchas 06 | New Office 365 ProPlus Customizations via Group Policy or XML 07 | New Updating and Repair Command-Line Options for Office 365 ProPlus

Microsoft Virtual Academy Module 2: Multi-language Deployment Considerations for Office 365 ProPlus Dean Yamada | Senior Premier Field Engineer, Microsoft Stephen Hall | Cloud Solutions Specialist, District Computers

Language packs, language interface packs (LIPs), Proofing Tools Importance of understanding Shell Context or Shell Transform –No automatic matching to the OS language for Shell Context Planning strategies for multi-national companies Module Overview

Office language packs, language interface packs (LIPs), Proofing Tools

Do you need the Language Pack or do you really only need the Proofing Tools? –How can I tell? Don’t forget about Companion Proofing Languages! All companies should check with their Microsoft Technical Account Manager/Microsoft Licensing on access to the volume licensing bits for the Office Multi-language Pack and Proofing Tools –Do you have access to the VLSC* ? Language interface packs Office language packs, language interface packs (LIPs), Proofing Tools, oh my!

Same disk-space-efficiencies of Office multi-languages in the past also applies to multiple Click-to-Run languages too! Differences in disk-space used for Click-to-Run builds?

CLICK-TO-RUN LANGUAGES VERSUS MSI-BASED INSTALLS/LANGUAGE PACKS DISK SPACE SIZES demo

Importance of understanding Shell Context or Shell Transform

With Office 365 Click-to-Run deployments, the first language listed takes over the Shell Context Menus –But re-running setup.exe with a different “first language” will take over the Shell Context Menus; last setup.exe install wins –Some regions require UI language by law Importance of understanding Shell Context or Shell Transform

As with Office MSI multi-languages in the past, decide how you will structure your installation source folders efficiently –Per geographic region? –Is EN-US acceptable as the Shell Context Menu for the majority of regions? –SCCM Application Model or Package Model? Do you want to allow users to choose a different language, post-deployment? Updating considerations for multi-languages for Click-to-Run or MSI Planning strategies for multi-national companies

UNDERSTANDING SHELL CONTEXT MENU BEHAVIOR AND MULTI-LANGUAGE PLANNING STRATEGIES demo

Resources

Additional MVA course: Office 365 ProPlus Deployment for IT Pros for-it-pros Resources

©2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, Office, Azure, System Center, Dynamics and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.