Before you begin

It is possible that your organization already has policies in place to manage Google Chrome and/or Microsoft Edge browsers. If this is the case, please ensure with the responsible team that the policies are applied in the correct order and that the policies for the eCDN for Google Meet extension are not overwritten by another policy.


Rolling out the eCDN for Google Meet extension

Microsoft Windows

Google Chrome

Option 1, using Google Admin

Follow this link to open the “Apps & extensions“ for Google Chrome browsers on Google Admin.

Add a new extension by clicking the “+” icon. You can add the extension by ID (peilhdmcabagpieoagpaacnfpldpacij) or you can add its URL from the Chrome Web Store. For the installation policy, we recommend using “Force Install”.

In the “Policy for extensions” section, add the following:

{ "DeploymentScriptURL": {"Value": "https://cdn.strivetech.io/services/storage/v0/entity-resource/<YOUR-ACCOUNT-ID>/<YOUR-DEPLOYMENT-ID>/gwc.min.js"}}
JSON

You need to replace <YOUR_ACCOUNT_ID> and <YOUR_DEPLOYMENT_ID> with the actual values from our Portal. If you are not sure what your IDs are, please contact us by opening a ticket in the StriveCast Help Desk. We will support you to get this information.

This method also works for macOS, Linux and ChromeOS systems.


Option 2, using an Active Directory Group Policy Object
Option a), using the Administrative Templates for Google Chrome and Windows Registry settings

First, please make sure that you have the Active Directory policy templates for Google Chrome available on your Domain Controller.

Then, create a new Group Policy Object (GPO) or edit your already existing one for Google Chrome browsers.

The following needs to be added to this GPO:

In the Group Policy editor, under “Policies”, choose the following from the administrative templates.

Select this template and add the eCDN extension to the list of force-installed extensions:

Google → Google Chrome → Extensions → Configure the list of force-installed apps and extensions

Enable the policy and set the following value in its options:

peilhdmcabagpieoagpaacnfpldpacij;https://clients2.google.com/service/update2/crx

Now, the configuration for the extension needs to be created. This requires setting a new key in the Windows Registry. For this, select Windows Settings → Registry from the Preferences menu item and create a new Registry Item with the following properties:

Hive: HKEY_CURRENT_USER

Key Path:Software\Policies\Google\Chrome\3rdparty\extensions\peilhdmcabagpieoagpaacnfpldpacij\policy

Value Name: DeploymentScriptURL

Value Type: REG_SZ

Value Data: https://cdn.strivetech.io/services/storage/v0/entity-resource/<YOUR-ACCOUNT-ID>/<YOUR-DEPLOYMENT-ID>/gwc.min.js

You need to replace <YOUR_ACCOUNT_ID> and <YOUR_DEPLOYMENT_ID> with the actual values from our Portal. If you are not sure what your IDs are, please contact us by opening a ticket at the StriveCast Help Desk. We will support you to get this information.

Here you can find an example how the configuration should look like in the end:

To verify your GPO, you can compare it with this example:

Option b), using Windows Registry settings only

If you don’t have the Active Directory policy templates for Google Chrome available, you can also set all required properties with Windows Registry keys.

To do this, go to Preferences → Windows Settings → Registry in the Active Directory Group Policy editor.

You need to create two new keys:

Force-install the extension:

Hive: HKEY_CURRENT_USER

Key Path: Software\Policies\Google\Chrome\ExtensionInstallForcelist

Value Name: 1

Value Type: REG_SZ

Value Data: peilhdmcabagpieoagpaacnfpldpacij;https://clients2.google.com/service/update2/crx

Configure the extension:

Hive: HKEY_CURRENT_USER

Key Path:Software\Policies\Google\Chrome\3rdparty\extensions\peilhdmcabagpieoagpaacnfpldpacij\policy

Value Name: DeploymentScriptURL

Value Type: REG_SZ

Value Data: https://cdn.strivetech.io/services/storage/v0/entity-resource/<YOUR-ACCOUNT-ID>/<YOUR-DEPLOYMENT-ID>/gwc.min.js

You need to replace <YOUR_ACCOUNT_ID> and <YOUR_DEPLOYMENT_ID> with the actual values from our Portal. If you are not sure what your IDs are, please contact us by opening a ticket at the StriveCast Help Desk. We will support you to get this information.

To verify your GPO, you can compare it with this example:

If your active policies are based on devices instead of users, you can also use the Hive HKEY_CURRENT_MACHINE for the Registry settings.


Contact us

For any further questions or problems, please open a ticket at the StriveCast Help Center.