Enable Monitoring in Google Chrome on macOS Endpoints

The following instructions describe the process of creating an MDM configuration profile to deploy the new Google Chrome extension for macOS endpoints using MDM settings. For illustration purposes, the instructions assume that you plan to deploy the extension using Jamf, an IT management application.
Alternatively, you can install the extension manually using the Chrome Web Store. Make sure that the Chrome Web Store URL is not blocked by your organization's network firewall.
When you download the agent installer package from the Broadcom Product Downloads portal, the package contains a ready-to-use MDM configuration file that you can use with a management application like Jamf to perform several deployment tasks simultaneously. See Sample MDM configuration file for macOS endpoints.
  1. Create a browser policy (
    .plist
    file) which you can upload to Jamf.
    For example:
    <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>ExtensionSettings</key> <dict> <key>egaejpfbkjamgheoingidhokbfnidlpi</key> <dict> <key>installation_mode</key> <string>force_installed</string> <key>update_url</key> <string>https://clients2.google.com/service/update2/crx</string> </dict> </dict> </dict> </plist>
  2. In Jamf, select a configuration profile.
  3. Navigate to
    Application & Custom Settings
    , and then click
    Add
    .
  4. Under
    Creation Method
    , select
    Upload File (PLIST file)
    .
  5. In the
    Preference Domain
    field, type
    com.google.Chrome
    .
  6. Click the
    Upload PLIST file
    button, and then browse to and select the
    .plist
    file that you created in Step 1.
  7. Click
    Save
    .
You can refer to the
System > Agents > Overview
page of the Enforce Server administration console to view and troubleshoot any failed deployments.