Installing and configuring Amplify
Last updated
Last updated
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.
Install the extension on your device manually to configure and test Amplify.
Install the Amplify extension:
From the Chrome Web Store on Google Chrome.
From the Edge Store on Microsoft Edge.
Push the extension to a target group of Amplify users via a group policy or any other configuration management solution.
After installing the Amplify extension, verify that the browser has added the extension by using the extension manager page:
For Google Chrome: chrome://extensions/
For Microsoft Edge: edge://extensions/
The Amplify extension from the Edge store only functions if SSO is enabled and configured.
The Amplify extension updates when a new version is released in the Chrome Web Store.
Set up Amplify based on your specific needs:
Integrate a single Nexthink instance with one or multiple web applications.
Integrate multiple Nexthink instances with one or multiple web applications.
To configure Amplify, ensure you have Manage Amplify permissions.
Open the browser where you installed the Amplify extension (Google Chrome or Microsoft Edge).
Right-click on the Amplify extension in the browser extension bar.
From the drop-down, click Options to open the Nexthink Amplify configuration page.
From the Nexthink Amplify configuration page, click on New instance.
Enter the Customer name and the URL of the organization's Nexthink instance using the following https://INSTANCE_NAME.cloud format.
The Nexthink URL must end with .nexthink.cloud with no forward slash after .cloud.
URL example:https://myorganization.nexthink.cloud.
Enable/disable SSO status.
SSO is enabled by default to use Okta-based SSO to log in to Amplify.
If SSO is not enabled on the Nexthink instance, disable the SSO toggle. Refer to the SSO configuration section of the Deploying Nexthink instance configuration via Registry for Amplify users documentation for more information.
Log in following a successful authentication.
Save the new instance configuration in the Amplify extension.
The Amplify browser extension supports integrating multiple Nexthink instances. This is particularly helpful for support teams sharing an ITSM solution with customers with independent instances.
To locally add multiple Nexthink instances to Amplify:
Open the browser where you installed the Amplify extension (Google Chrome or Microsoft Edge).
Right-click on the Amplify extension in the browser extension bar.
From the drop-down, click Options to open the Nexthink Amplify configuration page.
Click New instance and fill in the fields from the pop-up:
Name that is used to identify the customer. The customer name is unique.
URL of the Nexthink instance of the customer. The instance URLs are unique.
Enable or Disable the SSO status toggle to match the SSO-configured status of the Nexthink instance.
Log in to the instance.
Once the authentication is successful, the Amplify extension adds the instance to the configuration.
Click Save and add another instance by clicking on the Add instance button.
Edit or Delete instances, by opening the action menu from the relevant instance.
You require a valid account with Amplify permissions on each Nexthink instance to configure.
To deploy the Nexthink instance configuration to multiple devices:
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\
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
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.
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
Create the folder structure \kcidkikoejfejnfmbmhmfkncdlopflhe\policy under the registry path HKLM\Software\Policies\Microsoft\Edge\3rdparty\extensions\
In the policy folder, create the registry key and values as described below:
Name: instanceURL
Type: REG_SZ
Value: Enter your Nexthink instance URL, for example https://Instance-Name.nexthink.cloud
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
After configuring Amplify to integrate web applications for multiple instances, from the Amplify extension:
Download configuration to export the configuration details in .reg registry file.
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.
Local machine:
OR
Current user:
Local machine:
OR
Current user:
RELATED TASKS
