Hey folks,
We recently rolled out Chrome as the default browser on our macOS devices for the sales team. To streamline their workflow and improve efficiency, we need to enforce the installation of specific Chrome extensions, like a CRM tool and an email tracker.
The challenge is ensuring these extensions are automatically installed and stay enabled without the users being able to remove or disable them. Has anyone managed to do this?
19 Views
Hi Johnathon,
We faced a similar requirement on our team and managed to handle it with a configuration profile. Here’s a snippet of the configuration profile we used to force the installation of specific Chrome extensions:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 |
<?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>PayloadContent</key> <array> <dict> <key>ExtensionInstallForcelist</key> <array> <string>Enter you extension ID here</string> </array> <key>PayloadDisplayName</key> <string>Google Chrome</string> <key>PayloadIdentifier</key> <string>com.google.Chrome.C4B9D2F5-83DE-4234-9EC4-F95F40EE126F</string> <key>PayloadType</key> <string>com.google.Chrome</string> <key>PayloadUUID</key> <string>C4B9D2F5-83DE-4234-9EC4-F95F40EE126F</string> <key>PayloadVersion</key> <integer>1</integer> </dict> </array> <key>PayloadDisplayName</key> <string>Untitled</string> <key>PayloadIdentifier</key> <string>Macbook.65E96FC1-CBD1-43C9-A743-A85800BB366E</string> <key>PayloadType</key> <string>Configuration</string> <key>PayloadUUID</key> <string>65E96FC1-CBD1-43C9-A743-A85800BB366E</string> <key>PayloadVersion</key> <integer>1</integer> </dict> </plist> |
Replace “Enter you extension ID here” with the Extension ID of your choice. If you want to add another extension, you can include it within the array, like this:
<string>Extension ID 1<string>
<string>Extension ID 2<string>
Let me know if this works!
I have a query; do we need to restart the device or exit Chrome after associating the configuration profile? Are there any exceptions when deploying this config profile?
After deploying or associating the configuration profile, wait for some time as Chrome installs the specified extensions. There is no need to restart the device, but you should exit the Chrome browser once after associating the configuration profile.
If a particular extension ID is blocklisted, ensure that you remove the extension ID from the blocklist or else the extension will not be installed.
Don't have an account? Sign up
