Overview

 

Deploying Office 365 as a remote deployment package requires the package to be downloaded in line with a configuration xml that defines the package content. This configuration.xml is then used in the deployment of that package along with a setup.exe stub installer. As it is a remote distribution package, we need it to install silently and without any prompts to the end-user.

 

Downloading what you need.

 We use the Office Deployment Tool to create a setup.exe and generate a sample configuration.xml that can be modified according to your needs;

 

https://www.microsoft.com/en-us/download/details.aspx?id=49117

 

If more configuration of the xml is required then you can use https://officedev.github.io/Office-IT-Pro-Deployment-Scripts/XmlEditor.html to create the xml but you will still need the setup.exe from the ODT.

 

SAMPLE WORKING XML 

 

<Configuration>

 

  <Add OfficeClientEdition=”32″ Channel=”Monthly”>

 

    <Product ID=”O365ProPlusRetail”>

 

      <Language ID=”en-us” />

 

    </Product>

 

    <Product ID=”VisioProRetail”>

 

      <Language ID=”en-us” />

 

    </Product>

 

  </Add>

 

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

 

</Configuration>

 

 Once you have the setup.exe and the configuration.xml for your needs then the following command line will download the Office payload ready for the deployment;

 

setup.exe /download configuration.xml

 

If you do not specify a target directory, it will create an Office folder and download into there all required files.

 

Deploying the package

 You can zip the setup.exe, configuration.xml and the Office folder and its contents. Approx 1.7Gb.

 This zip file can then be uploaded to either the K1000 to form a managed install or the K2000 as a post installation task.

The deployment command line is ;

 setup.exe /configure configuration.xml

 

Pin It on Pinterest