Build - O365 Multi-Lang

First we need to grab the Office Deployment Tool from Microsoft

LogoDownload Office Deployment Tool from Official Microsoft Download CenterMicrosoft Store - Download Center

When launching the officedeployment~.exe you will be prompted to select a folder as this will extract the needed files.

After the files have been extracted you should have a setup.exe and a few example.xml files.

You can build your .xml manually or use the Microsoft Configuration Service.

https://config.office.com/config.office.com

You can sign in with your organization account which in return will store all .xml’s created. If you choose not to log in you may click the create button hidden at the bottom of the page.

I created a single .xml for download only and individual .xml based on languages. This will vary based on your wants and needs.

LogoConfiguration options for the Office Deployment Tool - Microsoft 365 AppsMicrosoftLearn
<Configuration>
  <Add OfficeClientEdition="64" Channel="MonthlyEnterprise">
    <Product ID="O365ProPlusRetail">
      <Language ID="en-us" />
      <Language ID="zh-cn" />
      <Language ID="nl-nl" />
      <Language ID="fr-fr" />
      <Language ID="de-de" />
    </Product>
    <Product ID="AccessRuntimeRetail">
      <Language ID="en-us" />
      <Language ID="zh-cn" />
      <Language ID="nl-nl" />
      <Language ID="fr-fr" />
      <Language ID="de-de" />
    </Product>
    <Product ID="ProofingTools">
      <Language ID="zh-cn" />
      <Language ID="nl-nl" />
      <Language ID="en-us" />
      <Language ID="fr-fr" />
      <Language ID="de-de" />
    </Product>
  </Add>
  </Configuration>

Channel that you choose is important. You must get the proper channel name correct. Old naming will not work.

LogoOverview of update channels for Microsoft 365 Apps - Microsoft 365 AppsMicrosoftLearn
Explains the various channels
LogoConfiguration options for the Office Deployment Tool - Microsoft 365 AppsMicrosoftLearn
Will show which Channels and naming to use in .xml

"MatchOS" is available, but personally prefer the Total Control method, which will also resolve issues if your current environment is not standardized.

Now lets open a cmd window and change directory to where our setup.exe and .xml files reside.

C:\Users\Nailk_1>cd c:\o365

c:\O365>

Launch the setup.exe with the switch /download pointing to the .xml for instructions on what to download

c:\O365>setup.exe /download AllLang.xml

Once the download has started a folder will be create in the root of the folder where setup.exe resides. This will be all of the files needed for installation.

Now its time to set-up our individual language .xml for the install.

<Configuration>
  <Add OfficeClientEdition="64" Channel="MonthlyEnterprise" OfficeMgmtCOM="TRUE" ForceUpgrade="TRUE">
    <Product ID="O365ProPlusRetail">
      <Language ID="en-us" />
    </Product>
    <Product ID="AccessRuntimeRetail">
      <Language ID="en-us" />
    </Product>
  </Add>
  <Property Name="SharedComputerLicensing" Value="0" />
  <Property Name="SCLCacheOverride" Value="0" />
  <Property Name="AUTOACTIVATE" Value="FALSE" />
  <AppSettings>
    <Setup Name="Company" Value="DEVLAB" />
    <User Key="software\microsoft\office\16.0\common\toolbars" Name="fontview" Value="1" Type="REG_DWORD" App="office16" Id="L_Listfontnamesintheirfont" />
    <User Key="software\microsoft\office\16.0\common\toolbars" Name="animation" Value="0" Type="REG_DWORD" App="office16" Id="L_Menuanimations" />
    <User Key="software\microsoft\office\16.0\common\internet" Name="donotuselongfilenames" Value="0" Type="REG_DWORD" App="office16" Id="L_Uselongfilenameswheneverpossible" />
    <User Key="software\microsoft\office\16.0\common\general" Name="shownfirstrunoptin" Value="1" Type="REG_DWORD" App="office16" Id="L_DisableOptinWizard" />
    <User Key="software\microsoft\office\16.0\common" Name="qmenable" Value="0" Type="REG_DWORD" App="office16" Id="L_EnableCustomerExperienceImprovementProgram" />
  </AppSettings>
  <Display Level="Full" AcceptEULA="TRUE" />
  <Logging Level="Standard" Path="%temp%" />
</Configuration>

If you select auto activate during a non-shared install - First person logging into device will be the primary user and this will count towards their 5 devices. So if your IT Techs are logging in to do some manual configurations I would recommend to set "AUTOACTIVATE" Value="FALSE"

I wont go into breaking down all variables here, but instead you can reference the Configuration options for the Office Deployment Tool linked above.

PreviousOffice 365 Multi-LangNextDeploy - O365 Multi-Lang

Last updated

Was this helpful?