Office Deployment Tool XML Configuration Examples for Office 2021 & 2024

Office Deployment Tool XML Configuration Examples for Office 2021 & 2024
Published: May 28, 2026 | Updated: September 22, 2026

Need a copy-ready Office Deployment Tool XML file? Use the examples below for Office LTSC 2024, Office LTSC 2021, Visio LTSC and Project LTSC. Each template is designed for a specific job: install, download, silent deployment, local-network deployment, languages, app exclusions or removal.

This page is the technical XML reference for the Office Deployment Tool guide. Use that guide for the overall download and setup workflow; use this page when you need the exact configuration.xml to copy, adapt and run.

Before you begin: Office Deployment Tool (ODT) deploys Click-to-Run Office products on Windows. Match the product ID, update channel and 32-bit or 64-bit architecture to the licence and existing Office installation on the device. All Office products installed on one device must use the same architecture.

Quick start: create, download and install

  1. Download and extract the latest Office Deployment Tool from Microsoft.
  2. Save one of the examples below as configuration.xml in the same folder as setup.exe.
  3. For a local or offline source, run setup.exe /download configuration.xml first.
  4. Run setup.exe /configure configuration.xml from an elevated Command Prompt to install or remove products.
setup.exe /download configuration.xml
setup.exe /configure configuration.xml

The download command is optional when the device can install directly from Microsoft’s Content Delivery Network. For Microsoft’s current deployment guidance and supported options, see Deploy Office LTSC 2024.

Choose the right product ID and channel

ProductProduct IDChannel
Office LTSC Professional Plus 2024ProPlus2024VolumePerpetualVL2024
Office LTSC Standard 2024Standard2024VolumePerpetualVL2024
Office LTSC Professional Plus 2021ProPlus2021VolumePerpetualVL2021
Office LTSC Standard 2021Standard2021VolumePerpetualVL2021
Project Professional 2024ProjectPro2024VolumePerpetualVL2024
Project Standard 2024ProjectStd2024VolumePerpetualVL2024
Visio LTSC Professional 2024VisioPro2024VolumePerpetualVL2024
Visio LTSC Standard 2024VisioStd2024VolumePerpetualVL2024

Use only the product ID that matches your licence. Do not use a Microsoft 365 Apps ID such as O365ProPlusRetail when deploying an Office LTSC volume product.

Copy-ready Office Deployment Tool XML examples

1. Install Office LTSC Professional Plus 2024

Use this standard 64-bit English template for Office LTSC Professional Plus 2024.

<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.

2. Install Office LTSC Standard 2024

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

3. Install Office LTSC Professional Plus 2021

Use the 2021 channel and product ID together. Do not mix 2021 and 2024 values in the same configuration file.

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

Need a retail Office 2021 product rather than LTSC? Use the product ID that matches the retail edition and omit the LTSC channel; see Microsoft Office 2021 Professional Plus for the relevant edition.

4. Download Office LTSC 2024 files for a local or offline install

Save this as download-office-ltsc-2024.xml. The SourcePath must be a writable folder when you run the download command.

<Configuration>
  <Add OfficeClientEdition="64" Channel="PerpetualVL2024"
       SourcePath="C:\ODT\OfficeLTSC2024">
    <Product ID="ProPlus2024Volume">
      <Language ID="en-us" />
    </Product>
  </Add>
</Configuration>
setup.exe /download download-office-ltsc-2024.xml

After the download completes, use the local-source template below to install from those files. Download 32-bit and 64-bit packages separately.

5. Silent install from a local network share

Replace \\FileServer\OfficeLTSC2024 with your actual UNC share. The user or deployment account must have read access to it.

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

This is suitable for branch offices, imaging, restricted-bandwidth sites and other offline deployment scenarios.

6. Remove older MSI Office while installing Office LTSC 2024

RemoveMSI is for older Windows Installer (MSI) Office products, such as Office 2016 and earlier. It does not remove Click-to-Run Office 2019; plan that removal separately.

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

7. Install extra languages and proofing tools

This installs English Office with French and German proofing tools. Use full language packs instead of proofing tools where users need the complete Office interface in another language.

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

To match the primary Office language to Windows, replace en-us with MatchOS.

8. Install Office LTSC 2024 but exclude selected apps

ODT installs an Office suite, then excludes the applications you do not want. This example leaves Word, Excel and PowerPoint while excluding Access, Outlook, OneNote and Publisher.

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

Other commonly used values are Excel, PowerPoint and Word. Confirm that the application is included in the suite before trying to exclude it.

9. Install Office LTSC 2024 with Visio and Project

