This deployment method is recommended for organizations that have not deployed other extensions via GPO and/or Intune.
Lemon Learning can provide a pre-configured MSI package including your chosen authentication method. It can be deployed remotely through your management tools and installed in silent mode. This package updates three values in the registry:
The [...\ExtensionInstallAllowlist] key, which authorizes the installation of the Player extension.
The [...\ExtensionInstallForcelist] which forces the installation of the Player extension.
The [...\3rdparty\extensions\[...]\policy] key, which allows you to insert your custom configuration key.
This deployment method is recommended for organizations that already manage extensions via GPO and/or Intune and wish to minimize the risk of conflicts.
Lemon Learning can assist you with a GPO-based deployment by providing a set of three registry keys for each browser you intend to support. These keys are:
The [...\ExtensionInstallAllowlist] key, which authorizes the installation of the Player extension.
The [...\ExtensionInstallForcelist] which forces the installation of the Player extension.
The [...\3rdparty\extensions\[...]\policy] key, which allows you to insert your custom configuration key.
Lemon Learning can support you in setting up a deployment via Intune. Two approaches are available:
Once you receive the MSI package, you will need to generate an .intunewin file using the Microsoft Win32 Content Prep Tool, then add the application to Intune via the Microsoft Endpoint Manager portal.
Once the custom registry keys have been provided, you should create a Configuration Profile, configure its settings, and add the OMA-URI entries corresponding to the keys. This profile can then be assigned to the relevant users or groups.
This deployment method requires Chrome Management to be enabled in your Admin Console, and for users to be signed into Chrome using their Workspace account.
To force-install the Chrome Player via Google Workspace:
Sign in to the Admin Console.
Navigate to Devices → Chrome → Settings → Users & browsers.
Select the relevant organizational unit (OU).
Add the extension from the Chrome Web Store and select Force install.
To apply your custom configuration:
While on the extension's settings page in the console, paste the provided JSON. Ensure you use the configuration key provided by your Solutions Engineer in the "Value" field.
{
"configKey": {
"Value": "XXX"
}
}
On the user side, the installation and configuration can be verified by navigating to chrome://policy/.