uberAgent

Installing the Edge Browser Extension

July 9, 2024

Contributed by:

uberAgent’s browser web app performance functionality requires a browser extension to be installed. This article lists the necessary steps.

Enabling the Agent Metric

To enable data collection from Edge make sure uberAgent’s BrowserPerformanceEdge metric is enabled in the configuration. In the default configuration, BrowserPerformanceEdge is enabled.

Installing the Edge Extension

The extension is available from the Chrome Web Store from two different channels: release and beta. The release channel gets only fully-tested versions of the extension, while the beta channel additionally gets beta-quality versions.

We recommend putting the majority of users on the release channel and a small minority on the beta channel.

Manual Installation

For tests and PoCs, it may be easiest to install uberAgent’s Edge extension manually from the Chrome Web Store. Please note that you need to allow extensions from other stores.

Release Channel

Install the extension from release channel on the Chrome Web Store.

Beta Channel

Install the extension from beta channel on the Chrome Web Store.

Automated Deployment

Deployment of uberAgent’s Edge extension is easily possible with Group Policy. Follow the steps in the Edge documentation to configure the ExtensionInstallForcelist setting. Extensions on the ExtensionInstallForcelist will also get installed if the Edge setting Allow extensions from other stores is not enabled.

To configure Edge to install the uberAgent extension from the standard Chrome Web Store update URL add the following to the ExtensionInstallForcelist setting:

Release Channel

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

Beta Channel

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

Offline Deployment

If your endpoints are not connected to the Internet and can’t access Chrome’s Web Store, you can also pre-install the extensions. Please contact us for the CRX file or use an online CRX extractor.

Note that using the offline deployment you need to push updated CRX files manually.

Relevant Configuration Settings

Native Messaging

uberAgent’s Edge extension uses native messaging to communicate with the agent. In a default configuration of Edge, native messaging is not restricted.

If native messaging has been restricted, for example via the NativeMessagingBlocklist Group Policy setting, an exception needs to be defined for the uberAgent extension, for example via the NativeMessagingAllowlist Group Policy setting.

The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.

Was this helpful

Installing the Edge Browser Extension

July 9, 2024

Contributed by:

July 9, 2024

Contributed by:

Installing the Edge Browser Extension

Enabling the Agent Metric

Installing the Edge Extension

Manual Installation

Release Channel

Beta Channel

Automated Deployment

Release Channel

Beta Channel

Offline Deployment

Relevant Configuration Settings

Native Messaging

In this article