Configure Chromium based Browser Extensions
When defining Web applications. You first have to ensure that the Agents are configured to measure these.
There are two options for making these measurements available. either through Agent configuration. This generates some Local Machine policy. Or through local or Domain User policy.
Extension types
Section titled “Extension types”There are two different Extensions type for these measurements.
- leifiaolndnnmnkhmhibkejddgcfbfjf
- gelgkjhdkdehhjeokbbkdplgkmhffnmc
Info:
1: Totally silent
2: Shows measured time. on extension Icon.
Configure through Agent configuration
Section titled “Configure through Agent configuration”When configuring from the Agent configuration page. You should be aware of the two options.
Network Report
Enable Chrome/Edge Extension as Local Machine Policy (Can also be enabled as User Machine Policy using Group Policy)
User Interface
Enable Chrome Extension Details
When only selecting Network Report. The Agent will install Type 1 of Extension (Silent).
If you also chose User-interface. The Agent will install Type 2 of Extension (With info).
When you select this option. The agent will generate some Browser policies. And some references to the messaging module. These settings are stored as Local machine policy and settings.
Configure through User Policy
Section titled “Configure through User Policy”When configuring as a User policy. You need to set the following policy options:
Google Chrome
Section titled “Google Chrome”Extension:
User Configuration → Policies → Administrative Templates → Google → Google Chrome → Extensions → Configure the list of force-installed apps and extensions
Insert the following entry:
“Type of Extension (1 or 2)“;https://clients2.google.com/service/update2/crx
Ex.
install the silent extension.
leifiaolndnnmnkhmhibkejddgcfbfjf;https://clients2.google.com/service/update2/crx
The connector between Browser and Performanceguard Agent (Native messaging)
Currently, there is no option for setting default values for Native messaging. So you have to create this registry Manually.
Create a registry key
HKEY_CURRENT_USER\SOFTWARE\Google\Chrome\NativeMessagingHosts\com.capasystems.performance
Where you set the default value to:
C:\Program Files\PerformanceGuard\Agent\chromeHost\com.capasystems.performance.json
Microsoft Edge Chromium
Section titled “Microsoft Edge Chromium”Extension:
User Configuration → Policies → Administrative Templates → Microsoft Edge → Extensions → Control which extensions are installed silently
Insert the following entry:
“Type of Extension (1 or 2)“;https://clients2.google.com/service/update2/crx
Ex.
install the silent extension.
leifiaolndnnmnkhmhibkejddgcfbfjf;https://clients2.google.com/service/update2/crx
The connector between Browser and Performanceguard Agent (Native messaging)
Currently, there is no option for setting default values for Native messaging. So you have to create this registry Manually. Microsoft Edge uses the Native messaging list from Google Chrome. If this is not specified in Edge.
Create a registry key
HKEY_CURRENT_USER\SOFTWARE\Google\Chrome\NativeMessagingHosts\com.capasystems.performance
Where you set the default value to:
C:\Program Files\PerformanceGuard\Agent\chromeHost\com.capasystems.performance.json
Verification of Settings
Section titled “Verification of Settings”Look in the registry on the client computer for the following keys, and check their values according to your configuration.
When using Agent configuration:
HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome\ExtensionInstallForcelist
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Edge\ExtensionInstallForcelist
HKEY_LOCAL_MACHINE\Software\Google\Chrome\NativeMessagingHosts\com.capasystems.performance
When using User policy:
HKEY_CURRENT_USER\Software\Policies\Google\Chrome\ExtensionInstallForcelist
HKEY_CURRENT_USER\Software\Policies\Microsoft\Edge\ExtensionInstallForcelist
HKEY_CURRENT_USER\Software\Google\Chrome\NativeMessagingHosts\com.capasystems.performance
Ex. policy definition with browser locked down
We’ve encountered an issue exporting this macro. Please try exporting again later.