When you start the setup of Office 2016 or 2019, it installs all the applications based on some predefined settings. This behavior is often undesirable. Therefore, you can customize the installation using the Office Deployment Tool (ODT) and a configuration file.

Microsoft no longer ships newer versions of Office with an MSI installer, but instead uses the Click-to-Run technique. Therefore, the setup program downloads the installation files from the internet. However, these are also available over local data media as usual.

Microsoft Office Click to Run setup in Task Manager

Microsoft Office Click to Run setup in Task Manager

No options for a standard setup ^

Unlike a conventional installation, Click-to-Run by default does not allow you to select which applications you want to install or specify the path where you want to save them.

The Click to Run setup will install all Office applications without giving the user a choice

The Click to Run setup will install all Office applications without giving the user a choice

However, if you want to customize the setup, Microsoft offers the ODT for this purpose. It consists of an .exe file that unpacks its contents into the selected directory when executed.

Content of the Office Deployment Tool

Content of the Office Deployment Tool

If you want to bypass this procedure and the corresponding User Account Control (UAC) prompt, you can also extract the contained files directly with 7-Zip.

Contents of the ODT ^

The package consists of serveral files: the setup.exe, example configuration files, and a text file with the end-user license agreement (EULA). To prepare for a customized installation, you have to create a new configuration file or edit the supplied template in the next step.

One example configuration delivered with the Office Deployment Tool

One example configuration delivered with the Office Deployment Tool

It is available in XML format and accepts a handful of elements to control the setup. Under "Configuration" an "Add" node is required. Its attribute "OfficeClientEdition" (with values "32" or "64") determines whether to install the 32- or 64-bit version.

Specify the source path ^

