Office customization tools download

Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy. The Office Customization Tool creates the configuration files that are used to deploy Office in large organizations.

These configuration files give you more control over an Office installation: you can define which applications and languages are installed, how those applications should be updated, and application preferences. After creating the configuration files, you can use them with the Office Deployment Tool to deploy a customized version of Office.

The Office Customization Tool is part of the deployment process for installing Office on hundreds or thousands of computers.

To follow this process end-to-end, we recommend completing the assessment and planning phases for your Office deployment. If you're not an enterprise administrator and are looking to install Office in your home or business, see Install Office with Office To work with the service, go to Office Customization Tool and choose the products, languages, and application preferences you want to configure.

For example, you can create a configuration file that downloads the bit English version of Microsoft Apps, or you can create a file that installs the bit English and German version of Office without Access and Publisher and with the EULA automatically accepted.

When you're done, you export the configuration file, which you can then use with the Office Deployment Tool or another software distribution solution to deploy Office in your organization.

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. File Name:. Date Published:. File Size:. System Requirements Supported Operating System.

Office provides two architecture-specific versions of the OCT, one for bit Office and one for bit Office The bit version of the OCT supports bit client editions of Office , and provides the same user interface, capabilities, and configurable settings as the bit version.

The OCT files are located in the Admin folder under the x86 bit and x64 bit folders, respectively. Download the appropriate file depending on whether you have bit or bit Office installed.

For example, if you installed the bit edition of Office Professional Plus volume edition , you would copy the entire bit version of the Admin folder into the folder that contains the bit Office Professional Plus source files.

To install this download: Download the file by clicking the Download button above and saving the file to your hard disk. Follow the instructions on the screen to complete the installation. This is the recommended tool for anyone creating a configuration for deploying Office ProPlus or other Click-to-Run based products and is fully supported by Microsoft.

Then simply go through the different categories, selecting the required options. There are default options that can be configured accordingly, some are required for deployment, some aren't. After configuring each category and clicking next, a tick mark will appear to indicate it's been passed. On the right hand side, in the Configuration settings area, it shows a summary of the configuration as it's being built.