Deploying Amplify to multiple devices

This documentation references external sources. Nexthink does not have control over the accuracy of third-party documentation, nor any external updates or changes that might create inconsistencies with the information presented on this page. Please report any errors or inconsistencies to Nexthink Support.

Nexthink Amplify relies on a browser extension available for Google Chrome and Microsoft Edge.

The Nexthink browser extension is available in the Chrome Web Store and Edge store.

• Download the extension from Nexthink Amplify - Chrome Web Store with bmpbcphgifhfkfjioddeenggdpffbgek as the extension ID.
• Download the extension from Nexthink Amplify - Microsoft Edge Addons with kcidkikoejfejnfmbmhmfkncdlopflhe as the extension ID.

Deploying the Amplify browser extension

Deployment considerations

• Deployment pace varies and depends on the release process of your organization.
• Any change in hardware or software precedes the implementation of the browser extension by a proof of concept and testing phase. This should be done on a limited number of endpoints.
• Use Group Policy Object (GPO) on Microsoft Windows to deploy the browser extension on selected target devices if this is the standard way of managing browser extensions in your organization.

  • Ensure that the Nexthink browser extension is a part of the organization’s browser policy, which enforces the extension.
• Use a mobile device management (MDM) solution to deploy the browser extension on managed macOS devices.

  • Chrome and Edge only apply the policy on macOS when it is delivered as a managed preference through MDM.
• Before deploying the Amplify browser extension, ensure that you do not have existing browser extensions set at the current or higher user level; otherwise, the system might uninstall them.

  • Check your existing policies on a device, by typing chrome://policy in the Chrome address bar.
  • Check your existing policies on a device, by typing edge://policy in the Edge address bar.

Before rolling out the extension to all target users, Nexthink strongly recommends educating those target users on how to use the extension.

Deployment policies

Your IT department can deploy the browser extension using a GPO or policy profile.

If the extension is not deployed through GPOs on Windows, verify that no existing policy can remove the extension.

For more information about policy management, refer to your browser documentation:

• Understand Chrome policy management
• Configure Microsoft Edge policy settings on Windows

Deployment from Chrome store

To deploy the Amplify browser extension for Google Chrome, add the Nexthink Amplify Chrome browser extension ID to the Chrome browser's Extension Install Force list GPO.

Here is an example of a registry key pushed by GPO for the Chrome browser:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\ExtensionInstallForcelist]
"1"="bmpbcphgifhfkfjioddeenggdpffbgek;https://clients2.google.com/service/update2/crx"

Force the browser extension pinned state

For managed Chrome browsers on Windows and macOS, you can pin the extension to the toolbar by default, making it easier to locate and use Amplify.

Adjust the toolbar_pin setting of the ExtensionSettings policy to force the browser extension pinned state.

Refer to the Chrome support website for more information.

Deployment from Edge store

To deploy the Nexthink browser extension for Microsoft Edge, add the Nexthink Applications Edge browser extension ID to the Extension Install Force list GPO of the Edge browser.

Here is an example of a registry key pushed by GPO for the Edge browser:

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\ExtensionInstallForcelist]
"1"="kcidkikoejfejnfmbmhmfkncdlopflhe"

Deploying Nexthink instance configuration via Registry for Amplify users

Google Chrome Extension

To deploy the Nexthink instance configuration to multiple devices:

1. Create the folder structure \bmpbcphgifhfkfjioddeenggdpffbgek\policy under the registry path HKLM\Software\Policies\Google\Chrome\3rdparty\extensions\
2. Add the Nexthink instance details by creating a registry key and values in the \policy folder as described below:

   • Name: tenants
   • Type: REG_SZ
   • Value: Enter your Nexthink instance details in the following format:

     • [{"uuid":"[unique-identifier]","name":"customer-A","url":"https://myorganization.nexthink.cloud"}]
3. In the browser properties, set up the registry value for:

• A local machine, if one or more users with the same role use the device: HKLM\Software\Policies\..\3rdparty\extensions\bmpbcphgifhfkfjioddeenggdpffbgek\policy
• A current and local user, if different users with different roles use the device: HKCU\Software\Policies\..\3rdparty\extensions\bmpbcphgifhfkfjioddeenggdpffbgek\policy

Microsoft Edge Extension

1. Create the folder structure \kcidkikoejfejnfmbmhmfkncdlopflhe\policy under the registry path HKLM\Software\Policies\Microsoft\Edge\3rdparty\extensions\
2. Add the Nexthink instance details by creating a registry key and values in the \policy folder as described below:

   • Name: tenants
   • Type: REG_SZ
   • Value: Enter your Nexthink instance details in the following format:

     • [{"uuid":"[unique-identifier]","name":"customer-A","url":"https://myorganization.nexthink.cloud"}]
