How to Use the Office Deployment Tool for Custom Installs

How to Use the Office Deployment Tool for Custom Installs
The Office Deployment Tool (ODT) is a powerful command-line utility that allows IT professionals and advanced users to download and deploy customized versions of Office to client computers. This tool gives you full control over the installation, allowing you to choose which applications to install, select languages, and configure update settings. It is the preferred method for deploying Office in large organizations and for creating customized installation packages.

This guide will walk you through the basic steps of using the ODT to create a tailored Office installation.

Understanding the Office Deployment Tool
The ODT consists of two main files:

setup.exe: The executable file that runs the deployment process.

configuration.xml: A text file that contains all the settings for your installation, such as the Office version, which applications to install, and language options.

By editing the configuration.xml file, you can control exactly what gets installed.

Пошаговое руководство
Step 1: Download the Office Deployment Tool
Go to the official Microsoft Download Center and download the Office Deployment Tool.

Run the downloaded executable file and accept the license terms.

Choose a folder to extract the files to (e.g., C:ODT). This will provide you with setup.exe and a few sample XML configuration files.

Step 2: Create a Custom Configuration File
You will need to create a configuration.xml file that defines your installation settings. The easiest way to do this is with the web-based Office Customization Tool (OCT).

Go to the Office Customization Tool website: config.office.com.

Select the Office version you want to deploy (e.g., Office 2021, Microsoft 365 Apps) and the architecture (32-bit or 64-bit).

Customize your installation by selecting the apps you want to install (e.g., you can choose to exclude Publisher or Access).

Configure your desired languages, update channel, and other settings.

Once you have configured everything, click “Export” in the top-right corner.

Save the generated XML file (e.g., configuration.xml) to the same folder as your setup.exe file.

Step 3: Download the Installation Files
Before installing, you need to download the Office installation files from Microsoft’s Content Delivery Network (CDN) to your local folder.

Откройте командную строку от имени администратора.

Navigate to your ODT folder by typing cd C:ODT and pressing Enter.

Run the following command to download the files:
setup.exe /download configuration.xml

The download process will run silently in the background without a progress bar. You will know it’s complete when the Command Prompt returns to a blinking cursor.

Step 4: Install Office with Your Custom Configuration
Once the download is complete, you can run the final command to install Office.

In the same Command Prompt window, run the following command:
setup.exe /configure configuration.xml

The Office installation will begin and will only install the applications and settings you defined in your XML file.

The installation will run silently. You will know it’s complete when the Command Prompt returns to a blinking cursor.

Часто задаваемые вопросы
Q: Can I use this to install Office on a single PC?
A: Yes, you can. While it’s primarily used for large deployments, it’s a great way to have full control over your personal installation.

Q: Do I need to be an administrator to use the ODT?
A: Yes, you must have administrator privileges to run the Command Prompt and install the software.

Q: What is the difference between /download and /configure?
A: The /download command downloads all the necessary installation files. The /configure command uses those files to perform the actual installation on the PC.

Заключение
The Office Deployment Tool is an essential utility for anyone who needs precise control over their Office installation. By using a simple XML file, you can customize your deployment, save bandwidth, and ensure a consistent setup across multiple machines. While it requires some familiarity with the command line, the process is straightforward and well-documented by Microsoft.