The primary language selected in the Office Customization Tool determines the Shell UI language. When deploying from a local source, we recommend that you use the Office Content Delivery Network (CDN) as a backup source for language packs.įor more information on standard deployments, see Plan your enterprise deployment of Microsoft 365 Apps. For more information, see Download the installation files for Microsoft 365 Apps. If you deploy Office from a local source on your network, you must download your languages to that source, in the same way that you download the Office package. To do so, select the languages you want to deploy in the Language section when creating the configuration file in the Office Customization Tool. To deploy Microsoft 365 Apps in multiple languages, you need to include the additional languages in the Office packages you create. Deploy multiple languages as part of deploying Office The setup will add the selected language to the user's device. If a user needs another language, they can just rerun the process for each required language. When users install Office from the Software page, they select a language from the Language drop-down box. If your organization allows it, users can install Microsoft 365 Apps languages directly from the Office 365 portal. Install languages from the Office 365 portal This article also includes the list of supported languages and details on how Office conserves network bandwidth when downloading language packs for deployment. If you use some languages only as editing tools, you can deploy just the proofing tools instead of full language packs to conserve network bandwidth.If you deploy a subscription version of the Project or Visio desktop app to a device that already has Office installed, you can automatically deploy them in the same languages as the installed version of Office.Creating separate packages for different language sets can make the Office deployment difficult to manage. When building Office packages to deploy, include all the language packs you plan to deploy in each package.If you upgrade from a Windows Installer (MSI) version of Office, you can automatically install the same languages as a previous MSI installation.When adding languages to an existing deployment of Office, you can deploy just the language packs, rather than the full version of Office.If you deploy Office from a local source on your network, use the Office Content Delivery Network (CDN) as a backup source for language packs that might not be available at that local source.Automatically install the same languages as the operating system.When deploying multiple languages in a large organization, we recommend these best practices: If a setting isn't yet available in the OCT, steps are given for creating the configuration file in a text editor. The steps in this article assume that you're deploying with Configuration Manager or the Office Deployment Tool, and that you use the Office Customization Tool (OCT) to create the configuration files for your deployment. You can deploy multiple languages by including those languages directly in the Office packages, or you can deploy languages as a separate package, after Office is already installed. In general, you deploy languages for Microsoft 365 Apps with the same process and tools that you use to deploy Office itself. For example, you can't use language packs downloaded from the Volume Licensing Service Center (VLSC) with Microsoft 365 Apps. You can't use language resources for Windows Installer (MSI) versions of Office with Microsoft 365 Apps, which uses Click-to-Run.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |