Office Deployment Tool for Office 2024: Full Setup Guide

Deploying Office LTSC 2024 requires more than running a standard installer. Microsoft recommends using the Office Deployment Tool (ODT) to configure, download, and install Office across devices. ODT provides IT administrators with control over version, language, architecture, update source, product ID, activation method, and included apps. Microsoft’s deployment guidance confirms that Office LTSC 2024, including Project and Visio, should be configured and deployed using ODT.

This guide explains how to use the Office Deployment Tool for Office 2024, how to create a configuration.xml file, how to download Office LTSC 2024 installation files, and how to install Office safely.

Quick Answer: How Do You Deploy Office 2024 with the Office Deployment Tool?

To deploy Office LTSC 2024 with the Office Deployment Tool:

1. Download the latest Office Deployment Tool from Microsoft.
2. Extract the files to a local folder.
3. Create or edit a configuration.xml file.
4. Use setup /download configuration.xml to download Office 2024 installation files, if needed.
5. Use setup /configure configuration.xml to install Office 2024.
6. Activate Office using the correct volume license method, such as MAK or KMS.

Microsoft lists these same core steps for Office LTSC 2024 deployment: download ODT, create the XML file, optionally download installation files, and install Office with ODT.

What is the Office Deployment Tool?

The Office Deployment Tool is Microsoft’s command-line tool for downloading and installing Office products that use Click-to-Run installation technology. For Office LTSC 2024, it is the main deployment method for organizations that need to install Office on one or more devices.

When you extract the Office Deployment Tool, you get two key files:

File	What it does
setup.exe	The command-line tool used to download or install Office
configuration.xml	The XML file that tells ODT what to install and how to install it

Microsoft explains that setup.exe is the ODT command-line tool, while configuration.xml specifies the settings for downloading or installing Office.

ODT functions as the engine, while configuration.xml directs its actions by specifying what to install, configure, or exclude.

Who Should Use the Office Deployment Tool for Office 2024?

The Office Deployment Tool is best for:

• IT administrators deploying Office LTSC 2024 across multiple PCs
• Businesses using volume-licensed Office products
• Users who need offline or local-network installation files
• Organizations that want to control installed apps and languages
• Businesses deploying Project 2024 or Visio 2024 alongside Office
• Environments with limited internet bandwidth
• Admins who want repeatable Office installation settings

Office LTSC 2024 is designed for organizations in regulated or restricted environments that cannot take regular feature updates. It is available through volume licensing and is separate from Microsoft 365 Apps, which continues receiving feature updates.

Office LTSC 2024 vs Microsoft 365 Apps: What’s the Difference?

Before deploying Office 2024, it is important to understand the capabilities and limitations of Office LTSC 2024.

Office LTSC 2024 is a perpetual, volume-licensed edition of Microsoft Office. It is intended for organizations that need a fixed feature set and cannot rely on ongoing cloud-delivered feature updates. Microsoft states that Office LTSC 2024 does not receive feature updates after launch, unlike Microsoft 365 Apps.

Feature	Office LTSC 2024	Microsoft 365 Apps
Licence type	Perpetual volume license	Subscription
Feature updates	No feature updates after launch	Receives ongoing feature updates
Best for	Restricted or regulated environments	Most modern business users
Deployment tool	Office Deployment Tool	Office Deployment Tool / Microsoft admin tools
Internet dependency	Lower after deployment	Higher for cloud-connected services

For many businesses, Microsoft 365 Apps may be more suitable. However, for organizations that need a fixed Office version, Office LTSC 2024 is the better fit.

Office LTSC 2024 System Requirements

Before deployment, check that your devices meet the minimum requirements.

Microsoft states that Office LTSC 2024 is supported on Windows 11, Windows 11 LTSC 2024, Windows 10 LTSC 2021, Windows 10 LTSC 2019, Windows Server 2025, and Windows Server 2022. For ARM-based devices, Windows 11 is the minimum supported version.

Requirement	Minimum
Processor	1.1 GHz, two-core processor
RAM	4 GB
Disk space	4 GB available space
Display	1280 x 768 resolution
Operating system	Supported Windows version
Architecture	32-bit or 64-bit, depending on deployment needs

Microsoft also notes that 64-bit Office is required for 4K and higher resolutions.

Products You Can Deploy with Office Deployment Tool 2024

