Office Deployment Tool XML Configuration Examples

The Office Deployment Tool XML configuration file directs the installer during an Office LTSC deployment.

It specifies the Office product, language, installation mode, source location, excluded apps, update settings, and inclusion of products such as Visio LTSC or Project LTSC.

When deploying Office LTSC 2024, Office LTSC 2021, Visio LTSC, or Project LTSC, the XML file is essential for configuring and executing the deployment.

This guide provides practical examples of Office Deployment Tool XML configuration for LTSC products, covering installation, download, silent deployment, offline installation, updates, uninstallation, and app exclusion.

What Is an Office Deployment Tool XML File?

An Office Deployment Tool (ODT) XML file defines deployment settings.

The Office Deployment Tool uses two key files:

setup.exe

configuration.xml

The setup.exe file initiates deployment, while the XML file defines what and how to install.

For example, this command installs Office based on the XML file:

setup.exe /configure configuration.xml

This command downloads the installation files first:

setup.exe /download configuration.xml

Microsoft’s LTSC deployment documentation confirms that Office LTSC 2024 and Office LTSC 2021 are deployed by downloading the Office Deployment Tool, creating a configuration XML file, optionally downloading installation files, and then installing Office with ODT.

Why XML Configuration Matters for Office LTSC

Office LTSC is commonly used in environments where organizations want a fixed, perpetual-license version of Office instead of Microsoft 365 Apps.

This makes the XML file critical, as LTSC deployments must be predictable, repeatable, and auditable.

A well-structured Office LTSC XML file enables you to:

• Install Office LTSC 2024 or Office LTSC 2021 silently
• Deploy Office from the Microsoft CDN or a local network share
• Install 32-bit or 64-bit Office
• Add Visio LTSC or Project LTSC
• Exclude apps such as Access, OneNote, Outlook, or Publisher
• Configure update behavior
• Remove older Office installations
• Standardize deployment across multiple devices

Microsoft states that Office LTSC 2024 continues to use the same deployment and update tools used for Office LTSC 2021 and Office 2019, including software distribution tools such as Microsoft Configuration Manager.

Basic Office Deployment Tool XML Structure

A basic Office LTSC XML file looks like this:

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

The most important XML elements are:

For Office LTSC volume products, Microsoft specifies special update channels: PerpetualVL2024 for Office LTSC 2024 and PerpetualVL2021 for Office LTSC 2021.

Office LTSC Product IDs for ODT XML

Before creating your XML file, choose the correct product ID.

Always match the product ID to your license type. Using a Microsoft 365 Apps product ID, such as O365ProPlusRetail, is not correct when your goal is to deploy Office LTSC volume-licensed products.

Office Deployment Tool XML Configuration Examples for LTSC

1. Install Office LTSC Professional Plus 2024

Use this XML to install Office LTSC Professional Plus 2024 in 64-bit English.

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

Run:

setup.exe /configure configuration.xml

Best for:
Standard Office LTSC 2024 Professional Plus deployments.

For the full Office 2024 setup process, see our Office Deployment Tool for Office 2024 guide.

2. Install Office LTSC Standard 2024

Use this XML if your organization has Office LTSC Standard 2024 instead of Professional Plus.

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

Best for:
Organizations licensed for Office LTSC Standard 2024.

3. Install Office LTSC Professional Plus 2021

Use this XML to install Office LTSC Professional Plus 2021.

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

Run:

setup.exe /configure configuration.xml

For a complete walkthrough, see our dedicated guide to the Office Deployment Tool for Office 2021.

4. Install Office LTSC Standard 2021

Use this XML for Office LTSC Standard 2021.

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

Best for:
Office LTSC 2021 Standard volume-license deployments.

5. Silent Install Office LTSC 2024

A silent Office LTSC install is useful for IT teams deploying Office through scripts, endpoint management tools, provisioning workflows, or remote software deployment platforms.

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

The key line is:

<Display Level="None" AcceptEULA="TRUE" />

This hides the installation interface and accepts the license terms.

Run:

setup.exe /configure configuration.xml

Best for:
Silent Office LTSC deployment across multiple business PCs.

6. Download Office LTSC 2024 Installation Files

If you want to download the Office LTSC 2024 installation files before installing, use the same XML and run the /download command.

<Configuration>
<Add OfficeClientEdition="64" Channel="PerpetualVL2024">
<Product ID="ProPlus2024Volume">
<Language ID="en-us" />
</Product>
</Add>
</Configuration>

Run:

setup.exe /download configuration.xml

Then install with:

setup.exe /configure configuration.xml

Microsoft lists downloading the installation files as an optional step when deploying Office LTSC 2024, especially when you are not installing directly from the Office CDN.

7. Install Office LTSC 2024 From a Local Network Share

For larger deployments, you may want to download Office once and install it from a local network path.

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

Run:

setup.exe /configure configuration.xml

Best for:
Enterprise deployments, offline staging, imaging workflows, branch offices, and bandwidth-controlled environments.

For the full Office 2024 setup process, see our Office Deployment Tool for Office 2024 guide.

