Deploy Browser Extension via GPO

Learn how to deploy the Kabeen browser extension using Microsoft GPO

In this article, you will learn how to deploy the Kabeen extension on Microsoft Edge, Google Chrome, or Mozilla Firefox browsers using GPO (Group Policy Objects) in a Microsoft Active Directory environment.

The browser extension works in synergy with the Kabeen agent (native application), so it must also be installed on the workstation to track web application usage.

Step 1: Create the GPO

  1. Log in to your domain administration workstation or directly on the domain controller
  2. Click Start, go to Administrative Tools and select Group Policy Management
  3. Right-click on your domain name and select Create a GPO in this domain
  4. In the new GPO window, enter a descriptive name

Step 2: Install Administration Template

On some domain controllers, you will need to deploy the administration templates (ADMX) for the browsers:

Step 3: Automatic Extension Installation

Microsoft Edge

  1. From User Configuration > Policies > Administrative Templates > Microsoft > Microsoft Edge > Extensions
  2. Edit Control which extensions are installed silently
  3. Select Enabled
  4. Click Show and paste the value jgdflahjneomipldehpneckiplknghbc

Google Chrome

  1. From User Configuration > Policies > Administrative Templates > Google > Google Chrome > Extensions
  2. Edit Configure the list of force-installed apps and extensions
  3. Select Enabled
  4. Click Show and paste the value hkmgmmaopoofgchofbngplopnhajbojc

Mozilla Firefox

  1. From User Configuration > Policies > Administrative Templates > Mozilla > Firefox > Extensions
  2. Edit Extensions to Install
  3. Select Enabled
  4. Click Show and paste the URL https://addons.mozilla.org/firefox/downloads/latest/kabeen/latest.xpi

For Firefox, to prevent users from disabling the extension, also enter the URL in Prevent extensions from being disabled or removed.

Configuration without the native agent (registry keys)

The extension normally retrieves the user's connection code and organization from the Kabeen native agent installed on the workstation. When the agent is not deployed, you can still authenticate and pre-configure the extension through the browser's managed storage, which on Windows is populated via registry keys.

Three values must be set, grouped under an Authentication subkey:

ValueTypeDescription
ApiTokenREG_SZWorkspace connection code, available in the Settings > Rover Management menu
StructureIdREG_SZIdentifier of the structure (subsidiary) the user belongs to
TeamIdREG_SZIdentifier of the business service (team) the user belongs to

Microsoft Edge

Create the following subkey (extension ID: jgdflahjneomipldehpneckiplknghbc), then add the three values:

HKLM\SOFTWARE\Policies\Microsoft\Edge\3rdparty\extensions\jgdflahjneomipldehpneckiplknghbc\policy\Authentication

Google Chrome

Create the following subkey (extension ID: hkmgmmaopoofgchofbngplopnhajbojc), then add the three values:

HKLM\SOFTWARE\Policies\Google\Chrome\3rdparty\extensions\hkmgmmaopoofgchofbngplopnhajbojc\policy\Authentication

Through a GPO, these values are deployed from Computer Configuration > Preferences > Windows Settings > Registry. The HKLM hive applies to all users of the workstation; use HKCU for a per-user configuration.

The StructureId and TeamId identifiers correspond to the structures (subsidiaries) and business services (teams) modeled in Kabeen's Organization view. Configured this way, the extension is authenticated and attached to the organization silently, without any user action.

PreviousDeploy User Agent via GPONextDeploy User Agent via Intune