Installing Office 2013/O365 with the Office Deployment Tool (ODT) for C2R


The intention of this post is to focus on the Office Deployment Tool (ODT) as part of the troubleshooting process.
In case you have trouble installing the click-to-run (C2R) version of Office, the ODT may come in handy and help to get your new Office installed.
The key concept is that the ODT allows to separate the file download from the installation process which helps to exclude network related issues from the picture.

If your computer is already in a troubled state from a previous failed attempt and you want to first try the default setup option, consider to follow the troubleshooting steps below:

  • Run the fix-it to remove reminiscences of previous failed installations:

   : Uninstall Microsoft Office 2013 or Office 365

  • Check task scheduler and make sure there are no Office entries left here (if there are any you should delete them)  :


  • Start the machine in clean boot:

   How to perform a clean boot to troubleshoot a problem in Windows 8, Windows 7, or Windows Vista

  • Disable firewall and antivirus; consider disabling proxy settings.


Here is a complete article of basic troubleshooting steps for installation issues: : General troubleshooting for installing Office 2013 and Office 365  

If you still encounter installation issues after testing the above steps, an essential step is the Office Deployment Tool.
We’ll show you the step by step instructions for the ODT in a bit but some administrative notes first.

    * NOTE: The general usage of the ODT is shown as well in this blog post:


   * More information on the Office Deployment Tool is available here:

=> : Office Deployment Tool for Click-to-Run

=> Office Deployment Tool for Click-to-Run (download link)

=> Product IDs that are supported by the Office Deployment Tool for Click-to-Run


That being said, here is a hands on example of the steps to install Office click to run via the Office Deployment Tool.
Please follow the outlined order.

1.  Download the Office Deployment Tool from the above link.

        - The resulting file will be an executable archive:


       - Once you extract it (by simply double clicking on it), it will contain 1 setup and 1 configuration file.



2.  You then need to modify the configuration file “configuration.xml”.

       - Open the file in Notepad

       - Here is how the default looks like and the pieces that need or can be amended:


 -> The comment markers <!-- and --> (highlighted in Red) need to be removed.

-> The value for SourcePath need to be replaced by a valid path on your machine.

       Note: This is the target path for the downloaded files.

      The simplest way would be to use the same path where you have placed the Office Deployment Tool.

      For example in my case, I saved the Office Deployment Tool in C:/ODT, therefore I will replace \\Server\Share\Office\ with C:\ODT\.

 The above are the ‘must do’ edits.


Now, the optional elements are:

-> Bitness of Office: by default it is 32, you may switch it to 64 if you wish. Note: The recommended default is 32 bit.

-> Product ID:

       - you should enter the product you need to install or for which you have a bought a license

       - you can find a list with available products here:

         : Product IDs that are supported by the Office Deployment Tool for Click-to-Run

-> Language:

      - by default we have English, in case you want another language, please replace accordingly

      - a list of language codes is available here:

       : Language Codes

 -> Additional products:

      - By default the configuration file references Office 365 Professional Plus Retail and Visio Professional Retail

      - You may remove the Visio set if you only wish to download one package, and replace the Office 365 Professional Plus with the needed product (if it is another product)

-> In case you need to configure other aspects of the installation you may also remove the <!--  and --> for the other settings.

     - A recommendation in this respect, in order to ensure that product updates are downloaded and installed automatically is to edit also the part highlighted in blue above


To summarize, here is how a basic configuration should look like:


<Add SourcePath="C:\ODT" OfficeClientEdition="32">

    <Product ID="O365ProPlusRetail">

      <Language ID="it-it"/>




<Updates Enabled="TRUE" UpdatePath=""/> 

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

 <!--  <Logging Name="OfficeSetup.txt" Path="%temp%" />  -->

<!-- <Property Name="AUTOACTIVATE" Value="1" />  -->




A full description of available customizations in the configuration.xml is available here.


 After modifying and saving the configuration.xml, we need to run a couple of commands in a CMD (Run as Administrator):

3.  The first is for downloading the setup files on the local machine.

         - The syntax looks like this:

         C:\PATH to setup>setup.exe /download "Path to configuration file\configuration.xml"

      Therefore, using the cd command you need to move into the folder where you have stored the deployment tool, then input the above command.

       In my case, I stored the setup and the configuration file in C:/ODT as seen above.

      Therefore the command will look like this:


      If all is well with the connection to the Office CDN servers, it should start downloading:


     And you will have a confirmation at the end that the packages have been downloaded successfully.

     If you then check in the folder where you have stored the setup.exe and the configuration file, you will see that a new folder has been created, containing the necessary components for the installation.


     The new folder structure won’t contain a setup executable file to run. The installation has to be performed through the deployment tool as well, with a very similar command as the one for download.


4.  In order to install, we need to simply replace the parameter of the above command, from /download to /configure:

       - The syntax will look like this:

        C:\<PATH to setup>setup.exe /configure "<Path to configuration file>\configuration.xml"

      - In my example, this is how it will look like:


     - After running this command, the installation dialog should come up and Office will start installing:

       (in my case I was installing an Italian version hence the progress bar is in Italian)

      - When the installation completed, you will also have the confirmation in the command prompt:



