Bulk Pre-installation of the DataGalaxy Extension

Organizations rolling the DataGalaxy extension out to a whole fleet can pre-install it centrally instead of asking each user to add it from the Chrome Web Store. This speeds up adoption, keeps every machine on the same version, and avoids disruption when scaling up.

Two management tools are covered here: Microsoft Intune and Jamf Pro. In both, the extension is identified by its Chrome Web Store ID, bpppldnipnppkmongnkihlioaojpmine.

How to pre-install the extension via Microsoft Intune

In Microsoft Intune, go to Devices → Configuration.
Screenshot: the Devices > Configuration path in Intune. (Re-add this image here — the original Freshdesk link expires after a few days.)

Create or update an Administrative Templates policy for the Windows 10 and later platform.
Screenshot: creating an Administrative Templates policy. (Re-add this image here — the original Freshdesk link expires after a few days.)

Select the appropriate included groups you want to use for deployment.

Edit the configuration settings.
Screenshot: editing the configuration settings. (Re-add this image here — the original Freshdesk link expires after a few days.)

Enable the Configure the list of force-installed apps and extensions setting and add the extension ID together with the update URL. Add this entry to the list:
```
bpppldnipnppkmongnkihlioaojpmine;https://clients2.google.com/service/update2/crx
```
Screenshot: the force-installed extension setting with the ID and update URL. (Re-add this image here — the original Freshdesk link expires after a few days.)

How to pre-install the extension and pre-fill the domain via Microsoft Intune

Create a new template > Custom Policy in Intune.
Screenshot: creating a Custom Policy template. (Re-add this image here — the original Freshdesk link expires after a few days.)

Add a configuration file containing the code below. Use this configuration file:

<?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>PayloadDescription</key>
  <string>Force/allow/block Google Chrome extensions on macOS via ExtensionSettings.</string>
  <key>PayloadDisplayName</key>
  <string>Chrome Extensions Policy</string>
  <key>PayloadIdentifier</key>
  <string>com.datagalaxy.chrome.extensions.AA89F643-12D4-4F8B-8CD5-EC9F8C52D464</string>
  <key>PayloadOrganization</key>
  <string>DataGalaxy</string>
  <key>PayloadRemovalDisallowed</key>
  <false/>
  <key>PayloadScope</key>
  <string>System</string>
  <key>PayloadType</key>
  <string>Configuration</string>
  <key>PayloadUUID</key>
  <string>AA89F643-12D4-4F8B-8CD5-EC9F8C52D464</string>
  <key>PayloadVersion</key>
  <integer>1</integer>

  <key>PayloadContent</key>
  <array>
    <dict>
      <key>PayloadType</key>
      <string>com.apple.ManagedClient.preferences</string>
      <key>PayloadVersion</key>
      <integer>1</integer>
      <key>PayloadIdentifier</key>
      <string>com.datagalaxy.chrome.mcx.529E8028-99E5-4C0F-8434-8347AECC5BF2</string>
      <key>PayloadUUID</key>
      <string>529E8028-99E5-4C0F-8434-8347AECC5BF2</string>
      <key>PayloadDisplayName</key>
      <string>Managed Preferences for com.google.Chrome</string>

      <key>PayloadContent</key>
      <dict>
        <key>com.google.Chrome</key>
        <dict>
          <key>Forced</key>
          <array>
            <dict>
              <key>mcx_preference_settings</key>
              <dict>
                <key>ExtensionSettings</key>
                <dict>
                  <!-- DG Production Extension: allowed only -->
                  <key>bpppldnipnppkmongnkihlioaojpmine</key>
                  <dict>
                    <key>installation_mode</key>
                    <string>allowed</string>
                    <key>update_url</key>
                    <string>https://clients2.google.com/service/update2/crx</string>
                    <key>toolbar_pin</key>
                    <string>force_pinned</string>
                  </dict>
                </dict>
              </dict>
            </dict>
          </array>
        </dict>
        <key>com.google.Chrome.extensions.bpppldnipnppkmongnkihlioaojpmine</key>
        <dict>
          <key>Forced</key>
          <array>
            <dict>
              <key>mcx_preference_settings</key>
              <dict>
                <!-- Keys defined by the DataGalaxy extension's managed_schema (Prod) -->
                <key>defaultDomain</key><string>DEFAULT_DOMAIN_HERE</string>
              </dict>
            </dict>
          </array>
        </dict>
      </dict>
    </dict>
  </array>
</dict>
</plist>

Replace DEFAULT_DOMAIN_HERE in the code with your own domain.

Save.

How to pre-install the extension via Jamf Pro

This option lets you configure Jamf so that signing in to the extension in Chrome is pre-filled from a Jamf Pro account.

Go to Configuration Profiles → + New → Applications & Custom Settings → Custom Settings.

Set the preference domain to com.google.Chrome, then upload or paste the property list below. Use this PLIST:

<dict>
  <key>ExtensionSettings</key>
  <dict>
    <key>bpppldnipnppkmongnkihlioaojpmine</key>
    <dict>
      <key>installation_mode</key>
      <string>allowed</string>
      <key>update_url</key>
      <string>https://clients2.google.com/service/update2/crx</string>
      <key>toolbar_pin</key>
      <string>force_pinned</string>
    </dict>
  </dict>
</dict>

Add a second custom settings payload, using com.google.Chrome.extensions.bpppldnipnppkmongnkihlioaojpmine as its preference domain.

Create the PLIST for that second payload. Use this PLIST:

<dict>
  <key>defaultDomain</key>
  <string>example</string>
</dict>

example is the value that will appear in the extension's login field. If you use the clientname.datagalaxy.com structure, replace example with the part that appears before .datagalaxy.com. If you use the datagalaxy.clientname.com structure (or any other variation), replace example with your full version of datagalaxy.clientname.com.