Office Deployment Tool: Step-by-Step Guide to Deploy Microsoft 365 Apps

The office deployment tool lets you download and deploy Click‑to‑Run versions of Office, such as Microsoft 365 Apps for enterprise, to your client computers.

Key Takeaways

• ODT is a command‑line utility for bulk Office installations.
• It works on Windows 10, Windows 11, and recent Windows Server releases.
• Configuration is driven by an XML file you create or edit.
• Common mistakes include mismatched language codes and forgetting to run the tool as administrator.
• After deployment, you can verify the install with the Office Deployment Tool log.

What Is the Office Deployment Tool?

The office deployment tool is a command‑line tool that you can use to download and deploy Click‑to‑Run versions of Office, such as Microsoft 365 Apps for enterprise, to your client computers. It is designed for administrators who need to manage installation sources, product and language combinations, or deployment configuration options.

Which Windows Versions Are Supported?

According to Microsoft, the tool runs on Windows 10, Windows 11, Windows Server 2016, Windows Server 2019, Windows Server 2022, and Windows Server 2025. If your environment includes any of these, you can use ODT without additional compatibility layers.

How to Download the Office Deployment Tool

1. Visit the official Microsoft Download Center page for the office deployment tool.

1. Click the Download button; the file is named officedeploymenttool.exe.
2. Save the executable to a folder where you have write permissions, for example C:\ODT.
3. Run the executable to extract setup.exe and configuration.xml files.

Because the download page is maintained by Microsoft, you’ll always get the latest version. Check the page regularly for updates.

Preparing the Configuration XML

The heart of ODT is the configuration XML file. It tells the tool which Office product to download, which language packs to include, and where to place the installation files.

1. Choose the product ID. For Microsoft 365 Apps for enterprise, use O365ProPlusRetail. For Office 2019, use Office2019Retail.
2. Set the language. Language codes follow the ISO 639‑1 format, e.g., en-us for U.S. English or fr-fr for French.
3. Define the download source. You can let ODT pull files directly from Microsoft’s CDN, or specify a shared network folder for offline installs.
4. Optional: Add exclusions. Use the ExcludeApp element to skip apps you don’t need, such as Access or Publisher.

Below is a minimal example that downloads the English version of Microsoft 365 Apps and stores it in C:\ODT\Source:

<Configuration>
 <Add OfficeClientEdition="64" Channel="Monthly">
 <Product ID="O365ProPlusRetail">
 <Language ID="en-us" />
 </Product>
 </Add>
 <Updates Enabled="TRUE" />
 <Display Level="None" AcceptEULA="TRUE" />
 <Property Name="SharedComputerLicensing" Value="TRUE" />
 <SourcePath>C:\ODT\Source</SourcePath>
</Configuration>

Running the Tool to Download Office Files

Open a Command Prompt with administrator rights and navigate to the folder where you extracted ODT. Then execute:

setup.exe /download configuration.xml

The tool reads the XML, contacts Microsoft’s servers, and downloads the required files to the SourcePath you defined. A log file named setup.log appears in the same folder, showing success or any errors.

Deploying Office to Client Machines

Once the source files are ready, you can push them to multiple computers using one of three methods:

• Group Policy. Create a startup script that runs setup.exe /configure configuration.xml on each machine.
• System Center Configuration Manager (SCCM). Import the ODT package and schedule a deployment.
• Manual copy. For small environments, copy the source folder to a USB drive and run the same command locally.

Make sure the command runs with elevated privileges; otherwise the installation will fail silently.

Common Mistakes and How to Avoid Them

Mismatched language codes. If the language ID in the XML doesn’t match an available pack, ODT aborts. Double‑check the code against Microsoft’s language list.

Running without admin rights. The tool needs to write to Program Files and the registry. Always launch the command prompt as administrator.

Forgetting to accept the EULA. The AcceptEULA="TRUE" attribute must be present; otherwise the install stops at the license prompt.

Using an outdated ODT version. Microsoft releases updates to support new Office channels. Periodically revisit the download page.

Verifying a Successful Deployment

After the install finishes, you can verify it in three ways:

1. Check the setup.log for a SUCCESS entry.
2. Open any Office app; the About dialog should display the correct version and channel (e.g., Monthly Enterprise).
3. Run cscript "C:\Program Files\Microsoft Office\Office16\OSPP.VBS" /dstatus to see activation status.

If any step reports an error, consult the log file first; it often points to a missing language pack or insufficient permissions.

When to Use the Office Deployment Tool vs. Microsoft Store

For a handful of machines, the Microsoft Store offers a quick, click‑to‑install experience. ODT shines when you need:

• Consistent configuration across dozens or hundreds of devices.
• Offline installations in bandwidth‑constrained environments.
• Custom language and app selections that the Store doesn’t expose.

If your organization fits any of these scenarios, ODT is the better choice.

Integrating ODT with Other Business Tools

NovaBizTech’s AI‑assisted workflow automator can generate the configuration XML based on a simple questionnaire. By linking the AI tools to automate business tasks guide, you can streamline the XML creation process and reduce manual errors.

What to Do Next

1. Download the latest office deployment tool from Microsoft’s official page.

1. Draft a configuration XML that matches your product, language, and source requirements.
2. Test the download and install on a single workstation before scaling.

Troubleshooting Specific Deployment Failures

When the Office Deployment Tool fails, the error codes in the setup log are your best friend. The log file, usually found in %temp%, contains the exact step where the process broke. If you see error 0x80070005, it is an access denied issue.

