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.

• 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"

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

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\ExtensionInstallForcelist]
"1"="bmpbcphgifhfkfjioddeenggdpffbgek;https://edge.microsoft.com/extensionwebstorebase/v1/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:

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

Deploying Nexthink instance configuration via Registry for Amplify users

Google Chrome

To deploy the Nexthink instance configuration to multiple devices:

1. Create the folder structure \bmpbcphgifhfkfjioddeenggdpffbgek\policy under the registry path mentioned below:

   • For Google Chrome: HKLM\Software\Policies\Google\Chrome\3rdparty\extensions\

   • For Microsoft Edge: HKLM\Software\Policies\Microsoft\Edge\3rdparty\extensions\

2. Add the Nexthink instance URL by creating a registry key and values in the \policy folder as described below:

   • Name: instanceURL

   • Type: REG_SZ

   • Value: Enter your Nexthink instance URL, for example, https://myorganization.nexthink.cloud

1. Configure the SSO authentication by creating a registry key and values in the \policy folder as described below:

   • Name: isSsoEnabled

   • Type: REG_SZ

   • Value: 1 for true or 0 for false

If you do not choose the SSO enabled option, it remains disabled by default.

If you are using a portal-less instance of Nexthink, you must enable SSO logins, as the system does not support non-SSO login attempts for portal-less instances.

1. 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

1. Create the folder structure \kcidkikoejfejnfmbmhmfkncdlopflhe\policy under the registry path HKLM\Software\Policies\Microsoft\Edge\3rdparty\extensions\

2. In the policy folder, create the registry key and values as described below:

   1. Name: instanceURL

   2. Type: REG_SZ

   3. Value: Enter your Nexthink instance URL, for example https://Instance-Name.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

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)

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 (Microsoft Edge)

Local machine:

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

OR

Current user:

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