Configuration guide: Chrome update compliance

Introduction

To get started with this library pack, please ensure all related content is installed and configured appropriately. This page provides guidance on which content is included and how to configure it.

Please keep in mind this is just a guide and represents suggested configurations. You are free to customize and edit content as you see fit based on your specific environment.

This page will guide you through the structure of the content.

Pre-requisites

This library pack contains content from the following expansion products

Some of these products offer default access to their respective content, and can still be used without the expansion products. To learn more about the default thresholds for expansion products, visit the extended documentation.

Content list and dependency

This library pack contains the following content and dependencies:

Type	Name	Description	Dependencies
Workflows	Chrome update compliance	Triggers remote check to determine if the Chrome browser is operating on an outdated version compared to the installed one. Users will be prompted with a campaign to restart their browser, enabling the update to be fully implemented.
Remote actions	Invoke Chrome update	Detecting scenarios whereby the browser Google Chrome has been updated on a device but the user has not yet restarted the browser.	Required as a workflow step to check if device is pending a Chrome browser restart.
Campaigns	Update Chrome - Invoke	Informs users that their Chrome browser needs to restart for the chrome update to complete.	Required to include a notification with the "Invoke Chrome update" remote action.

Type

Name

Description

Dependencies

Workflows

Chrome update compliance

Triggers remote check to determine if the Chrome browser is operating on an outdated version compared to the installed one. Users will be prompted with a campaign to restart their browser, enabling the update to be fully implemented.

Remote actions

Invoke Chrome update

Detecting scenarios whereby the browser Google Chrome has been updated on a device but the user has not yet restarted the browser.

Required as a workflow step to check if device is pending a Chrome browser restart.

Campaigns

Update Chrome - Invoke

Informs users that their Chrome browser needs to restart for the chrome update to complete.

Required to include a notification with the "Invoke Chrome update" remote action.

Configuration guide

To effectively use this library pack, the content must be installed and configured appropriately. Below are some suggested steps to install and configure the content properly before use.

Step 1) Install library pack content

Go to the Nexthink Library and install all required content.

Step 2) Edit campaigns

Navigate to the manage campaigns administration page to review and edit your campaigns.

For each installed campaign, please ensure to:

Customize the sender name and image.
Review and adjust questions.
Publish the campaign when you are ready to use it.

We recommend the following configurations for this campaign:

Name	Trigger	Priority
Update Chrome - Invoke	Remote action	Not urgent

Name

Trigger

Priority

Update Chrome - Invoke

Remote action

Not urgent

Step 3) Configure remote action(s)

Navigate to the manage remote action administration page to review and edit your remote actions.

We recommend the following configurations for these remote actions:

Name	Trigger	Schedule Query	Parameters to edit
Invoke Chrome update	Manual		Change campaign ID if needed

Name

Trigger

Schedule Query

Parameters to edit

Invoke Chrome update

Manual

Change campaign ID if needed

Invoke Chrome update - input parameters

Name	Default value	Description	Allow the user to enter a custom value
Restart Chrome	False	This input controls whether to force the restart of the Chrome browser. If it is set to True the Campaign ID is disregarded (not sent) and the browser is force restarted	Yes
Restart Chrome campaign ID	update_chrome_invoke	This input is mandatory. If the restart_chrome input is set to False we will invoke the Campaign to prompt the user to restart	No

Name

Default value

Description

Allow the user to enter a custom value

Restart Chrome

False

This input controls whether to force the restart of the Chrome browser. If it is set to True the Campaign ID is disregarded (not sent) and the browser is force restarted

Yes

Restart Chrome campaign ID

update_chrome_invoke

This input is mandatory. If the restart_chrome input is set to False we will invoke the Campaign to prompt the user to restart

Step 4) Maintain workflow trigger

We recommend triggering this workflow manually or on a daily schedule across all devices using the Chrome browser to ensure the browser version stays up to date.

Name Trigger Schedule Query Parameters to edit

Name	Trigger	Schedule Query	Parameters to edit
Chrome update compliance	Manually, Scheduled daily	`devices \| with execution.events \| where binary.name in [ "chrome.exe", "google chrome"]`

Chrome update compliance

Manually, Scheduled daily

devices
| with execution.events
| where binary.name in 
[ "chrome.exe", "google chrome"]

Usage guide

Your content is now configured and ready to be used. For usage overview and recommendations, you can visit the usage guide:

Usage guide: Chrome update compliance