Pushing Google Chrome Extensions – Addigy

This KB will assist you in pushing Google Chrome Extensions to Chrome Browers.

In order to accomplish this, copy the following .plist into a TextEdit file (make sure that it is reading in plain text, not rich text).

Google chrome must already be installed

Be sure to customize the relevant settings/keys specific to the extension you are deploying.

Line 39: CONFIGURATION NAME is responsible for the name of the config that will appear in Addigy.

Line 93: PLACE EXTENSION IDENTIFIER HERE is responsible for adding the extension of your choice.

Here is the .plist that you will need:

<?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>PayloadIdentifier</key>

<string>com.company.profile.chrome</string>

<key>PayloadRemovalDisallowed</key>

<true/>

<key>PayloadScope</key>

<string>System</string>

<key>PayloadType</key>

<string>Configuration</string>

<key>PayloadUUID</key>

<string>2016-09-12-07-13</string>

<key>PayloadOrganization</key>

<string>Your Company</string>

<key>PayloadVersion</key>

<integer>1</integer>

<key>PayloadDisplayName</key>

<string>CONFIGURATION NAME</string>

<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.normandale</string>

<key>PayloadUUID</key>

<string>121-qasd</string>

<key>PayloadEnabled</key>

<true/>

<key>PayloadDisplayName</key>

<string>Custom: (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>ExtensionInstallForcelist</key>

<array>

<string>PLACE EXTENSION IDENTIFIER HERE;https://clients2.google.com/service/update2/crx</string>

</array>

</dict>

</dict>

</array>

</dict>

</dict>

</dict>

</array>   

</dict>

</plist>

In order to get the identifier, go to the extension in the google web store and get it from your URL, it should look like this:

After you've modified this to your specifications, save it as a .mobileconfig as shown below

After saving, you'd then navigate to Policies>Catalog>MDM Configurations.

Next, select macOS>Custom Configuration in order to upload the configuration that was just made, as seen below:

In order to deploy this configuration, go to the desired policy, then go to MDM configurations, find the configuration you made, and click MDM Configurations --> Add configuration.

Within the same policy, you'd navigate to deploy changes, and click confirm all. If you want the changes to take effect immediately, you can select Deploy Now.

Adding Multiple Extensions

It is possible to add multiple extensions to a single .plist. Copy the string on 93 and paste it into line 95. The file should look like the screenshot below:

You can add more than 2 extensions following this format as long as you keep a space between each string and all of the strings stay within the arrays.

Error Storing Payload: Duplicate Entity

If deploying multiple copies of this .plist you will need to change the PayloadUUID in line 27 otherwise you will receive the following error as shown in the screenshot above: error storing payload: duplicate entity. You can visit uuidgenerator to generate a new UUID that you can use to replace the UUID that is in line 27 in the .plist file.

If you encounter any issues with this please feel free to contact support@addigy.com