The Office Deployment Tool can deploy several Office LTSC 2024 products.

Common Office 2024 Product IDs include:

Product	Product ID
Office LTSC Professional Plus 2024	ProPlus2024Volume
Office LTSC Standard 2024	Standard2024Volume
Project Professional 2024	ProjectPro2024Volume
Project Standard 2024	ProjectStd2024Volume
Visio LTSC Professional 2024	VisioPro2024Volume
Visio LTSC Standard 2024	VisioStd2024Volume

Microsoft lists these Product IDs as valid values for Office LTSC 2024 deployment with ODT.

Before You Start: What You Need

Before setting up Office 2024 with the Office Deployment Tool, prepare the following:

• A supported Windows device
• Administrator access
• The latest Office Deployment Tool
• A valid Office LTSC 2024 product key
• A MAK or KMS activation method, depending on your setup
• Internet access, unless using a local network source
• A text editor such as Notepad
• Optional: Office Customization Tool for creating XML files

Microsoft recommends downloading and using the latest version of ODT from the Microsoft Download Center.

Step 1: Download the Office Deployment Tool

First, download Office Deployment Tool from Microsoft.

After downloading it:

1. Run the Office Deployment Tool executable.
2. Accept the license terms.
3. Choose a folder where the files should be extracted.
4. Confirm that setup.exe and sample XML files are available.

Microsoft states that after extracting ODT, the folder includes setup.exe and a sample configuration.xml file.

Suggested folder path:

C:\ODT

Using a simple folder path streamlines command-line operations and reduces the risk of errors.

Step 2: Create the Configuration XML File

The configuration.xml file tells ODT what to download or install.

It can define:

• Office product
• Language
• 32-bit or 64-bit architecture
• Update channel
• Source path
• Apps to exclude
• Display level
• Product key method
• Whether to remove older MSI Office versions

Microsoft says you can create multiple XML files for different deployments, such as one for 64-bit Office LTSC Professional Plus 2024 in English and another for 32-bit Visio LTSC Professional 2024 in French.

You can create the XML manually in Notepad, or use Microsoft’s Office Customization Tool, which provides a web-based interface for building the configuration file. Microsoft recommends using the Office Customization Tool to simplify XML creation.

Sample Configuration XML for Office LTSC 2024 Professional Plus

Here is a basic XML file for installing Office LTSC Professional Plus 2024 (64-bit) in English.

<Configuration>
  <Add OfficeClientEdition="64" Channel="PerpetualVL2024">
    <Product ID="ProPlus2024Volume">
      <Language ID="en-us" />
    </Product>
  </Add>
  <RemoveMSI />
  <Display Level="None" AcceptEULA="TRUE" />
</Configuration>

What this XML does

XML setting	Meaning
OfficeClientEdition="64"	Installs 64-bit Office
Channel="PerpetualVL2024"	Uses the Office LTSC 2024 update channel
Product ID="ProPlus2024Volume"	Installs Office LTSC Professional Plus 2024
Language ID="en-us"	Installs English language files
<RemoveMSI />	Removes older MSI-based Office versions
Display Level="None"	Runs installation silently
AcceptEULA="TRUE"	Accepts the license agreement during deployment

Microsoft’s own sample XML for Office LTSC 2024 uses Channel="PerpetualVL2024", ProPlus2024Volume, RemoveMSI, and Display Level="None" AcceptEULA="TRUE".

Step 3: Choose 32-bit or 64-bit Office 2024

For most modern PCs, 64-bit Office is recommended, especially for users who work with large Excel files, databases, or memory-intensive workloads.

However, some organizations still choose 32-bit Office for compatibility with older add-ins or legacy workflows.

Microsoft states that all Office products installed on a device must use the same architecture, and you cannot have both 32-bit and 64-bit Office products installed on the same device. Microsoft also recommends 64-bit Office on devices with 4 GB or more of memory, while still advising organizations to assess compatibility needs.

Choose 64-bit Office if...	Choose 32-bit Office if...
Users work with large files	You rely on old 32-bit add-ins
PCs have 4 GB+ RAM	You have legacy compatibility needs
You want modern performance	Internal systems require 32-bit Office
You use large Excel workbooks	Existing macros/add-ins are not 64-bit ready

Step 4: Download Office LTSC 2024 Installation Files

