Google Chrome Managed (macOS)

Description

AfterChrome installing Chrome, some configuration maycan be desirable,managed examplesusing maymethods include:outlined in the KB: Google Chrome Configuration Recipe (mac0S)

However,

• Blockfrom autothe updates
Google
• SetAdmin homeConsole, page
it
• Disableis Welcomepossible Page
to

create a Management Token, push the token to devices and then control the browser experience with Google's Cloud management.

The below shows configuration for macOS.  For Windows you may wish to consider GPO: Manage Chrome updatesBrowser (Windows)Management Token can be used on macOS, Windows, Android and iOS.

Ingredients

• FW Central
• Chrome installer application already as a Fileset
• TheGoogle providedAdmin configurationConsole Fileset:access
• Chrome Browser Enrolment Token

macOS

Directions

Google

Google have their own KB on this topic: Enroll cloud-managed Chrome browsers

1. From the Chrome Browser view in the Google Admin console, use the 'kebab' (vertical ellipsis) to copy the token

FileWave

1. Download the above provided Fileset zip file, expand and drag both the Fileset and Configuration Profile into FileWave > Filesets
2. TheOpen 'Googlethe ChromeProfile Ksadmin'for containsediting 'ksadmin.sh'and scriptaccess whichthe configuresCustom ksadminSettings to allow silently disabling Chrome updatesPayload
3. TheEdit Configurationthe ProfileCloudManagementEnrollmentToken hasString, exampleentering setupsthe thattoken mayfrom requirethe editing,Google e.gAdmin Welcome and Home Page; replacing www.filewave.comconsole

Preference Names
A list of policies can be found at: Chrome Enterprise policy list

Association

When associating, to ensure the configuration is installed with the Application, consider creating a Fileset Group:

AssociatingAssigning the 'Google Chrome Managed'Management Token' Fileset Group will ensure Application and Configuration are associated to devices.  Below is an example using Deployments:

When there is an update to Google Chrome, replace the version in the Fileset Group with the latest version,version  (after testing,testing) andor re-instaladd Googlea Chrome Ksadmin

Controlling Updates

Updates may be managed with the use of additional configuration that may be added to thenew Fileset Group.Revision if desired.

The following profile contains:

<key>updatePolicies</key>
<dict>
  <key>com.google.Chrome</key>
  <dict>
    <key>UpdateDefault</key>
    <integer>3</integer>
  </dict>
</dict>

Download: Chrome Preferences Keystone.mobileconfig

Edit the profile integer to match the desired experience:

Setting	Description
0	Turns on auto-updates. Updates are always applied when detected by Google Software Update. This is the default value.
1	Updates are installed only from the scheduled update checks. Manual update checks will not install updates.
2	Turns off auto-updates. This stops Google Software Update automatically updating all users to the latest stable version of Chrome. Updates are only applied when the user manually checks for updates. For example, on the chrome://help page or by running the CheckForUpdatesNow.command utility.
3	Updates are never applied.

Add the 'mobileconfig' file as a Custom Settings Configuration Profile Payload

Google Software Management
Other Google software may also be managed with this process. Please read Manage Chrome updates (Mac) for full details of management options.