Use one configuration file when the products use the same architecture and the 2024 LTSC channel. Ensure you own a valid licence for each product.

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

For Standard editions, replace the ID with VisioStd2024Volume or ProjectStd2024Volume. You can also deploy Visio LTSC Professional 2024 or Project LTSC Professional 2024 alone by keeping just that product block.

10. Keep Office LTSC 2024 updates enabled

Office LTSC does not receive ongoing feature updates, but it should receive security and quality updates. The default update source is the Office CDN. Use an UpdatePath only when you actively maintain updates on a local share.

<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>

11. Use MAK activation securely

If your organisation uses MAK activation, add the key as PIDKEY. Store the XML in a restricted deployment location; do not expose a real product key in a public share, support ticket or source repository.

<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>

12. Remove Office LTSC Professional Plus 2024

Save this as remove-office-ltsc-2024.xml, then run the configure command.

<Configuration>
  <Remove>
    <Product ID="ProPlus2024Volume" />
  </Remove>
  <Display Level="None" AcceptEULA="TRUE" />
</Configuration>
setup.exe /configure remove-office-ltsc-2024.xml

Common XML deployment errors

SymptomCheck first
Nothing installsRun the command from an elevated Command Prompt; confirm the XML is well formed and the product ID/channel match.
Download completes but installation does not start/download only stages files. Run setup.exe /configure configuration.xml afterwards.
Local-source installation failsCheck the UNC path, network access and that the matching architecture was downloaded.
Office conflicts with an existing installationAll installed Office products must share one architecture. Use RemoveMSI only for MSI products; plan Click-to-Run removal separately.
Activation failsConfirm that the installed product, licence type and KMS or MAK activation method match.

Deployment checklist

  • Use the correct LTSC year, channel and product ID.
  • Choose 64-bit unless a tested add-in or application requires 32-bit.
  • Test the XML on a pilot device before wide deployment.
  • Keep separate XML files for download, installation and removal tasks.
  • Document the deployment’s channel, language, architecture, exclusions and activation method.
  • Keep security and quality updates enabled unless a controlled change process requires otherwise.

Next steps

For the full ODT workflow, including where to obtain the tool and how to run it, read the Office Deployment Tool guide. For 2024-specific deployment steps, see the Office Deployment Tool 2024 setup guide.

Verified

Verified Partners

Official keys at affordable prices.

Instant Delivery

Instant Delivery

Buy now and get your keys in seconds.

Live Support

24/7 Live Support

Our team is always here to assist.

Trusted Users

Trusted by 100k+ Users

Over 1 Million keys delivered worldwide.

FAQ About Office Deployment Tool XML Configuration Examples for Office 2021 & 2024

What is an Office Deployment Tool XML configuration file?

An Office Deployment Tool XML configuration file tells ODT how to install, download, update, or remove Office. For Office LTSC, it defines the LTSC product ID, channel, language, architecture, display settings, update behavior, and optional products such as Visio or Project.

What channel should I use for Office LTSC 2024?

Use: Channel="PerpetualVL2024". Microsoft specifies PerpetualVL2024 for volume-licensed Office LTSC 2024 products.

What channel should I use for Office LTSC 2021?

Use: Channel="PerpetualVL2021". Microsoft specifies PerpetualVL2021 for volume-licensed Office LTSC 2021 products.

What is the product ID for Office LTSC Professional Plus 2024?

Use: <Product ID="ProPlus2024Volume">

What is the product ID for Office LTSC Professional Plus 2021?

Use: <Product ID="ProPlus2021Volume">

How do I silently install Office LTSC?

Use this display setting: <Display Level="None" AcceptEULA="TRUE" />. Then run: setup.exe /configure configuration.xml

Can I install Office LTSC without an internet connection?

Yes. Use ODT to download the installation files first, copy them to a local or network location, and install using a SourcePath in the XML file.

Can I install Visio or Project with Office LTSC?

Yes. Add the Visio or Project product ID to the same <Add> section as Office. For example: <Product ID="VisioPro2024Volume"> or <Product ID="ProjectPro2024Volume">

Can I exclude apps from Office LTSC?

Yes. Use <ExcludeApp> inside the product section. Example: <ExcludeApp ID="Access" />, <ExcludeApp ID="Publisher" />, <ExcludeApp ID="OneNote" />

Should I use Office LTSC or Microsoft 365 Apps?

Use Office LTSC if your organization needs a fixed, perpetual-license Office release with no ongoing feature updates. Use Microsoft 365 Apps if users need cloud-connected features and continuous feature updates. Microsoft notes that Office LTSC 2024 does not receive new features after release.

Related posts
loader
Loading...