• Using the Office Deployment Tool for Click-to-Run

    With the release of Office 2013 Click-to-Run, Microsoft has created a tool to assist with the deploying of various 2013 Click-to-Run products. This blog walks through how to use and customize the Office Deployment Tool for Click-to-Run.

     

    Step 1.
    Download the Office Deployment Tool for Click-to-Run from here:
    http://www.microsoft.com/en-us/download/details.aspx?id=36778
    Running the officedeploymenttool.exe produces a Setup.exe and a configuration.xml file.

    Step 2.
    Edit the Configuration.xml file:
    Open the configuration.xml file in a word editor. You will see the XML data:
      

       <Configuration>
       <!-- <Add SourcePath="\\Server\Share\Office" OfficeClientEdition="32" >
       <Product ID="O365ProPlusRetail”>
       <Language ID="en-us" />
       </Product>
       <Product ID=”VisioProRetail”>
       <Language ID=”en-us” />
       </Product>
        </Add> -->
        <!--  <Updates Enabled="TRUE" UpdatePath="\\Server\Share\Office\" /> -->
        <!--  <Display Level="None" AcceptEULA="TRUE" />  -->
        <!--  <Logging Name="OfficeSetup.txt" Path="%temp%" />  -->
        <!--  <Property Name="AUTOACTIVATE" Value="1" />  -->
        </Configuration>

    Anything between comment marks <!--   --> will not run. So first remove the comment marks around Add SourcePath and the trailing </Add>

    Next, edit the “\\Server\Share\Office\” path to represent where you want to download the Office files too. Example – “C:\users\admin\desktop\odt\”

    If you are only installing Office Pro Plus, remove <Product ID=”VisioProRetail”> through </Product> to remove Visio from the install. Then save your Configuration.xml file.

    If you are wanting to exclude a specific app or apps from your install, you will use the <ExcludeApp ID="x" /> in the configuration.xml file as outlined here:
    http://technet.microsoft.com/en-us/library/dn745895(v=office.15).aspx

    If you are installing additional products, or a different product, view the following KB article for a full list of product IDs that are supported by the Office Deployment Tool for Click-to-Run:
    http://support.microsoft.com/kb/2842297 

    If you are adding additional languages to your install or want to further customize your install, please see the Reference for Click-to-Run configuration.xml file TechNet article:
    http://technet.microsoft.com/en-us/library/jj219426.aspx

    Step 3.
    Download the media:
    Open a command window and change the directory to the location of your setup.exe file. Next, run Setup.exe /download configuration.xml
     

    The software will begin downloading to your machine. This process usually takes 10 or so minutes, but can take as long as an hour or more depending on your internet connection and other factors.
    Once the software is done downloading, the command window will return to the C:\ Prompt.


     
    Step 4.
    Install the software.
    If you are installing on the same machine that you downloaded the software too, run the following command to start the install: Setup.exe /configure configuration.xml

     

    If you are planning on adding this download to a network share and having multiple users download Office from that location, make sure that DOMAIN COMPUTERS has Read & execute, List folder contents and Read permission. For more info on Installing from a network share, visit our blog entry on that topic here:
    http://blogs.technet.com/b/odsupport/archive/2012/11/20/office-2013-installation-hangs-at-10-percent-when-installing-from-a-network-share.aspx

  • Improvements included in the July 2014 update of Office 2013 for Office 365

    Background

    One of the goals of Office Click-to-Run is to continue to innovate and improve the product with each new update release.  This month is no different.

    More Information

    With the July 2014 update of Office 2013 for Office 365 the following improvements have been made:

    1. Smaller Update Download Package:  Based on feedback from our customers, we have made improvements to the size of the update package that has to be downloaded to each machine being patched.  We now use binary delta compression, so that the amount of data downloaded across the network is reduced by up to 70%.  For example, if you have installed the June 2014 build (version 15.0.4623.1002) and now apply the July 2014 build, the total amount of data downloaded to the computer will be less than 120MB compared to over 310 MB with the traditional update method.
      Note: This holds true only if you apply updates each month.  If you skip months, then the update package size will be larger.

    2. User-mode Streaming:  When installing Office 2013 for Office 365 from a network location, the requirement has been that the local computer accounts need “read” permissions to that network location.  This requirement is documented here.  With the July 2014 update, this is no longer a requirement.

  • New Application Selection feature offered with the May 2014 update of Office 2013 Click-to-Run

    Overview:

    The May 2014 update of the Office Deployment Tool  along with the May 2014 update of Office 2013 Click-to-Run (Build 15.0.4615.1001) offers administrators the ability to customize the installation to select which application to not install.

    Note: Versions of Office Deployment Tool and Office 2013 Click-to-Run prior to May 2014 do not support Application Selection.

    More Information:

    The configuration.xml file provided with the Office Deployment Tool supports a new ExcludeApp element.  This element can be set to an application name to keep that application from installing.  A sample snippet of the configuration.xml file would be as follows:

    <Product ID="O365ProPlusRetail">
          <Language ID="en-us" />
          <ExcludeApp ID="Access" />
          <ExcludeApp ID="Outlook" />
    </Product>

    A complete list of application names and IDs is as follows:

    Application Name Application ID
    Access <ExcludeApp ID="Access" />
    Excel <ExcludeApp ID="Excel" />
    InfoPath <ExcludeApp ID="InfoPath" />
    Lync <ExcludeApp ID="Lync" />
    OneDrive for Business <ExcludeApp ID="Groove" />
    OneNote <ExcludeApp ID="OneNote" />
    Outlook <ExcludeApp ID="Outlook" />
    PowerPoint <ExcludeApp ID="PowerPoint" />
    Project <ExcludeApp ID="Project" />
    Publisher <ExcludeApp ID="Publisher" />
    SharePoint Designer <ExcludeApp ID="SharePointDesigner" />
    Visio <ExcludeApp ID="Visio" />
    Word

    <ExcludeApp ID="Word" />

     

     

     

     

     

     

     

     

     

     

     

     

     

    Once the configuration.xml file has been created with this element added, you can run the command-line:

    <path>\setup.exe /configure <path>\<name of the configuration file>.xml

    This will install Office 2013 Click-to-Run without the application(s) added to the ExcludeApp element.  If an application needs to be added back, you can edit the configuration.xml to remove the ExcludeApp ID entry for that application and rerun the command-line listed above.


    Note: An Online Repair of Office 2013 Click-to-Run will install all the applications on the system, overriding the settings made in the configuration.xml file.

     

  • New Group Policies introduced with the April 2014 update of Office 2013 Click-to-Run

    Background:

    The SP1 for Office 2013 Click-to-Run introduced some new update capabilities to the product.  In order to manage these new features, four new Group Policy settings were introduced with the April 2014 update for Office 2013 Click-to-Run

     

    Requirements:

    In order for these four new policy settings to work, you will need to have at least the April 2014 build of Office 2013 Click-to-Run (Build 15.0.4605.1003) and download the latest Administrative templates files (ADMX/ADML) from the Microsoft Download Center.

     

    More Information:

    The four new Group Policy settings being introduced are summarized in the following table:

    Path Policy Setting Name Description Registry Key
    Microsoft Office 2013 (Machine)\Updates Update Path

    This policy setting allows you to specify the location where Office will get updates from.

    If you enable this policy setting, you can specify one of the following for the update location:  a network share, a folder on the local computer where Office is installed, or an HTTP address. Mapped network drives aren't supported.

    If you enable this policy setting, but you leave the update location blank, Office will get updates from the Internet.

    If you disable or don't configure this policy setting, Office will get updates from the Internet, unless you specify a different location by using the Office Deployment Tool.

    Important: This policy setting only applies to Office products that are installed by using Click-to-Run. It doesn't apply to Office products that use Windows Installer (MSI).

    HKLM\software\policies\microsoft\office\15.0\common\officeupdate!updatepath

    Microsoft Office 2013 (Machine)\Updates Target Version

    This policy setting allows you to specify a version number that you want to update Office to.  For example, version 15.0.4551.1512.

    If you enable this policy setting, you specify the version that you want to update Office to. The next time Office looks for updates, Office will try to update to that version. The version must be available where Office is configured to look for updates (for example, on a network share). If you enable this policy setting, but you leave the version blank, Office is updated to the most current version that's available at the update location for Office.

    If you disable or don't configure this policy setting, Office is updated to the most current version that's available at the update location for Office, unless you specify a different version by using the Office Deployment Tool.

    Important:  This policy setting only applies to Office products that are installed by using Click-to-Run. It doesn't apply to Office products that use Windows Installer (MSI).

    HKLM\software\policies\microsoft\office\15.0\common\officeupdate!updatetargetversion
    Microsoft Office 2013 (Machine)\Updates Update Deadline

    This policy setting allows you to set a deadline by when updates to Office must be applied.

    Prior to the deadline, users will receive multiple reminders to install the updates. If Office isn't updated by the deadline, the updates are applied automatically. If any Office programs are open, they'll be closed, which might result in data loss.

    We recommend that you set the deadline at least a week in the future to allow users time to install the updates.

    If you enable this policy setting, you set the deadline in the format of MM/DD/YYYY HH:MM in Coordinated Universal Time (UTC). For example, 05/14/2014 17:00.

    If you disable or don't configure this policy setting, no deadline is set, unless you specify one by using the Office Deployment Tool. Y

    ou can use this policy setting with the Target Version policy setting to ensure that Office is updated to a particular version by a particular date.

    The deadline only applies to one set of updates. If you want to ensure that Office is always up-to-date, you need to update the deadline in this policy setting every time a new update for Office is available.

    Important:  This policy setting only applies to Office products that are installed by using Click-to-Run. It doesn't apply to Office products that use Windows Installer (MSI).

    HKLM\software\policies\microsoft\office\15.0\common\officeupdate!updatedeadline
    Microsoft Office 2013 (Machine)\Updates Hide Update Notifications

    This policy setting allows you to hide notifications to users that updates to Office are available.

    When automatic updates are enabled for Office, in most cases updates are applied automatically in the background without any user input. However, updates can't be applied if an Office program is open. If an Office program is open, other attempts are made to apply the updates at a later time. If, after several days, updates haven't been applied, only then will users see a notification that an update to Office is available.

    If you enable this policy setting, users won't see notifications that updates to Office are ready to be applied.

    If you disable or don't configure this policy setting, users will see notifications that updates to Office are ready to be applied.

    This policy setting does not apply to notifications associated with update deadlines.

    Important:  This policy setting only applies to Office products that are installed by using Click-to-Run. It doesn't apply to Office products that use Windows Installer (MSI).

    HKLM\software\policies\microsoft\office\15.0\common\officeupdate!hideupdatenotifications

     

    Related Information:

    For more information on the new update related command-line options offered with SP1, please see the blog: The new Update Now feature for Office 2013 Click-to-Run for Office365 and its associated command-line and switches.

    For more information about setting the Update Path, Target Version and the Update Deadline by using the Office Deployment Tool, see Reference for Click-to-Run configuration.xml file.  However, you can't set Hide Update Notification by using the Office Deployment Tool.

  • Lync 2013 and OneDrive for Business are not installed when installing Office 2013 with Service Pack 1

    Update 4/28/14: A new version of the Office Customization Tool (OCT) has been released as part of the Office 2013 Administrative Templates to address this issue.  You can download the OCT from http://www.microsoft.com/en-us/download/details.aspx?id=35554.  Once downloaded double-click the executable to extract the contents which includes the Admin folder.  Copy this folder over the existing \Admin folder in your Office source.

    Create an MSP file to deploy Office 2013 w/ Service Pack 1 using the newly downloaded OCT.  If you want to use an existing MSP file you will need to Import the existing MSP file into the newly downloaded OCT and then save the MSP file.  Not importing an existing MSP file may cause the OCT to fail.

     
    After installing Office 2013 with Service Pack 1 from the Volume Licensing Service Center (VLSC) with a customized MSP file using the Office Customization Tool (OCT), Lync and OneDrive for Business are not installed.

    We are currently investigating the issue and will provide an update soon.  In the meantime, please use one of the following workarounds:
     

    1. Use the Updates folder on the original RTM release and the publically available Service Pack 1 MSP files: http://support.microsoft.com/kb/2817430.

    For further information on using the Updates folder to install Office updates, refer to the following Microsoft article: Deploying software updates with an initial Office 2013 installation


    2. Use the config.xml file to add Lync and OneDrive post install of Office 2013.  To accomplish this, edit the config.xml file to have the following:

    <Configuration Product="ProPlus">

                   <Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />
                   <OptionState Id="GrooveFiles2" State="local" Children="force" />
                   <OptionState Id="LyncCoreFiles" State="local" Children="force" />

    </Configuration>

    Note - this issue also applies to Excel Add-ins Power Map and PowerPivot.  If there is a need to install these add-ins you can do so by adding the following to the config.xml file:

                   <OptionState Id="ExcelAddInPowerMapFiles" State="local" Children="force" />
                   <OptionState Id="ExcelAddInPowerPivotFiles" State="local" Children="force" />


    Once the install of Office 2013 with SP1 has completed, run the following command-line:

    <path>\setup.exe /config <path>\config.xml

    For further information on using the Config.xml file in Office 2013, refer to the following Microsoft Article: Config.xml file reference for Office 2013