This typically happens if the user running the command prompt does not have administrative rights. Run the terminal as an administrator and try again. Do not ignore this; running as a standard user will always fail for system-wide installs.

Handling Network and Proxy Issues

Corporate environments often use proxies with SSL inspection. The ODT downloads large files from Microsoft’s CDN. If the proxy blocks these connections or modifies the SSL handshake, the download stalls. Check your network team’s allowlist for Microsoft’s CDN domains.

If you cannot change the proxy settings, use the /download switch on a machine that has direct internet access, copy the local cache folder to a secure share, and deploy from there. This bypasses the need for each client to connect to the internet during the install phase.

Managing Updates and Upgrades with ODT

Deploying Office is only half the job. Keeping it updated is the other. The ODT does not automatically update Office unless you configure it to. By default, Office installed via ODT uses the Current Channel. You can change this in the configuration XML by setting the Channel attribute.

If you need a stable environment for legacy applications, use the Monthly Enterprise Channel. It updates once a month and includes only security and critical fixes, skipping new features. This reduces breakage but means you wait longer for bug fixes.

Upgrading From Older Office Versions

You cannot upgrade Office 2016 or 2019 directly to Microsoft 365 Apps using the ODT without first uninstalling the old version. The setup engine detects the older product key and refuses to proceed. Uninstall the old version via Control Panel or PowerShell. Reboot the machine. Then run the ODT deployment script.

If you skip the reboot, the installer may hang or throw a file-in-use error. In large fleets, script the uninstall and reboot as a separate task before triggering the ODT deploy.

Customizing the Installation for Specific Roles

Not every user needs the full suite. A sales team might only need Excel and Outlook. A developer might need Visual Studio but not Access. The ODT lets you exclude specific applications in the configuration XML. Use the ExcludeApp element to remove unneeded components. This reduces the download size and installation time.

It also prevents users from accidentally opening apps they are not licensed for. However, be careful. Excluding an app that a shared add-in depends on can break that add-in. Test your configuration on a few pilot machines before rolling it out to the whole organization.

Setting Default File Locations and Templates

You can pre-configure where Office saves files by default. In the XML, you can set the DisplayLanguage and UpdateChannel, but for file paths, you usually rely on Group Policy. The ODT handles the application binaries, not the user preferences.

To set default save locations, create a Group Policy Object (GPO) that points to a network share or OneDrive for Business. Apply this GPO to the user group. This ensures compliance with your data retention policies.

Do not try to hard-code file paths in the ODT XML; it will not work as intended and will likely be overwritten by user settings.

How to Create a Silent Install for Large Enterprises

When you need to roll out Office to hundreds of machines without user interaction, a silent install is the way to go. The key is to add the /quiet switch to the ODT command line and ensure the configuration XML disables UI prompts.

Step‑by‑step silent install

• Open an elevated Command Prompt on the server that will host the source files.
• Run setup.exe /download configuration.xml to pull the latest Office bits.
• After the download finishes, execute setup.exe /configure configuration.xml /quiet. The /quiet flag tells ODT to run without displaying any dialogs.
• Verify the OfficeC2RClient.exe log in %temp% for any errors.

Because the install runs silently, you won’t see progress bars. Use the log file to confirm success, especially on machines with limited admin rights.

Using a Shared Network Share vs. Local Cache

ODT lets you store the Office source either on a shared network folder or on each client’s local cache. Each approach has trade‑offs you should weigh before deciding.

Network share advantages

• One central location means you only download the Office files once.
• Easy to apply patches: replace the files on the share and all future installs pick up the update.

Network share drawbacks

• Every client must have reliable connectivity during install; a dropped connection aborts the deployment.
• High concurrent traffic can saturate bandwidth on busy mornings.

Local cache advantages

• After the first download, each machine installs from its own disk, eliminating network spikes.
• Works offline, which is handy for laptops that travel.

Local cache drawbacks

• Initial download repeats on every device, increasing total bandwidth usage.
• Managing updates requires a script to re‑download the latest bits on each client.

Decision rule: if your environment has a stable LAN and you control install windows, a shared share usually saves time. If you support remote or mobile users, prefer the local cache method.

Practical Tip: Deploying Different Office Suites to Separate Departments

Many organizations need Outlook for sales, but only Word and Excel for finance. ODT lets you tailor the Product element in the XML for each group.

Sample XML fragment for a sales team

<Add OfficeClientEdition="64" Channel="MonthlyEnterprise">
 <Product ID="O365ProPlusRetail">
 <Language ID="en-us" />
 <ExcludeApp ID="OneNote" />
 </Product>
</Add>

Remove the <ExcludeApp> lines for finance, or replace the Product ID with the lightweight O365BusinessRetail SKU. Deploy each XML to the appropriate OU in Active Directory, then run the same ODT command targeting that XML. This keeps the install size small and reduces unnecessary updates.

Frequently Asked Questions

Can I use the Office Deployment Tool for Office 2016?

Yes. ODT supports Office 2016 Click‑to‑Run deployments, allowing you to control source paths and language packs just like newer versions.

Do I need a Microsoft 365 subscription to use ODT?

You need a valid license for the product you’re deploying. ODT itself is free, but the Office suite requires appropriate licensing.

Is it possible to uninstall Office with ODT?

ODT includes an /uninstall switch that removes the product defined in your configuration file. Use it with the same XML you used for installation.

Further reading

• Download Office Deployment Tool from Official Microsoft Download Center
• Office Deployment Tool | Microsoft Support
• Office Customization Tool – Microsoft 365 Apps admin center