Deploying Office Click 2 Run

In this article, Mano will go over the process required to deploy Microsoft Office as a Click 2 Run Package for Office 365 customers.

by | Published: | Updated:

Many organizations require deploying Microsoft Office as part of the complete Office 365 solution offered by Microsoft. Compared to previous versions of Microsoft Office,  the current 'Click to Run' package requires a slightly different installation and removal approach. This article will cover the installation process for the current C2R version, as well as how to uninstall previous Microsoft Office versions.

To start off the process, you need to make sure your computer has Internet access, as most of the resources we'll be using need to be downloaded from Microsoft's website. Also, if you plan on deploying the package to several computers, make sure to create a network share accessible to all the required machines.

Package Creation and Deployment

  1. Download the ODT Click to Run package for Office 365.
     
  2. Extract the package contents to a local folder, for example: C:\ODT.
     
  3. Modify the Configuration.xml file in accordance to your deployment requirements. The Configuration.xml file includes the Microsoft Office products to be installed, the supported languages, the location of the source files and more useful parameters.

The following Configuration.xml example shows the parameters to deploy Office ProPlus as well as Visio in English and Hebrew from the network location \\MyServer\Office365ODT\:

<Configuration>

 <Add SourcePath="\\MyServer\Office365ODT\" OfficeClientEdition="32" >

    <Product ID="O365ProPlusRetail">

        <Language ID="en-us" />

        <Language ID="he-il" />

    </Product>

   <Product ID="VisioProRetail" >

        <Language ID="en-us" />

        <Language ID="he-il" />

   </Product>

</Add>

<Updates Enabled="TRUE" UpdatePath="http://officecdn.microsoft.com/pr/39168D7E-077B-48E7-872C-B232C3E72675" />

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

<Logging Path="%SYSTEMDRIVE%\O365_Logs\" />

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

</Configuration>

More information about the parameters in the Configuration.xml file can be found here.

4.  To download the required setup files, after creating the Configuration.xml file, run the following command:

setup.exe /download <PATH-TO-CONFIGFILE>\Configuration.xml

All the Microsoft Office files and listed products will be downloaded to the specified location. Make sure to alter the path according to your requirements.

5.  Once the download completes, you can install and configure Microsoft Office by running this command:

Setup.exe /config <PATH-TO-CONFIGFILE>\Configuration.xml

All the listed Microsoft Office products in the XML file will be installed and any configuration changes required will be made.

Removing Older Microsoft Office Versions

If we need to remove any older version of Microsoft Office from the target machines, we can use Microsoft's published FixIT packages. The packages can be download here, but for us to be able to use them silently in a mass deployment, we only need the VBS files included in them. To extract the VBS files, just run the FixIT tool and copy the files from the %temp% directory while the tool is still open.

OffScrub03.vbs – Remove Office 2003

OffScrub07.vbs – Remove Office 2007

OffScrub10.vbs – Remove Office 2010 

OffScrub_O15msi.vbs – Remove Office 2013 / 365 (MSI)

OffScrub_O15c2r.vbs – Remove Office 2013 / 365 (C2R)

So in order for us to be able to silently remove a specific Microsoft Office product version, we'll run the following command:

cscript SCRIPT_NAME.vbs ALL /Quiet /NoCancel

Where SCRIPT_NAME represents the name of the script related to the Microsoft Office version we want to remove.

Mano Dory

About the Author

Mano Dory - Infrastructure Consultant at U-BTech Solutions

-

comments powered by Disqus