Home » Office 365 Patch Deployment
 

Office 365 Patch Deployment

Overview

Microsoft Office products are the most widely used business productivity software worldwide. Hence, it is imperative for enterprises to keep them secure and functional by installing Office updates released regularly. This document provides an overview of how Endpoint Central has enhanced the Office update process with the Click-to-Run technology.

NOTE- 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 Endpoint Central

The Office Click-to-Run update settings in Endpoint Central 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 Endpoint Central?

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, Endpoint Central has come up with the Office Click-to-Run update settings.

Pre-Requisites

Click on Threats & Patches → Settings → Office Click-to-Run 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. Select the languages of your choice. Make sure you select the language of the proofing tools already installed in your environment to avoid installation failures, along with any additional ones you might need.

Enable the option Automatically add Office Click-to-Run application languages, newly discovered in the network to the selected Language Pack list to automatically include any newly added language packs in your preferred language list.

If you want your already downloaded Office updates re-downloaded in the instance of a new language added to your preferred list, enable the option Re-download old updates with the newly added language packs.

Under the section Download source for Distribution servers, select the download source as:

  • Microsoft CDN if you have configured Distribution Server in your enterprise domain.By selecting this option, you can enhance the bandwidth usage. The patches will be downloaded to the Distribution Servers, while a copy of the patches (as ZIP) will be downloaded to the Central Server.This ensures that the systems get continued updates without any interruption, in case there are technical glitches in the Office Click-to-Run Settings. This is the most preferred setting.
  • Central Server if you have not configured Distribution Server in your enterprise domain. The patches will be downloaded directly from the Central Server to the agent. But this will consume a lot of network bandwidth. This will be the default setting.

 

Choosing how to Proceed

 

Under the How would you like to proceed with installation when Office applications are in use section, choose:

  1. Close applications in use forcefully and then update if the user has continuously skipped the update and you want to patch that specific application immediately to keep domain endpoints up-to-date. However, force-closing the application may result in data loss if business-critical tasks are underway, as the user may not be able to save progress. Choose this option only if you know the application is idle on those endpoints and no business-critical tasks are happening.
  2. Do not install updates when an Office application is in use if the user is working on business-critical tasks using that Office 365 application. The updates will be skipped, and the decision for installing will be revisited in the next refresh cycle based on whether the application is open.
  3. Allow the end-user to skip/close the application in use and proceed with the update. By selecting this, users can skip patch installation if they are using Office 365 applications for business-critical tasks. Once skipped, the decision for installing will be revisited in the next refresh cycle. It is recommended to choose this option to avoid affecting business productivity.

After configuring the Office Click-to-Run Settings, click on Save.

Deployment of Office 365 Patches

Once these settings are enabled, the Office Click-to-Run patch build is downloaded to the server by the Office deployment tool and maintained in the server store. Instead of downloading the entire zip, the agent only downloads necessary files (language packs and additional proofing tools) during the update process. This saves substantial agent bandwidth and supports more language packs. Manually updating Office Click-to-Run applications becomes possible as the process resets the UpdateURL once patching is done. These settings also leverage native end-user notifications that Office Click-to-Run updates use to keep end users informed about the update process. Overall, these settings streamline the Office update process and reduce the likelihood of updates failing or becoming corrupt.

NOTE- 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.

You can deploy the patches either manually or using an Automate Patch Deployment Task

Manual Deployment

Under Missing Patches tab, you can search and filter the required Office 365 patches. To learn more about how to manually deploy patches manually, refer to this page.

Automate Patch Deployment

You can automate the patching of Office 365 applications by creating an Automate Patch Deployment task.

Office 365 patch deployment using Automated Patch Deployment

 

When you are creating an APD task, under Select Applications section, after choosing the Updates & Severities of your choice, enable Patch Specific Applications and under Selected Applications if you type 'microsoft 365', you can see all the supported Office 365 applications listed. You can choose to add whatever applications that you want to be deployed with this APD task. After choosing the desired applications, configure other options and choose required targets where you want to automate Office 365 patching. By doing these, the deployment approved Office 365 patches for those chosen applications will be automated in those chosen targets. To learn in detail about creating Automate Patch Deployment tasks, refer to this page.

Troubleshooting

During the patching process, you might run into problems either during the download or installation of Office 365 patches.

Download Failure

To troubleshoot download failures, refer to this page.

Installation Failure

To troubleshoot Installation failures, refer to this page.

 

If you have any further questions, please refer to our Frequently Asked Questions section for more information.