8. Install Office LTSC 2021 From a Local Network Share

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

Best for:
Office LTSC 2021 deployments where installation files are stored on a local file server.

9. Install Office LTSC With Multiple Languages

Use multiple <Language> elements to install more than one language.

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

Best for:
Multilingual organizations, shared devices, global teams, or regional deployments.

10. Match Office LTSC Language to Windows

This XML installs Office using the same language as the operating system.

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

Best for:
Organizations using one XML file across devices with different Windows display languages.

11. Install 32-Bit Office LTSC 2024

Most modern deployments use 64-bit Office, but some organizations still need 32-bit Office to remain compatible with older add-ins or line-of-business applications.

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

Best for:
Legacy add-ins, older database integrations, and compatibility-sensitive environments.

12. Install Office LTSC 2024 With Visio LTSC 2024

Use this XML to install Office LTSC Professional Plus 2024 and Visio LTSC Professional 2024 together.

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

Best for:
Engineering teams, process mapping teams, operations teams, IT teams, and architecture departments.

13. Install Office LTSC 2024 With Project 2024

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

Best for:
Project managers, PMO teams, construction firms, consultants, implementation teams, and planning departments.

14. Install Visio LTSC 2024 Only

If Office is already installed and you only need to add Visio LTSC 2024, use this XML.

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

For Visio Standard 2024, use:

<Product ID="VisioStd2024Volume">

15. Install Project LTSC 2024 Only

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

For Project Standard 2024, use:

<Product ID="ProjectStd2024Volume">

16. Install Office LTSC 2021 With Visio LTSC 2021

<Configuration>
<Add OfficeClientEdition="64" Channel="PerpetualVL2021">
<Product ID="ProPlus2021Volume">
<Language ID="en-us" />
</Product>
<Product ID="VisioPro2021Volume">
<Language ID="en-us" />
</Product>
</Add>
<Display Level="None" AcceptEULA="TRUE" />
</Configuration>

17. Install Office LTSC 2021 With Project 2021

<Configuration>
<Add OfficeClientEdition="64" Channel="PerpetualVL2021">
<Product ID="ProPlus2021Volume">
<Language ID="en-us" />
</Product>
<Product ID="ProjectPro2021Volume">
<Language ID="en-us" />
</Product>
</Add>
<Display Level="None" AcceptEULA="TRUE" />
</Configuration>

18. Exclude Apps From Office LTSC

ODT lets you exclude specific Office apps during installation.

For example, this installs Office LTSC 2024 but excludes Access, Publisher, OneNote, and Outlook.

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

Common ExcludeApp values include:

<ExcludeApp ID="Access" />
<ExcludeApp ID="Excel" />
<ExcludeApp ID="OneNote" />
<ExcludeApp ID="Outlook" />
<ExcludeApp ID="PowerPoint" />
<ExcludeApp ID="Publisher" />
<ExcludeApp ID="Word" />

Best for:
Minimal installs, shared workstations, role-based deployments, or devices that only need selected Office apps.

19. Install Only Word, Excel, and PowerPoint

ODT does not use an “install only these apps” model. Instead, you install the Office product and exclude the apps you do not want.

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

This leaves the core apps such as Word, Excel, and PowerPoint installed, depending on the Office LTSC edition.

20. Remove Existing MSI-Based Office Before Installing LTSC

If you are replacing an older MSI-based Office version, use RemoveMSI.

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

Microsoft’s Office LTSC 2021 deployment guidance says existing Office versions should be removed before installing Office LTSC 2021.

Best for:
Migration from older Office versions to Office LTSC 2024 or Office LTSC 2021.

21. Remove Office LTSC 2024

Use the <Remove> element to uninstall Office LTSC 2024.

<Configuration>
<Remove>
<Product ID="ProPlus2024Volume" />
</Remove>
<Display Level="None" AcceptEULA="TRUE" />
</Configuration>

Run:

setup.exe /configure remove-office.xml

Best for:
Device cleanup, reinstallation, troubleshooting, or replacing one Office edition with another.

22. Remove Office LTSC 2021

<Configuration>
<Remove>
<Product ID="ProPlus2021Volume" />
</Remove>
<Display Level="None" AcceptEULA="TRUE" />
</Configuration>

For Office LTSC Standard 2021, use:

<Product ID="Standard2021Volume" />

23. Remove Visio LTSC or Project LTSC

Remove Visio LTSC 2024

<Configuration>
<Remove>
<Product ID="VisioPro2024Volume" />
</Remove>
<Display Level="None" AcceptEULA="TRUE" />
</Configuration>

Remove Project LTSC 2024

<Configuration>
<Remove>
<Product ID="ProjectPro2024Volume" />
</Remove>
<Display Level="None" AcceptEULA="TRUE" />
</Configuration>

Best for:
License changes, role changes, app cleanup, or the removal of products from shared devices.

24. Configure Office LTSC 2024 Updates

Office LTSC does not receive ongoing feature updates like Microsoft 365 Apps, but it does receive security and quality updates.

