fibercas.blogg.se

It can also create an Office App-V package, but that is not covered here. The XML files are used to define how “setup.exe” downloads an Office installation source, or how it configures an Office installation. Setup.exe /configure "\\FileServer\FileShare\2016\ProPlus\install.xml"Ĭonfiguration.xml is an example XML file. Setup.exe /download "\\FileServer\FileShare\2016\ProPlus\download.xml" Setup.exe /configure "C:\O365-Install\2016\ProPlus\install.xml" Here are some examples: setup.exe /download "C:\O365-Install\2016\ProPlus\download.xml" Setup.exe also requires a path to an XML file in the command. packager Produces an Office App-V package from an Office installation source configure Adds, removes, or configures an Office installation download Downloads files to create an Office installation source

Setup.exe is a standalone executable that requires one of 4 switches to operate. The file that you download is just an archive that contains two files: You can download them from the Microsoft Download Center by using the following links: Each one works only with that specific version of Office. There are two different versions of the Office Deployment Tool available – one for Office 2013 and a different one for Office 2016. 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. The Office 365 Deployment Tool (ODT) is used to download Office products and language files to your local network. According to Microsoft, the old update channel names are still supported in the latest version of the deployment tool. This post was updated 1 to reflect the new Update Channel names. Most of the information here leans towards an Office 2016 Professional Plus deployment.

The following notes are for deploying the Office 365 Click-to-Run (C2R) suite of applications in an enterprise environment.