3. In the browser properties, set up the registry value for:

   • A local machine, if one or more users with the same role use the device: HKLM\Software\Policies\..\3rdparty\extensions\kcidkikoejfejnfmbmhmfkncdlopflhe\policy
   • A current and local user, if different users with different roles use the device: HKCU\Software\Policies\..\3rdparty\extensions\kcidkikoejfejnfmbmhmfkncdlopflhe\policy

Deploying Amplify on managed macOS devices

Nexthink Amplify supports deployment on managed macOS devices for Google Chrome and Microsoft Edge through browser managed policies.

Deploying Amplify on macOS requires two policies per browser:

• Force-install policy: installs the extension from the browser's official store and prevents Amplify users from removing it.
• Managed configuration policy: delivers the tenants list — each entry's uuid, name, and url — to the extension through the browser's managed storage (chrome.storage.managed).

Extension details

Detail	Chrome	Edge
Extension ID	bmpbcphgifhfkfjioddeenggdpffbgek	kcidkikoejfejnfmbmhmfkncdlopflhe
Store update URL	https://clients2.google.com/service/update2/crx	https://edge.microsoft.com/extensionwebstorebase/v1/crx
Force-install preference domain	com.google.Chrome	com.microsoft.Edge
Managed configuration preference domain	com.google.Chrome.extensions.bmpbcphgifhfkfjioddeenggdpffbgek	com.microsoft.Edge.extensions.kcidkikoejfejnfmbmhmfkncdlopflhe
Configured setting	tenants — array of {uuid, name, url} entries	tenants — array of {uuid, name, url} entries

Deploy the force-install policy

Add the following keys to the force-install preference domain for each browser.

Chrome — com.google.Chrome.plist

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>ExtensionSettings</key>
    <dict>
        <key>bmpbcphgifhfkfjioddeenggdpffbgek</key>
        <dict>
            <key>installation_mode</key>
            <string>force_installed</string>
            <key>update_url</key>
            <string>https://clients2.google.com/service/update2/crx</string>
        </dict>
    </dict>
</dict>
</plist>

Edge — com.microsoft.Edge.plist

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>ExtensionSettings</key>
    <dict>
        <key>kcidkikoejfejnfmbmhmfkncdlopflhe</key>
        <dict>
            <key>installation_mode</key>
            <string>force_installed</string>
            <key>update_url</key>
            <string>https://edge.microsoft.com/extensionwebstorebase/v1/crx</string>
        </dict>
    </dict>
</dict>
</plist>

You can also force the extension's pinned state on managed macOS devices by adjusting the toolbar_pin setting of the same ExtensionSettings policy.

Deploy the managed configuration policy

Add the tenants key to the managed configuration preference domain for each browser. Each entry configures one Nexthink instance.

Chrome — com.google.Chrome.extensions.bmpbcphgifhfkfjioddeenggdpffbgek.plist

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>tenants</key>
    <array>
        <dict>
            <key>uuid</key>
            <string>[UNIQUE-IDENTIFIER]</string>
            <key>name</key>
            <string>[CUSTOMER-NAME]</string>
            <key>url</key>
            <string>https://<YOUR-NEXTHINK-INSTANCE>.nexthink.cloud</string>
        </dict>
    </array>
</dict>
</plist>

Edge — com.microsoft.Edge.extensions.kcidkikoejfejnfmbmhmfkncdlopflhe.plist

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>tenants</key>
    <array>
        <dict>
            <key>uuid</key>
            <string>[UNIQUE-IDENTIFIER]</string>
            <key>name</key>
            <string>[CUSTOMER-NAME]</string>
            <key>url</key>
            <string>https://<YOUR-NEXTHINK-INSTANCE>.nexthink.cloud</string>
        </dict>
    </array>
</dict>
</plist>

Replace [UNIQUE-IDENTIFIER] with a unique identifier (UUID) for the tenant, [CUSTOMER-NAME] with the customer or tenant display name, and <YOUR-NEXTHINK-INSTANCE> (including the angle brackets) with the actual Nexthink instance name, for example https://mycompany.eu.nexthink.cloud. To configure multiple tenants, add another <dict> entry inside the tenants array.

Verify the file with plutil -lint <file> after editing. It is not valid until you replace the placeholders.

Deployment options

