Skip to content
English
Back to IRIS Website
  • There are no suggestions because the search field is empty.

IRIS Clarity Windows Support Extension

How to deploy the IRIS Clarity Windows Support Extension for Chrome and Edge

 Path A — Chrome Web Store

Contact IRIS for the current Chrome Web Store extension ID before proceeding.

 

Step 1 A — Force-install on Chrome

Add the following registry entry on each managed machine (or push via Intune/GPO):

Key:   HKLM\SOFTWARE\Policies\Google\Chrome\ExtensionInstallForcelist Name:  1  (or any unused integer) Type:  REG_SZ Value: <iris_cws_extension_id>;https://clients2.google.com/service/update2/crx

Replace <iris_cws_extension_id> with the ID provided by IRIS.

 

Step 1 B — Force-install on Edge

Option 1 — reference the Chrome Web Store directly (try this first):

Key:   HKLM\SOFTWARE\Policies\Microsoft\Edge\ExtensionInstallForcelist Name:  1  (or any unused integer) Type:  REG_SZ Value: <iris_cws_extension_id>;https://clients2.google.com/service/update2/crx

Option 2 — use the Edge Add-ons store (if Option 1 causes issues):

Contact IRIS for the Edge Add-ons store ID, then use:

Key:   HKLM\SOFTWARE\Policies\Microsoft\Edge\ExtensionInstallForcelist Name:  1  (or any unused integer) Type:  REG_SZ Value: <iris_edge_extension_id>;https://edge.microsoft.com/extensionwebstorebase/v1/crx
 
Step 2 — Apply and verify

Push the policy via Intune or Group Policy:

  • Intune: Edge is supported natively in the settings catalog. Chrome requires the Google Chrome ADMX template (available from Google). Set each browser as a separate configuration profile.
  • Group Policy: Import the ADMX templates for Chrome and/or Edge. Set ExtensionInstallForcelist under Computer Configuration → Administrative Templates → [Browser] → Extensions.

On a test machine, open chrome://policy or edge://policy and confirm the extension ID appears in the forcelist. Then open the browser — the extension should install within a few minutes.

Updates: handled automatically by Google. No action required from your IT team.

 

Path B — Self-hosted

This path is available immediately and requires no Chrome Web Store approval. You host two files on any HTTPS server you control (examples: Azure Blob Storage, S3, SharePoint, an internal IIS or nginx server).

What you need before starting

  • The .crx file and update_manifest.xml — provided by IRIS
  • An HTTPS file host reachable from your managed machines
  • The extension ID: hoafahidigcfefnficbbajmnijpdedao
Step 1 — Host the extension files
  1. Edit update_manifest.xml (provided by IRIS). Replace the placeholder URL with the full HTTPS path where you will upload the .crx: 
    codebase="https://your-host.example.com/iris/iris-clarity-device-override-x.x.x.crx" version="x.x.x"
  2. Upload both files to your HTTPS host:
    • iris-clarity-device-override-x.x.x.crx
    • update_manifest.xml
  3. Confirm both URLs are reachable from a browser on a managed machine before continuing.
 
Step 2 — Force-install on Chrome
Key:   HKLM\SOFTWARE\Policies\Google\Chrome\ExtensionInstallForcelist Name:  1  (or any unused integer) Type:  REG_SZ Value: hoafahidigcfefnficbbajmnijpdedao;https://your-host.example.com/iris/update_manifest.xml
 
Step 3 — Force-install on Edge
Key:   HKLM\SOFTWARE\Policies\Microsoft\Edge\ExtensionInstallForcelist Name:  1  (or any unused integer) Type:  REG_SZ Value: hoafahidigcfefnficbbajmnijpdedao;https://your-host.example.com/iris/update_manifest.xml
 
Step 4 — Apply and verify

Push via Intune or Group Policy using the same steps as Path A. Verify at chrome://policy / edge://policy on a test machine.

 

Applying updates

When IRIS releases a new version, they will provide a new .crx file and the new version number. Your IT team needs to:

  1. Upload the new .crx to your HTTPS host.
  2. Edit update_manifest.xml — update version and codebase to match the new file.
  3. Re-upload update_manifest.xml.

Managed machines will pick up the update automatically within a few hours. No policy change is needed — the extension ID never changes.

 

Verifying the extension is working

On any managed machine after the policy has been applied:

  1. Open Chrome or Edge and go to chrome://policy / edge://policy. The extension ID should appear in the ExtensionInstallForcelist row.
  2. Go to chrome://extensions / edge://extensions. The IRIS Clarity Device Override extension should be listed as installed and enabled, with a "Installed by your administrator" label.
  3. Join or start any HTTPS-based VoIP call and confirm audio is routing through the IRIS device.

 

Excluding specific sites

If there is a site where users need to select their own microphone (e.g. a recording or broadcast tool), you can exclude it from the extension's rewrite via policy — no change to the extension itself is needed.

Add an ExtensionSettings policy entry for the extension ID with a runtime_blocked_hosts list:

  • Chrome: HKLM\SOFTWARE\Policies\Google\Chrome\ExtensionSettings
  • Edge: HKLM\SOFTWARE\Policies\Microsoft\Edge\ExtensionSettings

Contact IRIS with the list of domains to exclude and they can provide the exact policy value to set.

 

Getting help

For the extension files, extension IDs, or policy value assistance, contact the IRIS team. For policy deployment questions specific to your Intune or Active Directory environment, refer to your MDM documentation or internal IT resources.