Usage guide: Chrome update compliance

Overview

Maintaining updated web browsers is vital for security and efficiency, but managing updates can be difficult. Employees might neglect updates, leading to outdated Chrome versions on enterprise devices, posing security risks and limiting productivity. “Workflow: Chrome update compliance” pack helps to keep Chrome updated. It checks if the running Chrome version matches the latest one and prompts a restart if not. After two prompts, if not updated, it automatically restarts Chrome.

Ensure your library pack is properly configured by following the steps highlighted in its configuration guide:

Configuration guide: Chrome update compliance

Workflow Structure

This workflow is designed to operate automatically via an schedule trigger. This section describes the key steps in this workflow:

The workflow starts by checking whether the Chrome browser requires a restart due to an pending update. If no update is pending and a restart isn’t necessary, the workflow ends processing.

If a restart is needed then the campaign is triggered to inform the user about the need of restarting the browser.

In case the user consents, the remote actions restarts the browser and workflow terminates, recording that the necessary action has been taken.
If the user declines the Chrome browser restart, the workflow makes another attempt after a delay. In this scenario, if a restart is still required and the user once again refuses to restart the Chrome browser, a forced restart is implemented after a delay.