FAQ: Deploy Office 365 click-to-run using System Center Configuration Manager

FAQ: Deploy Office 365 click-to-run using System Center Configuration Manager

Q. How can I download the Office 365 click-to-run so I can deploy using local deployment capabilities?
 

A. Click-to-run for Office 365 normally pulls the bits down directly from Microsoft however its also possible to download the click-to-run for local deployment.

  1. Download the Office Deployment Tool from http://www.microsoft.com/en-us/download/details.aspx?id=36778 and install to a folder
  2. Once installed modify the default configuration.xml file to match the desired configuration. Help on the configuration.xml syntax can be found at https://technet.microsoft.com/en-us/library/jj219426(v=office.15). Below is an example format that downloads the core Office application set.


     
     

     

     
     
     
  3. Begin the download of the click-to-run using the configuration.xml configuration
    setup /download configuration.xml
  4. Once download you can navigate to the downloaded folder and you will see a number of cabinet files
  5. An App-V 5 version can be created which can then be loaded and deployed using System Center Configuration Manager 2012
    setup /packager configuration.xml s:\office\clicktorun\AppV5
  6. The App-V package will be created in the specified folder and can be loaded into SCCM using the Create Application action and selecting a type of Microsoft Application Virtualization 5. During the create process change the Name of the application to something like Office 365 ProPlus and set the Manufacturer and software version.
  7. Once imported into Configuration Manager you can customize the application deployment by specifying which specific applications should be deployed for various deployment types as needed.

    Once you have deployed the Office 365 click-to-run there are a number of methods to keep it updated. Typically you would not want the clients to automatically update and so in the configuration XML you would set the to FALSE or you would leave as true but configure your own UpdatePath which would point to a share on the network where you would download the updated Office 365 as required using the Office Download Tool. This can also be configured using Group Policy using the Office group policy templates and setting the machine Updates configuration settings. A great blog that details this can be found at http://blogs.technet.com/b/office_resource_kit/archive/2014/01/28/managing-updates-for-office-365-proplus-part-2.aspx, http://blogs.technet.com/b/odsupport/archive/2014/02/03/managing-updates-with-office-2013-click-to-run.aspx and https://technet.microsoft.com/en-us/library/dn761708.aspx.

    Alternatively you can create an updated version of the App-V Office 365 using the process above each time you want to deploy a new update.

TAGS: Office 365
Hide comments

Comments

  • Allowed HTML tags: <em> <strong> <blockquote> <br> <p>

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.
Publish