If you have signed up for Office 365 and provisioned user accounts for the users in your organization, you can enable users to install Office 365 ProPlus (and Project Pro, Visio Pro, SharePoint Designer, or Lync products) directly from the Office 365 portal. This is the default option. In managed enterprise environments, end-users may not have permission to install software from the Office 365 portal. Administrators can use the Office Deployment Tool to manage Click-to-Run installations.
To customize a Click-to-Run for Office 365 installation, administrators run the Office Deployment Tool and provide a custom Configuration.xml configuration file. The Office Deployment Tool performs the tasks that are specified by using the optional properties in the configuration file.
For the Office 2013 release, administrators can run the Office Deployment Tool to perform the following tasks:

  • Generating a Click-to-Run for Office 365 installation source To do this, administrators prepare a configuration file and run the tool in download mode.
  • Configuring Click-to-Run for Office 365 clients To do this, administrators prepare a configuration file and run the tool in configure mode.
  • Creating an App-V package To do this, administrators prepare a configuration file and run the tool in packager mode.

Note:
This article is part of the Content roadmap for Office 365 ProPlus for IT Professionals. Use the roadmap as a starting point for articles that help you deploy Office 365 ProPlus in your organization.

Are you looking for help with installing Office with Office 365? You may be looking for Get started with Office 365 and Install Office with Office 365, which will help you learn how to set up and use Office 365 on your computer, phone, and tablet.

  • Overview
  • Office Deployment Tool command-line properties
  • /download mode
  • Configuration.xml file for use with /download command
  • /configure mode
  • Configuration.xml file for use with /configure command
  • /packager mode
  • Configuration.xml file for packager mode

Overview

You can download the Office Deployment Tool from the Microsoft Download Center site. Administrators download and run the self-extracting executable file, which contains the Office Deployment Tool .exe file, dynamic link library resources (dlls), and a sample configuration file, configuration.xml.

To run the Office Deployment Tool, administrators must provide:

  • A command line property to specify the mode in which to run the tool
  • A custom Configuration.xml file to specify installation instructions such as the following:
  • Product and languages to install or remove
  • Source path
  • Level of user interface to display
  • Logging options
  • Product updates behavior

Office Deployment Tool command-line properties

You can use the Office Deployment Tool commands to do the following:

  • Specify the mode in which to run the Office Deployment Tool.
    • Use download mode to download Click-to-Run installation source for Office 365 products and languages to an on premise location.
    • Use configure mode to configure, and install Click-to-Run for Office 365 products and languages.
    • Use packager mode to create an App-V package from a Click-to-Run installation source.
  • Indicate the location of the custom Configuration.xml file.
  • Display Help for the tool.

The Office 2013 release supports the following Office Deployment Tool command-line properties:

  • /download
  • /configure
  • /packager
  • /help

Note/packager and /configure. To run these modes you must have elevated privileges or an administrator command prompt.

/download mode

Downloads Click-to-Run for Office 365 product source files.

/download uses the following syntax:

>setup.exe /download <path of Configuration.xml file>

Example:

\\server\share\setup.exe /download \\server\share\CustomC2RConfig.xml

where:

  • setup.exe is the Office Deployment Tool executable
  • \\server\share is the network location of the Setup.exe file and the custom Click-to-Run Configuration.xml file, CustomC2RConfig.xml
  • /download downloads product source files, depending on the options that you define in the Configuration.xml file

For information about the Configuration.xml syntax, see Click-to-Run for Office 365 Configuration.xml file.

Configuration.xml file for use with /download command

The following table lists Configuration.xml file elements that are used to download the Click-to-Run for Office 365 source by using the /download command. For more information about Configuration.xml, see Click-to-Run for Office 365 Configuration.xml file.

/download Required information:

  • Product(s)
  • OfficeClientEdition (attribute of Add element). Specifies the edition of Click-to-Run for Office 2013 product to use: 32- or 64-bit.
  • Language(s)

Optional information:

SourcePath. Indicates the location to save the Click-to-Run source when you run the Office Deployment Tool in download mode. If you do not specifySourcePath, Setup will attempt to create an \Office\Data\… folder structure in the working directory from which you are running setup.exe.

The following example of a Configuration.xml file is used with the /download command to download Office 365 ProPlus Click-to-Run English sources to the following location: \\server\share. Administrators can use any text editor, such as Notepad, to edit the Configuration.xml file that is included with the Office Deployment Tool download.

Note:

For the current release, you can install only one language. To install additional languages, run the Office Deployment Tool again and specify the additional language to install in the configuration.xml file. The Preview release supports English, Japanese, and Spanish languages.
<Configuration>
  <Add SourcePath="\\server\share" OfficeClientEdition="32">
   <Product ID="O365ProPlusRetail" >
     <Language ID="en-us" />
   <Product/>
  </Add>
</Configuration>

/configure mode

Configures, installs, or removes Click-to-Run for Office 365 products and languages, and applies any options that you specify in the custom Click-to-Run Configuration.xml file.
/configure uses the following syntax:
>setup.exe /configure Example:
\\server\share\Setup.exe /configure \\server\share\MycustomC2RConfig.xml
where:
setup.exe is the Office Deployment Tool executable
\\server\share is the network location of the Setup.exe file and the custom Click-to-Run Configuration.xml file, MycustomC2RConfig.xml in this example
/configure configures, installs, or removes products that are based on the options that you define in the custom Configuration.xml file

More Read

 

Suggested Posts:

Leave a Reply