5.  On the Office interface, you will then be prompted to activate the product either with a live account (1) or with a product key (2).



Enjoy your new Office!

Comments (22)
  1. Teodora B says:

    Yes, Francois, you can use the same procedure with HomeBusinessRetail also, as well as all the other codes in this article: : Product IDs that are supported by the Office Deployment Tool

  2. Teodora B says:

    Hi Nathan, I’m glad the information above was helpful.
    Regarding the /packager part, maybe the below sheds some more light:
    Essentially it is used when you want to create an Office App-V package.

  3. Nathan says:

    This is a lot of good info. What about using the /packager option?

  4. Prameela Ampolur says:


  5. Can the same be done with HomeBusinessRetail ???

  6. Adrian says:

    Globally dominates markets for decades … offers only a crappy XML to customize flagship product.

  7. PK82-MS says:

    I followed your instructions, but there was no progress output in the command prompt. I am not sure if that is an error or not, but I did find some files in the specified directory. Weird.

  8. David says:

    I’m going to be using this later to try and deploy Office Home&Business and Publisher Retail versions. There is a major problem with current C2R in that if you already have Office installed and the try to install Publisher the Pub install fails. It leaves
    you with no Publisher and a completely broken Office install. Why? Well having looked at the installation ISOs they are exactly the same. They even have an XML file listing all the product ID’s C2R supports – so what we have is a C2R singleimage installer.
    With different setup.exe based on which product you choose to download it for. So I’m not going to try and use this source with the deployment tool and a custom config.xml to deploy both Office H&B and Publisher at the same time. This should get around this
    ridicuous bug/problem.

    The sooner they ditch C2R the better in my opinion. This is not the first problem I have had with it and will not be the last. I think MS know it is junk as the fix for all C2R is uninstall and try again – aka there is no fix, so pickup dice and roll them again!

  9. Lucy says:

    Hi! I tried to follow your suggestions, but when I try to download the file, I obtain the error 2696484 …..
    can you help? Thank you!

  10. Ringtone says:

    " There was a problem downloading" and if I press the link to the path were it actualy downloads its forbidden

  11. Liana says:

    Hi, thanks for sharing this. May I know how big is the file? As for mine, it didn’t show "Packages downloaded successfully".

  12. adam says:

    So how do I setup a customised installation like I could with Office 2013 – setup.exe /admin

    What’s the equivalent?

  13. Emmanuel says:

    I had the " There was a problem downloading" issue, until I recreated the xml file. The structure (XML compliant) was correct, the synthax was correct, but did not work. Apparently something in the spacing…

    Advise for Lucy and Ringtone: recreate your config file o r try first with the standard one….

  14. senseye says:

    This is another joke from MS, seriously just make downloadable install packages, even if you get this method to work it ends up being twice as slow as the older methods.

  15. Gabe says:

    Microsoft should have kept the install as a install app like the previous versions of Office 365 complicates the deployment of installing Office software by using C2R to implement and deploying Office 2013. They should have stuck with the old way of installing
    via .exe or .msi install setup application.

    If it isn’t broken why change the way on how to implement and deploy newer versions of Office. MS Innovation broken as usual.

  16. How about Office 2016? Does this article support it? I already have all the files (from ms-vnext), what’s next?

  17. Jaime says:

    The download was not working for me because i was setting a Language ID that was not available for the product i was downloading (O365BussinessRetail). I was using my country locale es-ec but using general spanish locale es-es worked fine.

    Also you can set UpdatePath to "" so setup.exe selects the best CDN according to your location.

  18. Winterhowl says:

    I have downloaded Office 2013 Home and Business offline installation package (*.img) and burned that to DVD. Then I am trying to execute office deployment tool with /configure option with following confiugration.xml:

    Anyway installation does install all the applications :-/ Any ideas what is wrong here?


  19. Winterhowl says:

    For some reason xml content is not properly shown, so it can be found from here:

  20. declan says:

    Hi, when I run the configuration.xml, I don’t start seeing the "download progress" as per your photo eg
    Downloading file…..
    Downloading file….
    Downloading file….
    Downloading file….

    There is a process called Click to Run running and a Office folder has been created with the files inside so I guess all is ok I just can’t see the progress of it?

    Or have I ran it wrong?


  21. Andrew says:

    Hey guys. I have recently run into the Total Software Deployment software. The latest version of this app allows installing the click-to-run version of MS Office remotely using silent install. The program isn’t the most convenient solution, but may be
    useful to someone who needs to deploy the C2R Office version to multiple computers.

  22. pete says:

    Love Adrian’s comment. The documentation for this is horrible. It is basically trial and error installing, configuring, and setting this up for users. I can’t pre-activate Office, because the activation is based on the user account, of which I don’t have
    access to. The TechNet guides are sparse and ran into issues immediately, and there aren’t really guides to help you troubleshoot. Very frustrating.

Comments are closed.

Skip to main content