Privacy Statement. Open ODT! See System Requirements. Available on PC. Description Open and edit your ODT files instantly with our. Show More. People also like. EasyRTF Free. Additional information Published by tomwong. Published by tomwong. Copyright Copyright Developed by tomwong.
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. For more information, including an example configuration file, see Deploy languages to existing installations of Microsoft Apps. Allows you to control the installation of an Office product, as specified by the ID attribute , based on whether a particular MSI-based Office product is already installed on the device.
The value that you specify for the MSICondition attribute can be either a volume licensed or a retail version of the product, as long as that version of the product was installed by using MSI. MSICondition will recognize , , , and versions of the Office product that you specify. But, you can't specify a particular version. WW folder of the installation files for your existing version of the Office product. For example, the Setup.
WW folder. You can specify multiple types of an Office product, separated by a comma. In the following example, Project Online Desktop Client will be installed on the device only if an MSI-based version of Project Standard is already installed on the device. Defines which languages to download or install. If you define multiple languages, the first language in the configuration file determines the Shell UI culture, including shortcuts, right-click context menus, and tooltips.
After you download Microsoft Apps installation files, follow these steps to install Office on a client computer. As part of that installation, you can choose which products to install. In this example, the configuration file installs a bit English edition of Microsoft Apps for enterprise without Publisher:.
The display level is set to None , which means the user will not see any user interface during the install. For more information about the configuration options, see Configuration options for the Office Deployment Tool. From a command prompt, run the ODT executable in configure mode with a reference to the configuration file you saved. In the following example, the configuration file is named installconfig. You must have local administrator permissions on the client computer.
You can run the executable from the client computer on which you want to install Office or you can put the ODT and the configuration file on a network share and run it from there. If you use a network share, make sure to pass the full network path for both the setup. After running the command, you should see the Office installation start unless you set display level to none. After installation is complete, the command prompt will display "Products configured successfully. 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.
0コメント