File deployment tool

You can start by copying and pasting the example below into a text file and saving it with a name of your choosing. Use the file to modify the XML elements and attributes and use the rest of this article to learn more details about each of the elements and attributes. This configuration file includes the most-commonly used elements and attributes, and can be used to download and install Office on a client computer.

The Logging element is no longer supported as a configuration option for the Office Deployment Tool. Defines the location of the Office installation files. If the ODT is run in download mode, defines where to save the files.

If not included and the ODT is run in download mode, the Office installation files are downloaded to the same folder as the tool. When you download Office to a folder that already contains that version of Office, the ODT will conserve your network bandwidth by downloading only the missing files.

For example, if you use the ODT to download Office in English and German to a folder that already contains Office in English, only the German language pack will be downloaded. When you use the Version attribute, we recommend including the Channel attribute as well.

If you don't include the Channel attribute, the default channel will be used, which might not match the specified version.

This setting can make it easier to add language packs or Visio and Project without updating Office to a newer version. Defines whether the bit or bit edition of Microsoft Apps is downloaded or installed.

If Office is installed and OfficeClientEdition is specified, then it must match the already installed architecture. If it doesn't, the installation will fail, since mixed architectures are not supported.

Defines which channel to use for installing Office. If Office is not installed on the device, the default setting for the Channel attribute is Current. If Office is installed on the device and the channel attribute is not specified, the ODT will match the channel of the existing installation. This value determines the channel to be installed, regardless of an optionally specified update channel in the Updates element or via Group Policy Setting.

If there is such setting with a different update channel, the channel switch is performed after the installation during the next update cycle.

For more information, see Change the Microsoft Apps update channel. For more information about update channels, see Overview of update channels for Microsoft Apps. If you're deploying Office Professional Plus or Office Standard , which are volume licensed versions of Office, there is a different update channel you need to use: PerpetualVL For more information, see Update channel for Office Defines where the installation files are downloaded from when running ODT in download mode.

Most commonly used to distribute specific languages and products for Office from a central location on your network to another location. Note that you must specify a version when using DownloadPath, as shown in the example. To use the Office CDN as a backup source for language packs, include the "AllowCdnFallback" attribute in the configuration file, as shown in the example. When installing languages, the ODT looks first for source files in the location specified in the SourcePath attribute.

If set to TRUE, then your existing installation of Microsoft Apps will be changed to the architecture sometimes referred to as the bitness that is specified in the OfficeClientEdition attribute. For example, you can use this to change a bit installation of Microsoft Apps to a bit installation. For more information about using MigrateArch, see Change a Microsoft Apps installation from bit to bit. Defines which products to download or install. If you define multiple products, the products are installed in the order in the configuration file.

You can also use the Product element to add language packs to existing installations of Microsoft Apps. Step 2: Run Office Deployment Tool file that downloaded. After the installation is complete, find the folder containing this toolkit. As below:. In this folder you will easily see the following files:. However, in this article I will guide you to download and install the Office Standard version.

Therefore, we must have standard XML configuration file to do it. Step 3: Create a configuration file. XML for Office Standard with the instructions as below:. Yes, install Microsoft Download Manager recommended No, thanks. What happens if I don't install a download manager? Why should I install the Microsoft Download Manager? In this case, you will have to download the files individually.

You would have the opportunity to download individual files on the "Thank you for downloading" page after completing your download. Files larger than 1 GB may take much longer to download and might not download correctly. You might not be able to pause the active downloads or resume downloads that have failed.

Details Note: There are multiple files available for this download. Once you click on the "Download" button, you will be prompted to select the files you need. File Name:. To change where your client computers receive their updates, run the ODT in configure mode and specify an update path in the configuration file.

This article does not cover all the issues related to managing updates for Office in your organization. For more information on that scenario, including using Group Policy, see Choose how to manage updates to Microsoft Apps. When installing Microsoft Apps, you can exclude specific applications. To do so, follow the steps for installing Office with the ODT, but include the ExcludeApp element in your configuration file.

For example, this configuration file installs all the Microsoft Apps for enterprise applications except Publisher:. If you've already installed Microsoft Apps, you can also use the ExcludeApp element to remove an application that you've previously installed. For example, the configuration file above removes Publisher from the previous installation of Office.

You can also remove an entire language version of Microsoft Apps. To do so, follow the steps for excluding products for installing Office with the ODT, but replace the configuration file with one that uses the Remove element. For example, this configuration file removes the Spanish language version of Microsoft Apps for enterprise:. For more information about the options for excluding or removing apps, see Configuration options for the Office Deployment Tool. If you don't want OneDrive installed with those applications, use the ExcludeApp element to remove it, as shown in the example.

For details on deploying languages, see Overview of deploying languages for Microsoft Apps. As part of your deployment, you can define application preferences for Microsoft Apps, including VBA Macro notifications, default file locations, and default file formats. To do so, you deploy Office using the standard steps in Install Microsoft Apps , but you include application preferences as part of your configuration file.

To create the configuration file, we recommend you use the Office Customization Tool for Click-to-Run , a web application with a full user interface.

In this example, the configuration file installs the bit version of Microsoft Apps for enterprise in English and displays the Trust Bar for all VBA macros in Excel. For more information on the app preferences, we recommend browsing the options in the tool itself. Note: When Office is installed, the app preferences defined in the configuration file are applied to all existing users of the device and any new users added to the device in the future.

You can apply new application preferences to client computers that already have Microsoft Apps installed without changing any other deployment setting. To do so, create a configuration file that contains application preferences and then run the ODT in customize mode.

Customize mode ignores all other settings in the configuration file except application preferences.