Office Click-to-Run update settings - Enhance your O365 patching experience

Microsoft Office products are the most widely used business productivity software worldwide. Hence it is imperative for enterprises to keep them up and running securely. This requires installing Office updates that are released on a regular basis. This document will give an overview of how Patch Manager Plus has enhanced the Office update process with the Click-to-Run technology.

This feature is available for build numbers 10.1.2137.1 and later builds.

What is Click-to-Run technology?

Click-to-Run was a technology introduced by Microsoft to deliver and update Office 2010 products. It is now used by Office versions 2010, 2013, 2016 running on the Office 365 subscription model. Click-to-Run is an alternate installation type for Microsoft products that uses streaming and virtualization to reduce the time taken for installation and to help run multiple versions of Office on the same system.

How does Click-to-Run work?

Click-to-Run products use streaming, so Office applications can be used before the whole suite or product is downloaded completely. After download, Office is stored inside a virtualized application space. This virtual space separates Office Click-to-Run applications from existing Office versions thereby enabling multiple versions of Office to run on one system.

Office Click-to-Run update settings in Patch Manager Plus

The Office Click-to-Run update settings in Patch Manager Plus gives users the option to choose the language packs and additional proofing tools that they want downloaded with their Office updates. Further users can automate the process of adding newly discovered languages in the network to their selected language packs list and also choose to re-download old updates with new ones once a new language pack has been added.

Why do we have this option in Patch Manager Plus?

The Click-to-Run technology was adopted to enhance the download and installation process of Office applications. Similarly Office updates have certain concerns when they are being downloaded. For instance, Office applications cannot be patched when they are in use and they consume more bandwidth per agent. To avoid these effects, to support more language packs, and to manually allow users to install updates, Patch Manager Plus has come up with the Office Click-to-Run update settings.

How do you configure this option?

  • Navigate to Admin > Patch Settings > Office Click-to-Run settings.
  • Once in there, you have the options to select the Language Packs to be downloaded with the updates and Additional Proofing Tools you want downloaded with your office updates.
  • office-click-to-run

  • Make sure you select the proofing tools already installed in your environment to avoid installation failures, along with any additional proofing tools you might need.
  • Furthermore, you can automatically enable the newly added language packs to be included in your preferred language list and also have your Office updates re-downloaded incase a new language is added to the list.
  • System administrators can also configure the update process behavior, that is, they can choose to ask the end-users to close Office applications before their update process, or force close open applications and proceed with the update process.
  • What is the workflow once these settings are configured?

    Once these settings are enabled, the Office Click to Run patch build is downloaded to the server by the Office deployment tool and is maintained in the server store. The entire zip is not downloaded by the agent, instead the agent only downloads the necessary files (language packs and additional proofing tools you have opted for) during the update process. This saves substantial agent bandwidth and allows us to support more language packs. Manually updating of Office Click to Run application will also become possible as the enhanced process resets the UpdateURL once the patching is done. These settings also leverage the native end-user notifications that Office Click-to-Run updates have to keep end users informed about the updating processes. All in all these settings streamline the Office update process and reduce the possibilities of Office updates failing or getting corrupt.

    This feature will include an extracted folder of about 7 GB in addition to the zip file already present, which will take up Disk space. This is the expected behavior of this feature and users don't have to worry about the reduced Disk space.


1) Where do the Office patches get downloaded, once the Click-to-Run settings are enabled?

Once the Click-to-Run Settings have been enabled, the Office patches will be downloaded in the server's patch store i.e. the Patch Repository Location, as specified in the server.

In the case of a Distribution Server, the Office patches will be downloaded in the specified patch repository location of both the Central Server and the Distribution Server.

2) How to enhance bandwidth usage while using Office Click-to-Run?

To enhance bandwidth usage, users can navigate to the Office Click-to-Run Settings and can set the Download source for Distribution Servers as Microsoft CDN. Once this is done, the Office patches will directly be downloaded to the Distribution Servers from the Microsoft CDN and will result in less bandwidth usage between the Central Server and the Distribution Servers.

If the download source is set as Microsoft CDN, the patches will be downloaded to the Distribution Servers while a copy of the patches (as ZIP) will also be downloaded to the Central Server as a backup. This ensures that the systems get continued updates without any interruption, in case there are technical glitches in the Office Click-to-Run Settings.

3) Can we use Cleanup Settings to delete the Office patches specifically, before 3 months?

As of now, all the patches will be deleted from the patch repository, based on the Cleanup Settings configured. Hence, it isn't currently possible to delete these patches before 3 months.

4) Why is there a size mismatch between the office patch shown in the ManageEngine console and the patch downloaded on the server?

The Office patch and size displayed on the console are that of the Office deployment tool and not the installation files. Once this executable is downloaded in the Patch Repository, this will automatically be extracted to obtain the required setup and configuration files.

The language packs and proofing tools selected in the Click-to-Run Settings will automatically be applied to the configuration files, which in turn modifies its size.

Hence, there appears to be a size mismatch in the downloaded files, since it is based on the language packs selected by the user.