,The following notes are for deploying the Office 365 Click-to-Run (C2R) suite of applications in an enterprise environment. Most of the information here leans towards an Office 2016 Professional Plus deployment.Update This post was updated 14-Oct-2017 to reflect the new Update Channel names.
Im having some issues with deploying office 2016 language pack. Here is what i have done so far: i created Office 2016 MST file using setup.exe /admin (OCT not. Btw are you planning to switch to click to run in your org? Office 2010 Silent Uninstall. By lharris90. However, I've hit a problem as this won't remove the individual language packs (approx. 4) and the Office proofing tools. Does anyone have any experience in this area to point me in the right direction.or an alternative method for removal? I would like to try and include all installation.
Msi Silent Install
According to Microsoft, the old update channel names are still supported in the latest version of the deployment tool. Test before you deploy.Office 365 Deployment ToolThe Office 365 Deployment Tool (ODT) is used to download Office products and language files to your local network.
You can then deploy those Office products and languages to computers from a network share, or push the installation files to a machine with a management tool, and install locally.There are two different versions of the Office Deployment Tool available – one for Office 2013 and a different one for Office 2016. Each one works only with that specific version of Office. You can download them from the Microsoft Download Center by using the following links:.The file that you download is just an archive that contains two files:. Setup.exe. Configuration.xmlSetup.exeSetup.exe is a standalone executable that requires one of 4 switches to operate. /download Downloads files to create an Office installation source/configure Adds, removes, or configures an Office installation/packager Produces an Office App-V package from an Office installation source/help Displays the help informationSetup.exe also requires a path to an XML file in the command. Here are some examples: setup.exe /download 'C:O365-Install2016ProPlusdownload.xml'setup.exe /configure 'C:O365-Install2016ProPlusinstall.xml'setup.exe /download 'FileServerFileShare2016ProPlusdownload.xml'setup.exe /configure 'FileServerFileShare2016ProPlusinstall.xml'Configuration.xmlConfiguration.xml is an example XML file.
The XML files are used to define how “setup.exe” downloads an Office installation source, or how it configures an Office installation. It can also create an Office App-V package, but that is not covered here.Downloading Office 365 ProPlusWhen downloading the Office C2R source bits, the XML defines the following:Source PathThe path to where the Office folder is created by setup.exe. The Office C2R source bits will be downloaded into the Office folder. If no path is given, the Office folder is created in the same location as setup.exe.Office Client EditionThe bit architecture to download: 32-bit or 64-bit.Update ChannelThe Office 2016 to download from (Insiders, Monthly, Targeted or Broad).Product IDThe Office product suite to download.
You cannot download individual Office suite applications.LanguagesOne or more languages to include in the download.Example XML for downloading Office 2016 Pro Plus, 32-bit, English-US: 
You can also define exclusions for individual Office applications.LanguagesOne or more languages to include. The first language listed will become the primary language.Display Level & EULAThe display level during installation (None or Full), and if the EULA is accepted (True or False).LoggingThe logging level (Off or Standard), and the file path for the log file (local path or UNC).UpdatesDefine if updates are enabled and the update path. If the update path is not defined, the Office apps will download and install their updates from Microsoft’s CDN.
Additional update parameters include the update channel, target version, and deadline.