Category filter
Custom configuration profile to add Chrome extensions on macOS devices
Google Chrome extensions are small add-on applications and features that can be installed in Chrome to customize and enhance the browsing experience. They are essentially small programs integrated into the Google Chrome app and serve a single purpose. For example, a grammar checker extension is used to correct typos, and an ad blocker extension can remove unnecessary ads from popping up while web surfing, etc. Instead of manually adding Chrome extensions from the Chrome Web Store, the user can apply a custom configuration profile to add the extensions on macOS devices. IT admins can remotely deploy this custom configuration profile to multiple macOS devices in their organization using Hexnode’s Deploy Custom Configuration feature.
Configuration profile to add 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 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 |
<?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> |
Replace CONFIGURATION NAME
with the name you want the configuration to be called. Also replace the PLACE EXTENSION IDENTIFIER HERE
with the ID of the extension you want to add in the endpoint’s Chrome browser. To get the identifier, go to the extension in the Chrome Web Store and get it from your URL. For example, the identifier of the Google Translate extension looks like this:
What happens at the device end?
Once the policy and custom configuration are associated, click on the jigsaw icon at the top-right of the opened Chrome window to bring up the extensions manager. You can see the configured extension added to the list.