Microsoft states that Office LTSC 2024 typically receives updates once a month on the second Tuesday and does not receive new features after release.

Example XML:

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

25. Configure Office LTSC 2021 Updates

<Configuration>
<Add OfficeClientEdition="64" Channel="PerpetualVL2021">
<Product ID="ProPlus2021Volume">
<Language ID="en-us" />
</Product>
</Add>
<Updates Enabled="TRUE" Channel="PerpetualVL2021" />
<Display Level="None" AcceptEULA="TRUE" />
</Configuration>

26. Disable Office LTSC Updates

This is not usually recommended, but some organizations temporarily disable updates for controlled environments.

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

Use this carefully. Disabling updates may prevent Office from receiving important security and reliability fixes.

27. Use a Specific Office LTSC Version

In compatibility-sensitive environments, you may need to deploy a specific Office LTSC build.

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

Replace:

16.0.xxxxx.xxxxx

with the exact build you want to deploy.

Best for:
Testing, controlled rollouts, compatibility validation, and rollback scenarios.

28. Add a MAK Product Key in the XML

Some LTSC deployments use MAK activation. In that case, you can include the product key in the XML file.

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

Security note:
Be careful when storing product keys in XML files. Limit access to the deployment folder and avoid exposing the file to standard users.

Microsoft notes that activation for volume-licensed Office remains based on KMS or MAK activation.

Common Office Deployment Tool Commands

Download Office LTSC installation files

setup.exe /download configuration.xml

Install Office LTSC

setup.exe /configure configuration.xml

Remove Office LTSC

setup.exe /configure remove-office.xml

Install from an elevated command prompt

cd C:\ODT
setup.exe /configure configuration.xml

Best Practices for Office LTSC XML Configuration

1. Use the Right LTSC Channel

Use the correct channel for the Office LTSC version:

Using the wrong channel is one of the most common ODT XML mistakes.

2. Use the Right Product ID

Do not mix Microsoft 365 Apps product IDs with LTSC product IDs.

For Office LTSC 2024 Professional Plus, use:

<Product ID="ProPlus2024Volume">

Not:

<Product ID="O365ProPlusRetail">

3. Choose 64-Bit Unless You Need 32-Bit

For most modern deployments, 64-bit Office is the better default. Use 32-bit only when older add-ins, macros, or business applications require it.

4. Test Before Broad Deployment

Before deploying Office LTSC to many devices, test your XML file on one clean machine or virtual machine.

Check:

• Office installs successfully
• Correct apps are installed
• Excluded apps are not installed
• Activation works
• Updates work as expected
• Existing Office versions are removed if needed

5. Keep Separate XML Files for Different Jobs

Instead of one large XML file for everything, use clear file names:

install-office-ltsc-2024.xml
install-office-ltsc-2021.xml
install-visio-2024.xml
install-project-2024.xml
remove-office-ltsc-2024.xml
download-office-ltsc-2024.xml

This approach simplifies troubleshooting.

6. Use Local SourcePath for Offline or Large Deployments

If many devices will install Office from the same network, download the files once and deploy from a network share.

This reduces repeated internet downloads and gives IT more control over the installation source.

7. Document Your XML Files

Add comments or maintain a simple internal deployment note explaining:

• Office version
• Product ID
• Channel
• Language
• Architecture
• Apps excluded
• Source path
• Activation method
• Last tested date

This documentation helps future administrators understand the rationale behind the XML file's configuration.

Troubleshooting Office LTSC XML Deployment

Office LTSC Does Not Install

Check these common issues:

Office Downloads but Does Not Install

The /download command only downloads installation files.

This command downloads:

setup.exe /download configuration.xml

This command installs:

setup.exe /configure configuration.xml

You usually need both steps when preparing an offline or local-source deployment.

“Couldn’t Install” or “Something Went Wrong” Error

Check:

• The command prompt is running as administrator
• The XML file is in the same folder as setup.exe
• The product ID matches your license
• The update channel matches the Office LTSC version
• The device can reach the source path or Microsoft CDN
• Security software is not blocking the setup

Excluded Apps Still Appear

This can happen if Office was already installed before you changed the XML file.

To fix it, remove Office and reinstall it with the corrected XML file, or rerun ODT with the updated configuration, depending on the app and installation state.

Office LTSC Activation Fails

Check whether your organization uses:

• KMS activation
• MAK activation
• Active Directory-based activation

Also, confirm that the installed product matches the license key or activation method.

Final Thoughts

The XML file is the heart of an Office LTSC deployment. Once you understand the correct product IDs, channels, languages, and ODT commands, you can create repeatable deployment files for Office LTSC 2024, Office LTSC 2021, Visio LTSC, and Project LTSC.

For the full deployment workflow, read the main Office Deployment Tool Guide. If you are working with a specific version, continue with our guides for the Office Deployment Tool for Office 2024 and the Office Deployment Tool for Office 2021.

Together, these guides give you complete insights into the Office Deployment Tool, from basic setup to version-specific deployment and practical XML configuration examples.