If you want to install Office directly from Microsoft’s Office CDN, you do not need to pre-download the files. Microsoft says installing directly from the Office CDN requires the least administrative effort and is recommended when internet connectivity and bandwidth allow it.

However, if you want to deploy Office from a local network share, you need to download the installation files first.

Open Command Prompt as administrator, go to your ODT folder, then run:

cd C:\ODT
setup /download configuration.xml

If your XML file has a different name, replace configuration.xml with your file name.

Microsoft explains that when you run setup /download configuration.xml, the download may appear quiet in the background, and the command prompt returns once the download completes.

Step 5: Install Office LTSC 2024 with ODT

Once your XML file is ready, install Office with this command:

cd C:\ODT
setup /configure configuration.xml

If you are deploying silently, the installation may not show much on screen. Once setup is complete, open Word, Excel, or another Office app to confirm installation.

Microsoft documents using configuration.xml to set up Office LTSC 2024 with the Office Deployment Tool.

Step 6: Activate Office LTSC 2024

Office LTSC 2024 uses volume activation methods, usually KMS or MAK.

Activation method	Best for
KMS	Larger organizations that activate Office through an internal Key Management Service
MAK	Smaller deployments or devices that activate directly with Microsoft using a Multiple Activation Key

Microsoft’s Office LTSC 2024 deployment guidance states that the PIDKEY value can be used for KMS with a Generic Volume License Key or for MAK with a MAK product key.

If you purchased Office 2024 through Brytesoft, make sure you use the product key and installation instructions provided with your order.

Installing Office 2024 from the Office CDN vs Local Network Share

You can deploy Office LTSC 2024 in two main ways.

Method	Best for	Pros	Cons
Office CDN	Devices with reliable internet	Easier setup, fewer local files to manage	Uses internet bandwidth on each device
Local network share	Larger deployments or restricted environments	Faster repeated installs, better bandwidth control	Requires file storage and update management

Microsoft notes that Office LTSC 2024 installation files are available on the Office CDN, and admins can either install directly from the CDN or download the files to a local network location such as a shared folder.

Example: Deploy Office 2024 from a Local Network Share

If your organization wants to download Office 2024 once and install it on multiple PCs, use a shared folder.

Example XML:

<Configuration>
  <Add OfficeClientEdition="64" Channel="PerpetualVL2024" SourcePath="\\Server\Share">
    <Product ID="ProPlus2024Volume">
      <Language ID="en-us" />
    </Product>
  </Add>
  <RemoveMSI />
  <Display Level="None" AcceptEULA="TRUE" />
</Configuration>

Then run:

setup /download configuration.xml

After the files are downloaded to the shared folder, run this on target devices:

setup /configure configuration.xml

Microsoft’s sample configuration for Office LTSC 2024 includes a SourcePath pointing to a shared folder, and Microsoft explains that SourcePath controls where Office installation files are downloaded to and installed.

How to Exclude Apps from Office 2024 Installation

By default, Office LTSC Professional Plus 2024 installs all included Office apps. If you do not want to install a specific app, use the ExcludeApp element.

Example: install Office 2024 but exclude Access.

<Configuration>
  <Add OfficeClientEdition="64" Channel="PerpetualVL2024">
    <Product ID="ProPlus2024Volume">
      <Language ID="en-us" />
      <ExcludeApp ID="Access" />
    </Product>
  </Add>
  <RemoveMSI />
  <Display Level="None" AcceptEULA="TRUE" />
</Configuration>

Microsoft states that ExcludeApp can be used to control which apps are installed, and gives Access as an example.

How to Deploy Office 2024 with Project and Visio

You can install Office LTSC 2024 together with Project 2024 or Visio 2024 by adding multiple product entries to the XML file.

Example:

<Configuration>
  <Add OfficeClientEdition="64" Channel="PerpetualVL2024">
    <Product ID="ProPlus2024Volume">
      <Language ID="en-us" />
    </Product>
    <Product ID="ProjectPro2024Volume">
      <Language ID="en-us" />
    </Product>
    <Product ID="VisioPro2024Volume">
      <Language ID="en-us" />
    </Product>
  </Add>
  <RemoveMSI />
  <Display Level="None" AcceptEULA="TRUE" />
</Configuration>

Microsoft lists Office LTSC Professional Plus 2024, Project LTSC 2024 Professional, and Visio LTSC 2024 Professional among the LTSC products available for Windows devices.

