Extension deployment

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.

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:

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://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:

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

RELATED TASK

Amplify Installation and configuration guide

Last updated

#451: 2024.8-Overview of integration DOC

Change request updated