The attribute "SourcePath" points where to retrieve the installation files. If you have mounted the ISO file as a virtual DVD, you specify the root directory of the drive here (for example "D:\"):

<Add OfficeClientEdition="32" SourcePath="D:\">

Alternatively, you can copy the installation media to a share in the network and enter the universal naming convention (UNC) path.

As a child node of Add, the configuration expects one or more Product elements. These do not describe the individual applications, but the stock-keeping units (SKUs) of Office using the ID attribute. Allowed values for Office 2016 and 365 are, for example:

  • O365ProPlusRetail
  • O365BusinessRetail
  • VisioProRetail
  • ProjectProRetail
  • AccessRuntimeRetail
  • LanguagePack

Office 2019 supports the following strings, amongst others:

  • ProPlus2019Volume
  • Standard2019Volume
  • ProjectPro2019Volume
  • ProjectStd2019Volume
  • VisioPro2019Volume
  • VisioStd2019Volume

This support document contains the full list of all product IDs the ODT accepts.

Excluding certain Office applications ^

Another child element of Product determines which applications not to install. For each program you would like to do without, you insert such an element and specify its name in the attribute ID, for example:

<ExcludeApp ID="Access" />

Supported values for the applications are:

  • Access
  • Excel
  • Groove
  • Lync
  • OneDrive
  • OneNote
  • Outlook
  • PowerPoint
  • Publisher
  • Word

Groove also covers OneDrive for Business, and Lync covers Skype for Business.

Installation of Office 2019 is limited to the four core applications

Installation of Office 2019 is limited to the four core applications

More options ^

In addition to this core configuration, the ODT also supports several other options. With these, you can acknowledge the EULA automatically or specify which channel to use for future updates.

A useful setting allows you to pin the Office applications to the taskbar. However, this only works under Windows 7 and 8.1; in Windows 10 it has no effect.

The Microsoft Website has complete documentation for all supported settings.

Configuration example ^

A sample configuration for installing from local media could look like this:

<Add OfficeClientEdition="32" SourcePath="D:\">
<Product ID="O365ProPlusRetail"> 
<Language ID="de-de" />
<ExcludeApp ID="Publisher" />
<ExcludeApp ID="Access" />
<ExcludeApp ID="OneDrive" />
<ExcludeApp ID="Groove" />
<ExcludeApp ID="Lync" />
<ExcludeApp ID="OneNote" />
<Updates Enabled="TRUE" Channel="Broad" />
<Display Level="None" AcceptEULA="TRUE" />
<!--  <Property Name="AUTOACTIVATE" Value="1" />  -->
<Property Name="PinIconsToTaskbar" Value="TRUE" />

Running a custom setup ^

Once the configuration file contains all desired settings, you can start the ODT. Launch the setup.exe from the downloaded ODT archive.

The command looks like this:

setup.exe /configure configuration.xml
Starting the ODT with a custom installation

Starting the ODT with a custom installation

After a short preparation phase, the tool displays the icons of the programs it will install.

Removing applications ^

If you have installed unwanted Office components, either because you have not excluded them in the configuration file or because you have executed the standard setup, you cannot uninstall them via the control panel. Uninstalling them via the control panel will remove Office entirely.

However, it is not necessary to remove the entire package and then reinstall the desired programs. Instead, you can use the ODT and simply add the programs you want to uninstall under ExcludeApp in the configuration file.

Subscribe to 4sysops newsletter!

The subsequent execution of setup.exe will then remove all applications you have already installed but excluded in the configuration file.

  1. 8string 2 years ago

    Good information but you forgot one small yet significant item. As stated in the XML files you show, but you cut it out from the screen grab, this only works on versions of Windows Enterprise. It will not run on Home or Pro. Or have I missed something in reading the documentation when I downloaded ODT? 


  2. Riccardo 1 year ago

    Same here, any chance to get it working on Windows 10 pro. I launch setup.exe from ODT extracted zip after configuring xml file but nothing happen.


  3. Johan Löhr 1 year ago

    It really does work with Windows 10 Home edition.

    First attempt failed . . . I had the complete MS Office 2016 Professional Plus suite installed on my laptop and tried to remove the unwanted components with a script. This didn't work at all and I was left with a second installation of MS Office.

    At second attemp I first removed both Office installations using the Control Panel. Next I installed Word, Excel, PowerPoint and Outlook with the following script:


      <Add OfficeClientEdition="32" SourcePath="I:\">
        <Product ID="ProPlusRetail">
          <Language ID="nl-NL" />
                    <ExcludeApp ID="Access" />
                    <ExcludeApp ID="OneNote" />
                    <ExcludeApp ID="Publisher" />
                    <ExcludeApp ID="OneDrive" />
                    <ExcludeApp ID="Groove" />
                    <ExcludeApp ID="Lync" />
                    <ExcludeApp ID="Teams" />


    Explanation of the lines in the script:

    • I installed the 32 bit version --> <Add OfficeClientEdition="32"
    • I mounted an image of the Office installation DVD to virtual drive I --> SourcePath="I:\">
    • Because I have MS Office 2016 Professional Plus, I changed <Product ID="O365ProPlusRetail"> into <Product ID="ProPlusRetail">
    • I'm Dutch, so . . . --> <Language ID="nl-NL" />
    • The next 7 lines exclude the unwanted programs.

    Save the script as 'configuration.xml' in the folder where you extracted the zip file. In my case 'D:\ODT'.

    To start the installation, I opened a DOS box as administrator and changed to 'D:/ODT. Finally the setup process was started with the command 'setup /configure .\configuration.xml'.


  4. grubs 7 months ago

    April 2021 and this worked perfectly to install selective components of Office 365 Home.  Followed  Johan Löhr 's comment in structuring the xml file (but did 64 bit instead).

    Then mounted the img file for office 365 I had downloaded  which creates the virtual F: drive in my case

    The ODT setup.exe and configuration.xml were in a folder on my desktop and I ran the setup.exe as administrator from the command line. -  it found the files on the virtual F: drive due to the SourcePath  line in the xml

    Many thanks to Wolfgang and to Johan Löhr for additional clarity.


Leave a reply to grubs Click here to cancel the reply

Please enclose code in pre tags

Your email address will not be published. Required fields are marked *


© 4sysops 2006 - 2021


Please ask IT administration questions in the forums. Any other messages are welcome.


Log in with your credentials


Forgot your details?

Create Account