Google Chrome Managed (Windows)

Description

Chrome browser user experience may be managed on multiple device types by way of a Google Management Token available through the Google Admin Console.

Details on obtaining a token and Chrome management can be found in the following KB:

• Managed Google Chrome

The directions below describe applying the token to Windows devices. Use a system-level Chrome installation: Google does not support per-user Chrome installations for this Windows enrollment method.

Ingredients

• Chrome App Fileset
  
• Chrome Browser Enrolment Token (only available via Google Admin Console)

Directions

A Chrome Application Fileset will be required to instal Chrome onto devices.  There are multiple ways to achieve this.

Winget is built into FileWave and Google Chrome is available via Winget:

If preferred, a standalone installer could be downloaded and delivered as an installer or converted to a file level installation by way of Fileset Magic.

Likewise, there is more than one way to apply the token to manage the Chrome browser.  Registry diff files can be used, but this example offers a scripted method.

Before deploying this Fileset, review its effect on existing browser management. The supplied script removes existing Chrome enrollment registry keys and attempts to set both the enrollment token and mandatory enrollment. It is not just a token-copy operation. Use a pilot device first; for an already managed browser, follow Google's enrollment and re-enrollment guidance before changing its management.

KB Windows Google Chrome Administrator Token.fileset.zip

1. Create a Fileset Group for Windows Chrome
2. Add the created Google Chrome Installer Fileset into this group
3. Download the above Fileset
4. Unzip and drag the Fileset into this same Fileset Group 

   

5. Open the scripted Fileset for the Administrator token and select the containing PowerShell script: 

   

6. Choose Get Info > Executable > Environment Variable 

   

7. Edit the value of the chrome_token variable with the copied Google Management Token from the Google Admin Console
   

Deploy the 'Windows - Google Chrome' Fileset Group to a pilot Windows device and confirm that both the installer and token script complete. After the token is applied, quit Chrome if it is open and launch it again. In the Google Admin console, open Managed browsers and confirm that the device appears in the intended organizational unit before expanding the Deployment. A successful Fileset activation alone does not confirm Chrome enrollment.

Assigning the 'Windows - Google Chrome' Fileset Group targets both the application and configuration Filesets; verify installation and browser enrollment separately.  When there is an update to Google Chrome, replace the version in the Fileset Group with the latest version  (after testing) or switch to a new Fileset Revision if desired.