Close Menu
    Facebook X (Twitter) Instagram
    Trending
    • Successful Adoption of a “Cloud First” Strategy
    • Speaking at Nordic Virtual Summit
    • Workplace Ninja User Group Denmark February Meetup
    • Workplace Ninja User Group Denmark Meetup – May 2022
    • Workplace Ninja User Group Denmark Meetup – April 2022
    • Speaking at Modern Endpoint Management Summit 2022
    • Speaking at Nordic Virtual Summit 2022 – 3nd Edition
    • CoLabora Recordings – January 2022
    RONNIPEDERSEN.COM
    • Home
    • Enterprise Mobility
      • Configuration Manager
      • Identity and Access
      • Information Protection
      • Intune
    • Cloud and Data Center
      • Data Center Management
      • Group Policy
      • Enterprise Security
      • Hyper-V
      • PowerShell
    • Guides
    • Webcasts
    • Links
    • About
      • Contact me
      • Disclaimer
    RONNIPEDERSEN.COM
    You are at:Home»Enterprise Mobility»Configuration Manager»Deploying Office 2016 using the Click-to-Run Deployment Tool

    Deploying Office 2016 using the Click-to-Run Deployment Tool

    16
    By Ronni Pedersen on September 22, 2015 Configuration Manager, Enterprise Mobility

    Update: Before you read this post, check out my new guide on TechNet right here: https://gallery.technet.microsoft.com/How-to-Deploying-Office-e9f296fb

    Today Microsoft has released the Office 2016 Deployment Tool.

    This Tool allows administrators to customize and manage Office 2016 Click-to-Run deployments. It will also help administrators to manage installations sources, product/language combinations, and deployment configuration options for Office Click-to-Run.

    The tool can be downloaded here: http://www.microsoft.com/en-us/download/details.aspx?id=49117&WT

    Prepareing and Deploying Office 2016

    After downloading and extracting the Deployment Tool, we need to create a download.xml that is used to download or update the installation source with the latest version of Office 365 Pro Plus (2016).

    We also need to create a configuration.xml file that are used when deploying Office 2016.

    clip_image001

    Note: When you attempt to download the Office 365 ProPlus from the Microsoft content delivery network (CDN) using the Office Deployment Tool (ODT) you might get the following error message:

    clip_image005

    This occurs when you leave the SourcePath blank in the configuration.xml.  For example, your configuration.xml looks as follows:

    <Configuration>
    <Add SourcePath=” ” OfficeClientEdition=”32″ >
    <Product ID=”O365ProPlusRetail”>
    <Language ID=”en-us” />
    </Product>
    </Add>
    </Configuration>

    To workaround this issue, you will need to specify a path (UNC or Local folder) in the SourcePath attribute of the configuration.xml file.  This requirement is for /download only and not for /configure.

    More info about this bug: http://blogs.technet.com/b/odsupport/archive/2015/09/22/office-365-proplus-2016-couldn-39-t-install-error-30015-1007-when-trying-to-download-using-the-office-deployment-tool-odt.aspx

    Creating the Configuration files

    This is how the download.xml file that I use in my lab looks like:

    SNAGHTML2c9573c

    Note: There is a bug with the

     

    And here is the configuration.xml file:

    clip_image004As you can see, I’m downloading both the Danish and English version but I’m only deploying one language.

    Here is a cool tool that will help you create the xml files you need:
    http://officedev.github.io/Office-IT-Pro-Deployment-Scripts/XmlEditor.html

    Running Setup

    To download the latest version you need to run the following command:

    Setup.exe /download download.xml

    And when the download is complete you can run the following command to install Office:

    Setup.exe /configure configure.xml

    That’s it… Happy deployment…

     

    /Enjoy

    +Ronni Pedersen

    For more updates on Deployment and Enterprise Client Managemet please follow me on Twitter: @ronnipedersen

    If you want to connect via LinkedIn, you can reach me here: https://dk.linkedin.com/in/ronnipedersen

    • Tweet
    • Share 0
    • +1
    • LinkedIn 0

    Related

    Ronni Pedersen
    • Website
    • Facebook
    • X (Twitter)
    • LinkedIn

    My name is Ronni Pedersen and I'm currently working as a Cloud Architect at APENTO in Denmark. My primary focus is Enterprise Client Management solutions, based on technologies like AzureAD, Intune, EMS and System Center Configuration Manager. I'm is also a Microsoft Certified Trainer and Microsoft MVP in Enterprise Mobility.

    Related Posts

    Speaking at Nordic Virtual Summit

    Workplace Ninja User Group Denmark February Meetup

    Speaking at Modern Endpoint Management Summit 2022

    16 Comments

    1. Pingback: Office 2016 Released - msdigest.net - by Peter Schmidt [MVP & MCSM]

    2. Kenneth Sundby on September 23, 2015 09:33

      This works fine too: SourcePath=”.”

      Reply
      • Ronni Pedersen on September 30, 2015 18:58

        Great tip 🙂 Thanks for sharing!

        Reply
    3. kaktus on September 23, 2015 19:18

      Hello,

      Very nice write-up! Do you know will this C2R installation method be the only available installation option with Office 2016 or will there be the normal setup.exe with Office Customization Wizard like it was with Office 2013 ?

      Reply
      • Ronni Pedersen on September 30, 2015 18:56

        There will be a normal MSI download also. It should be ready for download tomorrow.
        I expect to released a full guide to that version within 2 weeks.

        Reply
    4. glenn on September 23, 2015 21:18

      But how can i make a file so that i can selected by the install

      Reply
      • Ronni Pedersen on September 30, 2015 18:51

        You can’t… But you can create multiple configuration files that fits all your needs 🙂
        Check out my new guide here: https://gallery.technet.microsoft.com/How-to-Deploying-Office-e9f296fb

        Reply
    5. pmdci on September 26, 2015 10:18

      Hi Ronni,

      I’m glad to see you manage to use Office Deployment Tool in the end. In my case I’ve not been so lucky.

      In fact I manage to make it work in one VM, where I use the following config to choose what applications to install:

      This code worked perfectly in VM1. In fact I could see during the install process that the progress window shows only the icons of the applications being installed.

      In VM2 the file simply does not work. Rather than showing the icons of the applications being installed, it shows a big OFFICE 2016 logo.

      Back in VM1 I then tried to use another file to remove Word:

      But that didn’t work…

      Any ideas of what might be wrong?

      Regards,
      P.

      Reply
      • Ronni Pedersen on September 30, 2015 18:49

        I don’t have the answer to your problem, but I’ve just released this guide: https://gallery.technet.microsoft.com/How-to-Deploying-Office-e9f296fb/view/Reviews
        Check it out 🙂

        Reply
    6. PiotrZ on October 5, 2015 14:56

      Hi
      I don’t think using SoftwareMicrosoftWindowsCurrentVersionUninstallO365ProPlusRetail – en-us. is good way for Detection Rule, esspecialy for later on updates deployed by SCCM.
      For me you should put SOFTWAREMicrosoftOfficeClickToRunConfigurationVersionToReport == 16.0.xxxxxxx

      Reply
      • Ronni Pedersen on October 8, 2015 08:57

        I agree. There are some scenarios where you want to control the version, but for customers that want to use Office as a service, and stay on the latest version, this will work just fine.

        Reply
    7. Flemming WIlton Hansen on March 10, 2016 14:26

      Tak for hjælpen,

      På alle de MS sider jeg har fundet omkring dette emne, er der en syntaxfejl. Har derfor ikke fået downloadet noget før jeg fandt din side.

      Hos MS står der : Setup.exe /download download.xml

      ..og ikke som du gør Setup.exe /download download.xml , som virker !!!

      Mvh
      Flemming

      Reply
      • Ronni Pedersen on March 11, 2016 21:22

        Tak for feedback 🙂

        Reply
    8. Steve Johnson on April 25, 2016 14:48

      Hi,
      I’m trying to deploy Office 2016, and have searched for help…your blog helped greatly until the configuration file…the one shown in the blog is all remarked out, so I couldn’t get the configuration to work (unless you meant to leave it all remarked out). Your download xml file worked flawlessly, so I wondered if your configuration file just didn’t get uploaded…or is it supposed to be blank?

      Thanks…

      Reply
    9. Martin on May 27, 2016 10:35

      Hi Ronnie

      in your post you write:

      Note: There is a bug with the

      And here is the configuration.xml file:

      a bug with the….. the….. ??

      Reply
    10. Hoder on October 5, 2016 14:04

      What’s your experience with SourcePath?

      Reading your guide, I notice you don’t use any SourcePath in Configuration.xml Is Setup.exe clever enough to use the files from the Office folder automatically, or will the lack of SourcePath mean you download the needed install files from Microsoft on every install?

      Reply
    Leave A Reply Cancel Reply

    This site uses Akismet to reduce spam. Learn how your comment data is processed.

    Follow
    APENTO

    Follow APENTO here:

    Subscribe to Blog via Email

    Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    About
    My name i s Ronni Pedersen and I'm currently working as a Cloud Architect at APENTO in Denmark. My primary focus is Endpoint Management and Security, based on Microsoft technologies. I'm also a Microsoft Certified Trainer and a dual Microsoft MVP in both Security and Windows.
    Recent Posts
    • Successful Adoption of a “Cloud First” Strategy
    • Speaking at Nordic Virtual Summit
    • Workplace Ninja User Group Denmark February Meetup
    • Workplace Ninja User Group Denmark Meetup – May 2022
    • Workplace Ninja User Group Denmark Meetup – April 2022
    Archives
    TOP POSTS
    • Deploying Office 2016 using the Click-to-Run Deployment Tool
    • Find the TimeZoneName for your SCCM/MDT Deployments
    • How to Access the MBAM BitLocker Recover Keys directly in SQL
    • SCCM 2012 R2: Where is the SMSTS.log located?
    • Integrate Jamf Pro with Microsoft Intune
    RECENT COMMENTS
    • Sebi on Prepare for Co-Management: Migrate Intune Devices without user affinity
    • Vadim P on SCCM: Failed to Get Client Identity (80004005)
    • TM on Active Directory Based Activation in an multi domain environment
    • unkown on Setting OSDComputerName using CustomSettings.ini
    • TJ Scott on Setting OSDComputerName using CustomSettings.ini
    DISCLAIMER
    The content on this website is presented "as-is" with no guarantees. The use of scripts from this website is at your own risk. Always test before putting something in production! Opinions expressed are my own.
    © 2025 ThemeSphere. Designed by ThemeSphere.

    Type above and press Enter to search. Press Esc to cancel.