On macOS, Chrome and Edge only honor ExtensionSettings and the extension's managed configuration when the policy is delivered as a managed preference through MDM.

Each option below deploys the same four preference domains, where the domain name matches the plist filename minus .plist:

Preference domain	Purpose
com.google.Chrome	Chrome force-install
com.google.Chrome.extensions.bmpbcphgifhfkfjioddeenggdpffbgek	Chrome managed configuration (tenants)
com.microsoft.Edge	Edge force-install
com.microsoft.Edge.extensions.kcidkikoejfejnfmbmhmfkncdlopflhe	Edge managed configuration (tenants)

Before deploying, replace all placeholders in the managed configuration plists and validate every file with plutil -lint <file>.

Deploy using a generic MDM

Any MDM that supports custom configuration profiles or custom preference payloads can deploy these plists:

1. Create a custom settings payload for each preference domain listed in the table.
2. Upload or paste the corresponding plist content as the payload value.
3. Scope the profiles to the target device group and deploy them at the device level, not the user level.

If you already manage other Chrome or Edge policies from the same MDM, merge the ExtensionSettings key into the existing com.google.Chrome or com.microsoft.Edge payload instead of creating a second profile for the same domain. Two profiles managing the same domain can overwrite each other.

Deploy using Jamf Pro

1. Go to Computers → Configuration Profiles → New.
2. Enter a name, for example "Nexthink Browser Extension," and leave the level at Computer Level.
3. Add an Application & Custom Settings payload with Upload as the source.
4. Enter the Preference Domain, for example com.google.Chrome, and upload the matching plist file.
5. Repeat steps 3–4 for each of the four preference domains. They can all live in the same configuration profile.
6. On the Scope tab, select the target computers or smart groups, then click Save.

Deploy using Microsoft Intune

1. Go to Devices → macOS → Configuration profiles → Create profile.
2. Select Templates → Preference file.
3. Enter the Preference domain name, for example com.google.Chrome, and upload the matching plist file.
4. Assign the profile to the target device group.
5. Repeat for each of the four preference domains. Intune allows one preference domain per profile, so this results in four profiles.

Verify the deployment

On a target device:

1. Open chrome://policy (or edge://policy) and click Reload policies. ExtensionSettings appears in the list, and the tenants configuration appears under the extension's policy section on the same page.
2. Open chrome://extensions (or edge://extensions). The extension appears, marked Installed by your administrator, with no option to remove it.

Exporting the configuration details from the Amplify extension

After configuring Amplify to integrate web applications for multiple instances, from the Amplify extension:

1. Download configuration to export the configuration details in .reg registry file.
2. Deploy the web application configurations to the target Amplify user devices via Registry.

   • The configuration file contains individual files for HKLM and HKCU settings for Google Chrome and Microsoft Edge respectively.

Deployment considerations:

• The Amplify extension does not pull the central configuration from Nexthink for configured multi-instances.
• Registry values update configured web applications locally if present, preventing any configuration edits from within the Amplify extension.
• Invalid syntax values in the registry do not update web application configurations.

Refer to the Deploying Nexthink instance configuration via Registry for Amplify users section on this page.

Deploying configuration details on Amplify user devices - Registry path (Google Chrome Extension on Google Chrome browser)

Local machine:

HKLM\SOFTWARE\Policies\Google\Chrome\3rdparty\extensions\bmpbcphgifhfkfjioddeenggdpffbgek\policy

OR

Current user:

HKCU\SOFTWARE\Policies\Google\Chrome\3rdparty\extensions\bmpbcphgifhfkfjioddeenggdpffbgek\policy

Deploying configuration details on Amplify user devices - Registry path (Google Chrome Extension on Microsoft Edge browser)

Local machine:

HKLM\SOFTWARE\Policies\Microsoft\Edge\3rdparty\extensions\bmpbcphgifhfkfjioddeenggdpffbgek\policy

OR

Current user:

HKCU\SOFTWARE\Policies\Microsoft\Edge\3rdparty\extensions\bmpbcphgifhfkfjioddeenggdpffbgek\policy

Deploying configuration details on Amplify user devices - Registry path (Microsoft Edge Extension)

Local machine:

HKLM\SOFTWARE\Policies\Microsoft\Edge\3rdparty\extensions\kcidkikoejfejnfmbmhmfkncdlopflhe\policy

OR

Current user:

HKCU\SOFTWARE\Policies\Microsoft\Edge\3rdparty\extensions\kcidkikoejfejnfmbmhmfkncdlopflhe\policy