Installing Web Threat Shield Chrome Browser Extensions
Webroot follows Google and the Chromium Projects best practice concerning Browser Extension deployment. Webroot therefore cannot deploy Browser Extensions without notifying end users. Partners wishing to install Chrome browser extensions silently in managed environments may do so using the following methods for enforced installation.
Enforced installation of the Chrome extension for Enhanced Web Threat Shield (EWTS) for Webroot SecureAnywhere in managed environments can be achieved easily. Enforced installation will not prompt the user to activate or accept the extension, and also prevents the user from disabling it.
In a non-enforced environment, the user will be prompted to enable the extension for Chrome as depicted the following image.
A non-enforced extension can, by design, be enabled, disabled or removed by the user via chrome://extensions/ as shown in the following image.
Chrome extensions, which are deployed silently in managed environments, are marked as shown in the following image. The user in this scenario cannot disable or remove the extension himself, this is controlled by the administrator. Note that there will not be any user prompts for enabling the extension.
Using Active Directory Group Policies
Google provides administrative templates for Windows Server 2003 (ADM template) and Windows Server 2008+ (ADMX template) which, once imported, will provide Chrome specific policies for Group Policies.
Required administrative templates can be downloaded from Google via below link:
To create a forced installation of Chrome browser extensions via Active Directory Group Policies:
- Open the Group Policy Management console. Right click your domain and select Create and Link a GPO here.
- Name your new GPO; in this example it is called Chrome Enforced Policy.
- Right click your new GPO and select Edit. You should get a new window as shown below.
- Expand the Computer Configuration.
- Right click Administrative Templates.
- Click Add/Remove Templates.
- Click Add.
- Point to the ADM or ADMX file from the Google Chrome templates archive you downloaded.
- Click Open and then click Close.
You should now see Google as an additional folder inside the Administrative Templates.
- Inside the Administrative Templates, expand Google\Google Chrome\Extensions.
- Click Configure the list of force-installed extensions.
- Click Enable.
- Click Show.
- Add the line of text below to the list of Extension/App IDs and update URLs to be silently installed.
- Confirm all dialogs/buttons.
This will install the Webroot EWTS extension for Chrome on any domain computer that this policy applies to.
Using Google Suite to Force Install a Single Custom App
Enforced installation of the Chrome extension for EWTS is supported on Google Suite managed environments. General directions for installing extensions and applications can be found in Google Help.
To install the Chrome extension for the EWTS you will need to add a Custom App using the following steps.
To install the Chrome extension:
- Sign in to the Google Admin console.
- From the Admin console dashboard, click Device management.
- On the left, click Chrome management.
- Click App management.
- On the right, click the three dots to bring up the overflow menu.
- Select Add custom app.
- In the custom app dialog, enter the ID:
- Enter the following
for Webroot Filtering Extension.
- Click Add.
- From the App Management screen select the newly added extension identified by the ID.
- From the app options, select User Settings.
- Select the relevant Org you wish to install the Chrome extension for EWTS into and turn Allow installation and Force installation ON.
- Click Save.
Users logging into Chrome using their credentials for the chosen Org will now receive the Webroot Filtering Extension in their Chrome browser. Please refer to the G Suite documentation from Google regarding Org structures and advanced options for managing applications.
Note: At this time we do not support Webroot SecureAnywhere on Chromebooks. In order to avoid a poor experience for users running on these devices you will need to utilize policy control within G Suite, please refer to the G Suite help documentation for more information.
If using Active Directory or Google Suite are not suitable, using the Windows Registry might be an alternative to silently install the Chrome extension for the EWTS. Note that this option requires the computers to be part of a Microsoft Windows Domain.
Note: Using this method might conflict with Active Directory Group Policies or G Suite managed environments.
Details about available policy settings for Chrome can be found at:
Use the Windows Registry Editor (regedit.exe) to:
- Check whether the Registry key listed below exists.
Existence of this key may indicate that other management applications are enforcing Chrome policies, specifically forced installation of extensions, which can cause conflicts if below steps are continued.
- Add the following Registry value:
Windows Registry Editor Version 5.00
If you want to register additional extensions, please ensure continuous numbering.