Download files with office deployment tool






















You can use the Office Deployment Tool to make updates to your client computers after installing Microsoft Apps. There are two ways to make the updates:. Only the files that have changed in the new version will be updated. Use the ODT to download the Office installation files and then point your client computers to that location to receive their updates. 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. You must run the executable from the client computer on which you want to apply the app preferences and you must have local administrator permissions on that computer.

When using customize mode, 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. If you apply application preferences when Office apps are running, the preferences will be applied when Office is next restarted. To do so, update the configuration file and then run the ODT in packager mode.

The setup. The configuration. You use the configuration. You can name the file anything that you want, as long as it retains the xml file extension.

Once you have a copy of the ODT, you need to create a configuration. You can create multiple configuration. For example, you would create a configuration. When you run the ODT from an elevated command prompt, you specify which configuration. Instead of using a text editor to create your configuration.

The OCT provides a web-based interface for making your selections and creating your configuration. For more information, see Overview of the Office Customization Tool. Please note that this is different than the Office Customization Tool that you might have used in the past to install volume licensed versions of Office that used Windows Installer MSI as the installation technology.

There are a series of settings in the configuration. The following table lists the most common settings to configure in the configuration. More information about these configuration. The following is a sample configuration. To uninstall versions of Office, Visio, or Project from the device, use the Remove element.

Once you have a copy of the ODT and have created your configuration. To do that, open an elevated command prompt, go to the folder where you saved the ODT and the configuration.

If you have saved the configuration. It will look as if nothing is happening, but the download is happening in the background. Once the download is complete, you are returned to a command prompt. If you want to check that the files are downloading, go to the location you specified for your SourcePath in the configuration. For example, Which files you see and the names of the files depend on whether you are downloading the bit or bit version of Office and which languages you are downloading.

The installation location can't be changed. The following is a sample configuration. We recommend that you uninstall any previous versions of Office before installing volume licensed versions of Office There are several ways that you can use the RemoveMSI element when installing volume licensed versions of Office Even though this article is about Microsoft Apps, most of the information also applies to volume licensed versions of Office Once you have a copy of the ODT and have created your configuration.

To do that, open an elevated command prompt, go to the folder where you saved the ODT and the configuration. If you have saved the configuration. It will look as if nothing is happening, but the download is happening in the background. Once the download is complete, you are returned to a command prompt. If you want to check that the files are downloading, go to the location you specified for your SourcePath in the configuration.

For example, Which files you see and the names of the files depend on whether you are downloading the bit or bit version of Office and which languages you are downloading.

You can also use Microsoft Endpoint Configuration Manager to deploy volume licensed versions of Office Configuration Manager current branch has a wizard that steps you through the process and builds the configuration. Earlier versions of Configuration Manager require you to download the ODT and create your own configuration. You must be using at least version , but version is recommended.

On that same page, you can also select to install Project and Visio. Then, in Configuration Manager, you create an application and a deployment type. After that you distribute the application and then deploy it. You can use the ODT and the configuration. For more details, see Language element. You can also just install proofing tools by specifying the Product ID as "ProofingTools" in your configuration.

Proofing tools packages, which are a new capability for Office , are much smaller than full language packs. They can also be installed whether or not the language pack for a given language is installed. If you're upgrading from a Windows Installer MSI version of Office, you can get Click-to-Run versions of the same language resources — for example, language packs, language interface packs, or proofing tools — installed when you deploy Office Skip to main content.

This browser is no longer supported. Download Microsoft Edge More info.



0コメント

  • 1000 / 1000