My 02D Cents
  • Welcome to my 02d cents
  • Multi-Language
    • Windows 10 Multi-Language ISO
      • Installing OSDBuilder
    • Office 365 Multi-Lang
      • Build - O365 Multi-Lang
      • Deploy - O365 Multi-Lang
  • General
    • Config Manager Install (manual) - WIP
      • Accounts / Groups
      • Prepare Server
        • Server - Drives
        • Install Services & Pre-Reqs
        • Registering ServicePrincipalNames for SQL
        • Open Server Ports for SQL
      • Install SQL
      • Install Power BI Report Server
      • Install SSMS
      • Configure SQL Memory Size
      • Install CU for SQL
      • Install WSUS
      • Install ADK & WinPE
      • Install MEMCM (TP) - Database
      • Install MEMCM
      • MEMCM - Resources / Downloads
    • Focused Sections
      • Applications
      • Reporting
      • MEMCM Client
  • Resources
    • Links
    • Scripts
      • MEMCM - Create Boundary & Collection
      • Task Scheduler - Auto Reboot
      • MEMCM - Boundaries Export
      • MSOL - Change AzureAD License
    • Tools
Powered by GitBook
On this page
  • Individual Applications
  • Application with logic

Was this helpful?

  1. Multi-Language
  2. Office 365 Multi-Lang

Deploy - O365 Multi-Lang

PreviousBuild - O365 Multi-LangNextConfig Manager Install (manual) - WIP

Last updated 2 years ago

Was this helpful?

When deploying O365 to various languages you will need to decide your deployment path.

  • Individual applications

  • Application with logic

  • Individual Task sequences

  • Task sequence with logic

Individual Applications

*Dont Think this option works in current MEMCM* This option would potentially consume the most storage resources.

Each language would require its own application and the install resources would be duplicated times the number of languages you were supporting.

When setting the command to install just point to the .XML you created for the specified language.

setup.exe /configure en-us.xml

Application with logic