How to Deploy Office 2024 in Multiple Languages

To install multiple languages, add more Language entries under the product.

Example:

<Configuration>
  <Add OfficeClientEdition="64" Channel="PerpetualVL2024">
    <Product ID="ProPlus2024Volume">
      <Language ID="en-us" />
      <Language ID="fr-fr" />
      <Language ID="de-de" />
    </Product>
  </Add>
  <RemoveMSI />
  <Display Level="None" AcceptEULA="TRUE" />
</Configuration>

Microsoft says ODT and configuration.xml can be used to deploy Office LTSC 2024, including Project and Visio, in multiple languages.

Should You Use RemoveMSI?

In most upgrades from older Office versions, yes.

RemoveMSI removes older Office versions installed with Windows Installer. This helps prevent conflicts between older Office installations and Office LTSC 2024.

Microsoft recommends removing previous Office versions before installing Office LTSC 2024 and explains that RemoveMSI can remove older MSI-based Office, Visio, or Project versions.

However, Office 2019 uses Click-to-Run rather than MSI, so removing Office 2019 requires the Remove element instead of RemoveMSI. Microsoft specifically notes this distinction in its Office LTSC 2024 deployment guidance.

Common Office Deployment Tool Commands

Command	What it does
setup /download configuration.xml	Downloads Office files based on the XML settings
setup /configure configuration.xml	Installs Office based on the XML settings
setup /help	Shows ODT command options

For Office LTSC 2024, the two most important commands are /download and /configure.

Troubleshooting Office Deployment Tool 2024 Issues

1. setup.exe does nothing

If ODT seems to do nothing after running a command, do not panic. The Office files may be downloading quietly in the background. Microsoft notes that during setup /download, it might look as though nothing is happening, but the download is occurring in the background.

Check your target download folder for an Office folder containing a Data subfolder.

2. Office installs the wrong edition

Check your Product ID.

For Office LTSC Professional Plus 2024, use:

<Product ID="ProPlus2024Volume">

For Office LTSC Standard 2024, use:

<Product ID="Standard2024Volume">

3. Office installs in the wrong language

Check the language ID in your XML.

Example for English United States:

<Language ID="en-us" />

4. Office installation fails on a PC with an older version of Office installed

Use RemoveMSI if the older Office version uses Windows Installer technology. For Office 2019 or newer Click-to-Run versions, check whether you need the Remove element instead.

5. 32-bit and 64-bit Office conflict

You cannot install 32-bit and 64-bit Office products side by side on the same device. Microsoft states that all Office products on the device must use the same architecture.

6. Office does not activate

Check that:

• You installed the correct Office edition
• You used the correct product key or activation method
• Your product key matches Office LTSC 2024
• Your KMS host or MAK activation is configured correctly
• The device has network access if activation requires it

Best Practices for Office LTSC 2024 Deployment

To make deployment smoother:

• Always download the latest Office Deployment Tool.
• Test your XML file on one device before a wider rollout.
• Use the Office Customization Tool if you are not comfortable writing XML manually.
• Use 64-bit Office unless you have legacy compatibility requirements.
• Keep separate XML files for different user groups or languages.
• Use RemoveMSI when upgrading from older MSI-based Office versions.
• Confirm your activation method before deployment.
• Use a local network share if deploying to many devices with limited bandwidth.
• Document your XML files so future admins know what each one does.

Recommended Office 2024 Deployment Structure

For a clean deployment workflow, use this folder structure:

C:\ODT
│
├── setup.exe
├── configuration-office2024-proplus.xml
├── configuration-office2024-standard.xml
├── configuration-project2024.xml
├── configuration-visio2024.xml
└── Office
    └── Data

This structure keeps the tool, XML files, and downloaded Office files organized in a single deployment location.

Conclusion

The Office Deployment Tool is the safest and most flexible way to deploy Office LTSC 2024. With the right configuration.xml file, you can control exactly which Office product is installed, which language is used, whether Project or Visio is included, whether older MSI versions are removed, and whether installation files come from Microsoft’s CDN or your local network.

For most users, the basic process is simple:

setup /download configuration.xml
setup /configure configuration.xml

The configuration.xml file is central to deployment. Build it carefully, test before rollout, and retain a clean copy for future use.