Overview of Click-to-Run customization
Applies to: Office 365 ProPlus
Topic Last Modified: 2014-06-05
Summary: Provides information about how to customize Click-to-Run for Office 365 installations and how to enforce user and computer settings.
Audience: IT Professionals
Administrators can customize Click-to-Run for Office 365 installations. Click-to-Run is a Microsoft streaming and virtualization technology that significantly reduces the time that is required to download and use Office products. The Office 2013 release provides a downloadable Office Deployment Tool for Click-to-Run that allows administrators to download Click-to-Run product and language sources to an on-premises location. This is useful in scenarios where administrators want to minimize the demand on the network or to prevent users from installing products from the Internet because of corporate security requirements.
Group Policy is an infrastructure that administrators can use to implement specific computing configurations for users and computers. They can use Group Policy to enforce user and computer settings for Click-to-Run for Office 365 installations. They can also apply policy settings to member servers and domain controllers within the scope of an Active Directory forest and use Group Policy to define configurations. After doing that one time, they can rely on the operating system to enforce the settings.
Group Policy settings are contained in Group Policy objects (GPOs), which are linked to selected Active Directory Domain Services (AD DS) containers. These include sites, domains, or organizational units (OUs). The settings within GPOs are evaluated by the affected targets by using the AD DS hierarchical container structure.
In this article:
Office 2013 introduces a new customization tool for Click-to-Run for Office 365. Administrators can use the Office Deployment Tool to customize Click-to-Run installations and to allow users to install Click-to-Run for Office 365 products from an on-premises location. You can download the Office Deployment Tool from the Microsoft Download Center site. The download includes a sample configuration file, Configuration.xml. To customize an installation, administrators run the Office Deployment Tool and provide a customized Configuration.xml file. The Office Deployment Tool performs the tasks that are specified by using the optional properties in the Configuration.xml file.
The Office Deployment Tool is a downloadable self-extracting executable file that contains the following:
Office Deployment Tool .exe file
A sample Configuration.xml file
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 configuration file for Click-to-Run to specify installation instructions such as the following:
Product and languages to install
Product and languages to remove
Installation source path
Level of user interface to display
Product updates behavior
For more information about the Office Deployment Tool, see the following resources:
You can use Group Policy for both Windows Installer-based Office 2013 and Click-to-Run for Office 365. It is the recommended tool for managing the user and computer settings that you want to enforce in Office 2013 and Click-to-Run for Office 365.
In an Active Directory environment, administrators apply policy settings to groups of users and computers in a site, domain, or organizational unit to which a Group Policy object is linked. True policy settings are written to the approved registry key locations for policy, and these settings have access control list (ACL) restrictions that prevent non-administrator users from changing them. Administrators use Group Policy to create highly restricted or lightly managed desktop configurations, which depends on their specific business and security requirements. Group Policy settings have precedence over Office Customization Settings (OCT) user settings. The OCT is used to customize Windows Installer-based installations.
For more information about Group Policy for Office 2010, see the following resources. The information also applies to Office 365 ProPlus and Office 2013.
Office 2013 introduces a new application and document compatibility tool, known as Telemetry Dashboard, It replaces the Office 2010 compatibility tools Office Migration Planning Manager (OMPM), Office Code Compatibility Inspector (OCCI), and Office Environment Assessment Tool (OEAT). You can use the Group Policy Administrative Template files to configure and enable Telemetry Agent, a component of Telemetry Dashboard. For more information about Group Policy settings for Telemetry Dashboard, see Deploy Telemetry Dashboard.