Deploying the extension is best done using your existing endpoint management tools:
- If you use Google Workspace there's a quick way to just deploy the extension to users logged in to Chrome with their work email address. Be careful about combining these methods as setting force install policies for Chrome as described in this article will override other extensions deployed using the Google Workspace admin console.
- If you deploy the Windows Browser Helper this will force deploy the extension.
- For macOS we recommend reading our detailed macOS MDM deployment guide.
This article acts as a reference for alternative approaches for deploying and troubleshooting just the browser extension (not the Browser helper) on Windows and macOS.
Windows - Group Policies
Group Policy Objects are typically configured for Windows machines on Active Directory.
Chrome
- Read the Google documentation on setting up the
admxandadmlfiles for Chrome. - In the Group Policy Editor, go to Google > Google Chrome > Extensions > Configure the list of force-installed apps and extensions
- Select Enabled
- Click Show
- Enter the ID
igjpcenkahclnlkcldhphacgmfilbefd
Edge
- Read the Microsoft documentation on setting up the
admxandadmlfiles for Edge. - In the Group Policy Editor, go to Administrative Templates > Microsoft Edge > Extensions and then select Control which extensions are installed silently.
- Select Enabled.
- Click Show.
- Enter the ID
alhagkkmlflbnlckfifmlemhcmaaflon
Firefox
- Download the Firefox policies from https://github.com/mozilla/policy-templates/releases
- Extract the Zip and find the
firefox.admxfile (underpolicy_templates_vX.X\windows) and the language specificfirefox.admlfile (under the respective language sub-folder, e.g.en-US). - Deploy the
admxandadmlfiles. - In the Group Policy Editor, go to Administrative Templates > Firefox > Extensions then Right click and Edit Extension Management.
- Select Enabled.
- Click Show.
- Cut and paste the following JSON:
{
"browserextension@trelica.com": {
"installation_mode": "force_installed",
"install_url": "https://addons.mozilla.org/firefox/downloads/latest/trelica/latest.xpi"
}
}Windows - Setting the Registry
Group Policies effectively set registry keys to force-install Edge, Chrome and Firefox.
For Chrome and Edge, the registry values are effectively a list, where the name is a numerical sequence. If you already have values set, then you should choose the next available value.
There's a PowerShell script (Set-ForceInstallBrowserExtensions.ps1) that will apply these registry settings for HKEY_CURRENT_USER for Chrome, Edge and Firefox here:
Chrome
HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome\ExtensionInstallForcelist| Name | Type | Data |
|---|---|---|
1 (or next number in the sequence) |
String (REG_SZ) | igjpcenkahclnlkcldhphacgmfilbefd |
Edge
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Edge\ExtensionInstallForcelist| Name | Type | Data |
|---|---|---|
1 (or next number in the sequence) |
String (REG_SZ) | alhagkkmlflbnlckfifmlemhcmaaflon |
Firefox
HKEY_LOCAL_MACHINE\Software\Policies\Mozilla\Firefox| Name | Type |
|---|---|
ExtensionSettings |
Multi-String Value (REG_MULTI_SZ) |
| |
Windows - Intune
Chrome and Edge
- Go to Devices > Configuration profiles > Create profile
- Choose the platform Windows 10 and later and the profile type Settings catalog, then click Create.
- Enter a name and description, and click Next.
- Click Add settings.
- In the Settings picker, scroll down and expand the Microsoft Edge category.
- Choose Extensions.
- Choose the Control which extensions are installed silently setting.
- Close the panel, and click Add settings again.
- Search for Chrome and select Administrative Templates\ Google\ Google Chrome\ Extensions.
- Choose Configure the list of force-installed apps and extensions setting.
- Close the panel and now Enable both of the settings you added.
- Enter the following IDs for the respective setting:
- Chrome:
igjpcenkahclnlkcldhphacgmfilbefd - Edge:
alhagkkmlflbnlckfifmlemhcmaaflon
- Chrome:
- Click Next to step through and assign any Scope tags or Assignments (e.g. Add all devices).
- Review the profile and click Create.
- The profile list doesn't always update so click Refresh to confirm the new profile has been created.
Firefox
- Go to Devices > Configuration profiles and click Create profile.
- Select the platform Windows 10 and later, and the profile type Templates.
- Select the Custom template and click Create.
- Enter a name and description, and click Next.
- Click Add to add a new OMA-URI.
- Enter a Name and Description.
- Paste in the OMA-URI:
./Device/Vendor/MSFT/Policy/Config/Firefox~Policy~firefox~Extensions/ExtensionSettings - Choose the Data Type String.
-
Paste in the following value:
<enabled/> <data id="ExtensionSettings" value=' { "browserextension@trelica.com": { "installation_mode": "force_installed", "install_url": "https://addons.mozilla.org/firefox/downloads/latest/trelica/latest.xpi" } }'/> - Click Save.
- Click Next to step through and assign any Scope tags or Assignments (e.g. Add all devices).
- Review the profile and click Create.
- Step through clicking Next to assign the profile to the appropriate devices.
macOS Profile File
Many MDMs (e.g. Kandji, SimpleMDM) can deploy macOS Profile files.
Please also read our full guide to deploying SaaS Manager to macOS with an MDM.
Signed profile: trelica-extensions.mobileconfig
macOS Property List (plist)
If your MDM requires Property List (plist) settings you can use the following:
com.google.Chrome preference domain
<?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>ExtensionInstallForcelist</key>
<array>
<string>igjpcenkahclnlkcldhphacgmfilbefd</string>
</array>
<key>NativeMessagingAllowlist</key>
<array>
<string>com.trelica.browser_helper</string>
</array>
</dict>
</plist>com.microsoft.Edge preference domain
<?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>ExtensionInstallForcelist</key>
<array>
<string>alhagkkmlflbnlckfifmlemhcmaaflon</string>
</array>
</dict>
</plist>org.mozilla.firefox preference domain
<?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>EnterprisePoliciesEnabled</key>
<true/>
<key>ExtensionSettings</key>
<dict>
<key>browserextension@trelica.com</key>
<dict>
<key>install_url</key>
<string>https://addons.mozilla.org/firefox/downloads/latest/trelica/latest.xpi</string>
<key>installation_mode</key>
<string>force_installed</string>
</dict>
</dict>
<key>ExtensionUpdate</key>
<true/>
</dict>
</plist>Troubleshooting
All the above apply browser policies.
Each browser has a specific internal page which lets you view applied policies. This is very useful for troubleshooting:
| Browser | URL | Notes |
|---|---|---|
| Chrome | chrome://policy | |
| Edge | edge://policy | |
| Firefox | about:policies | Click 'Errors' on the left to view details of issues. |
Comments
0 comments
Please sign in to leave a comment.