Browser extension deployment on Windows

This page explains how to distribute Admina Extension to Google Chrome or Microsoft Edge on Windows devices. It also covers linking the extension to your Admina organization. You can choose from three installation methods depending on your environment: manual, GPO, or Microsoft Intune.

​

Prerequisites

• Devices run Windows 10 or later
• Google Chrome or Microsoft Edge is installed

If you restrict outbound destinations, review the network requirements in About Admina Extension. Prerequisites for each distribution method (permissions and management tools) are listed on each method’s page.

​

Configuration goals

When you deploy to Windows devices, configure the following three items.

1. Write install directives to HKLM → the extension installs automatically
2. Write organization and user parameters to HKCU → the extension runs linked to your organization
3. Use a logon script to set USEREMAIL at sign-in → step 2’s UserEmail is filled automatically

How you write these values depends on the distribution method. Each method’s page walks through the steps for that method. When all three are in place, the extension becomes active without action from the user. The delivery channel (GPO, Intune, scripts, and so on) does not matter. After configuration, you should see the following.

• When the user starts the browser, the extension installs automatically and the user cannot disable or remove it
• The extension reads HKCU parameters and runs linked to the organization, user, and device

​

Configuration items

This section summarizes the registry values and environment variables you ultimately set on client devices. It applies regardless of distribution method (manual, GPO, Intune, and so on). For delivery steps, see each method’s page. The values here follow common behavior on Windows, Google Chrome, and Microsoft Edge. You can set the same values with your own scripts or asset management tools, not only the methods on each method’s page.

​

Install directive (HKLM)

Set a force-install directive for the extension in the machine registry (HKLM).

If you cannot write to ExtensionSettings (use ExtensionInstallForcelist)

If asset management software already manages ExtensionSettings, you may not be able to write there. Examples include SKYSEA Client View and LANSCOPE. Use ExtensionInstallForcelist instead. Either approach is enough. Choose the other if another product already uses the same mechanism and you see a conflict.

Browser	Key	Type	Data
Chrome	HKLM\Software\Policies\Google\Chrome\ExtensionInstallForcelist	REG_SZ	bdeanmdeckegmfjpbnngomallcedjold;https://clients2.google.com/service/update2/crx
Edge	HKLM\Software\Policies\Microsoft\Edge\ExtensionInstallForcelist	REG_SZ	flggmhlpipcopffjfkpgkoljghfkmfcg;https://edge.microsoft.com/extensionwebstorebase/v1/crx

Value names are sequential numbers. Use the next free number (often 1 if none exist yet).With this approach, you still need Extension parameters (HKCU) and User email address (logon script). If your asset management tool can deploy extensions, you may register the same values there.For how conflicts work and how to verify them, see Browser extension policy conflicts and workarounds.

​

Extension parameters (HKCU)

Set parameters in the user registry (HKCU) so the extension can identify your Admina organization and users. Registry keys differ by browser.

• Chrome: HKCU\Software\Policies\Google\Chrome\3rdparty\extensions\bdeanmdeckegmfjpbnngomallcedjold\policy
• Edge: HKCU\Software\Policies\Microsoft\Edge\3rdparty\extensions\flggmhlpipcopffjfkpgkoljghfkmfcg\policy

For both browsers, set the following values under those keys. By default, set UserEmail (%USEREMAIL%) and UserPC (%COMPUTERNAME%) to reference environment variables. For manual setup on devices and users you already know, you may use fixed values instead of variables. For standard bulk deployment, keep the variables.

​

User email address (logon script)

Set the signed-in user’s email address in the user environment variable USEREMAIL. How you set USEREMAIL at logon depends on the distribution method. For how to distribute the scripts, see the page for each method. The scripts are samples. Change how you obtain email addresses to match your environment. Examples include Active Directory attributes, Microsoft Entra ID, and fixed lists. If you set UserEmail to %USEREMAIL% but USEREMAIL is not set, the extension cannot identify the user. It will not link to your organization. When you use %USEREMAIL%, always deploy a logon script as well.

​

Choose an installation method

If deployment settings reach devices but the extension does not install, see the workaround guide. See Browser extension policy conflicts and workarounds.

​

Technical notes and FAQ

For HKLM, HKCU, policy conflicts, and permissions, see Browser extension technical notes and FAQ for Windows. That page lists common questions for all distribution methods.