, 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. 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 Tool The Office 365 Deployment Tool (ODT) is used to download Office products and language files to your local network.
Added a missing /norestart parameter to the.NET Framework 4 Full (64-bit) – silent uninstall command line. Added information about.NET Framework 4.5 and 4.5.1 install, repair and uninstall. Added a link to the.NET Framework Repair Tool. Office 2010 Completely Silent Install – A really quick rundown I’ll assume most of the people here are techs and just looking for a quick and easy no hassles ‘get me going’ solution. I’ll do my best to deliver.
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.xml Setup.exe Setup.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 information Setup.exe also requires a path to an XML file in the command. Here are some examples: setup.exe /download 'C: O365-Install 2016 ProPlus download.xml' setup.exe /configure 'C: O365-Install 2016 ProPlus install.xml' setup.exe /download ' FileServer FileShare 2016 ProPlus download.xml' setup.exe /configure ' FileServer FileShare 2016 ProPlus install.xml' Configuration.xml Configuration.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 ProPlus When downloading the Office C2R source bits, the XML defines the following: Source Path The 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 Edition The bit architecture to download: 32-bit or 64-bit.
Update Channel The Office 2016 to download from (Insiders, Monthly, Targeted or Broad). Product ID The Office product suite to download. You cannot download individual Office suite applications. Languages One or more languages to include in the download.
Example XML for downloading Office 2016 Pro Plus, 32-bit, English-US:
For the local and UNC paths, the path must contain a trailing “ ” at the end of the path, and none of the paths should include the Office folder. Office Client Edition The bit architecture being installed: 32-bit or 64-bit. Product ID The Office product suite to install. You can also define exclusions for individual Office applications. Languages One or more languages to include. The first language listed will become the primary language. Display Level & EULA The display level during installation (None or Full), and if the EULA is accepted (True or False).
Logging The logging level (Off or Standard), and the file path for the log file (local path or UNC). Updates Define 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. Whenever possible, all of the update parameters should be controlled using group policy, which is done at the machine level.
Example XML for installing Office 2016 Pro Plus, 32-bit, English-US:
![]()
Include all required language IDs when downloading the Office bits, and then use this download as a single source for installing one or more of those languages to the user base. Each additional language adds approximately 150-200 MB to the size of the Office bits. MatchOS tells the installer to install the same language as the client’s operating system. When installing, the first language listed becomes the primary language, and determines the Shell UI language. The Shell UI is the language that is used to display shortcuts, right-click context menus, and tooltips.
If the user changes languages in the app, the right-click menus remain with the primary language. If you decide that you want to change the Shell UI language after an initial installation, you have to uninstall Office, and then reinstall it. You cannot use the.msi installers to add language packs to Office 2016 click to run installations. A list of language IDs can be found here: Example XML for downloading multiple languages in Office 2016
To turn on shared computer licensing, include the following XML element: Example XML for installing Office 2016 Pro Plus on a terminal server:
Use a combination of the XML ExcludeApp elements to add/remove Office Applications. Use a combination of the XML Language IDs to add/remove language packs. If you are changing the primary language (the first language ID listed), you have to uninstall Office before installing with a new primary language. Use the Force App Shutdown XML element to make sure all Office apps are closed before re-configuring.
Repairing an Office Installation If an Office application isn’t working properly, sometimes restarting it will fix the problem. If that doesn’t work, you can try repairing it.
When the repair is done, the computer may need to be restarted. Performing a full online repair of Office will install any excluded applications. The quick repair does not install excluded Office applications. Repair Using Programs & Features Control Panel Programs Programs and Features. Click the Office product you want to repair, and then click Change.
For a Quick Repair: Quick Repair Repair. For a Full Online Repair: Online Repair Repair Repair from the Command Line Office Click-to-Run from Office 365 allows you to automate either a quick repair or an online full repair. OfficeClicktoRun.exe is the executable that will allow you to automate a repair in Office 2016.
Important:. If your organization installed Office on your computer, contact your IT department to install any language packs. If you're an administrator who has deployed a volume licensed version of Office 2016 to your users, you can from the Volume Licensing Service Center (VLSC). If you're an administrator who has deployed a volume licensed version of Office 2019 to your users, you can. Step 1: Install the language accessory pack The language accessory pack files are available for free download for either the 32-bit (x86) or 64-bit (x64) architectures of Office. Select the version of Office you're using from the tabs below, then select the language desired from the drop-down list.
Finally choose the appropriate architecture (32-bit or 64-bit) from the download links provided. If you're not sure what you're using see Once the file is downloaded, double-click it to install it.
Comments are closed.
|
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |