Amplify installation and configuration

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.

Installing the Amplify browser extension

  1. Install the extension on your device manually to configure and test Amplify.

    • Install the Amplify extension from the Chrome Web Store on either the Google Chrome or Microsoft Edge browser.

    • Install the Amplify extension from the Edge Store on Microsoft Edge browser

  2. Push the extension to a target group of Amplify users via a group policy or with any other configuration management solution.

  3. 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 updates when a new version is released in the Chrome Web Store.


Configuring Amplify

Set up Amplify based on your specific needs:

To configure Amplify, ensure you have Manage Amplify permissions.

Configuring Amplify for a single instance

Follow the steps below to configure Amplify to integrate one Nexthink instance with one or multiple web applications.

From the Amplify browser extension:

From the Nexthink web interface:

Connecting to the Nexthink instance from the Amplify extension

Configure Amplify manually to integrate with the Nexthink instance:

  1. Open the browser where you installed the Amplify extension (Google Chrome or Microsoft Edge).

  2. Right-click on the Amplify extension in the browser extension bar.

  3. From the drop-down, click Options to open the Nexthink Amplify configuration page.

  4. From the Nexthink Amplify configuration page, click on New instance.

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

  1. Enable/disable SSO status.

  2. Log in following a successful authentication.

  3. Save the new instance configuration in the Amplify extension.

Deploying Nexthink instance configuration via Registry for Amplify users (extension installed from Chrome store)

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.

  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

Deploying Nexthink instance configuration via Registry for Amplify users (for extension installed from Edge store)

  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

Integrating with web applications from the Amplify extension

Integrate the Amplify extension with web-based applications for a specific device.

This local configuration does not apply to other Amplify user devices until you add the web application configurations to the Nexthink platform.

To integrate web application configuration locally:

  1. Open the browser where you installed the Amplify extension (Google Chrome or Microsoft Edge).

  2. Right-click on the Amplify extension in the browser extension bar.

  3. From the drop-down, click Options to open the Nexthink Amplify configuration page.

  4. Select the Local tab under Web application configuration.

  5. Click Add web application.

The Amplify extension only displays the Local and Central tabs in case of a single instance configuration.

  1. Fill in the Web application URL field, and use the User or device identifier and String selector according to the desired behavior for Amplify:

Enable the Amplify button on all pages of the web application

To enable the Amplify button on all pages of the web application, without reading the webpage for device or user identification fields:

  1. Add the base URL of the application in the Web application URL field.

  2. Leave the User or device identifier value field blank.

Enable the Amplify button on pages specific to a module of the web application

To enable the Amplify button on pages specific to a module of the web application, without reading the webpage for device or user identification fields:

  1. Add the URL specific to the application module in the Web application URL field.

    • For example, place the Amplify button on all pages of the ServiceNow incidents module by entering the web application URL: https://your-service-now.com/nav_to.do?uri=%2Fincident.do

  2. Leave the User or device identifier value field blank.

Enable Amplify to read identifiers from specific fields of the web application

Some web applications may no support the Amplify web application configuration using specific field identifiers due to differences in UI designs/fields.

To enable Amplify to read identifiers from specific fields of the web application:

  1. Open a new tab on your browser with the web application page URL with the populated device/user field. Copy the entire page URL.

  2. Add web application in Amplify and paste the copied URL in the Web application URL field.

  3. Select identifier in Amplify to open the web application URL using the Field selector pop-up.

  4. Use the highlighter to choose the field of interest on the page. Once selected, the system loads the element into the Field selector pop-up. See the image below.

  1. If pop-ups from the web application prevent you from selecting the correct fields:

    • Switch on the Disable selector toggle in the Field selector pop-up and navigate to the webpage of interest.

    • Once on the correct page, switch off the Disable selector toggle and pick the correct field.

  2. If needed, select a specific part of the string from the device or user identifier field using the String selector* on the Field selector pop-up:

    • Enter the relevant regular expression in the String selector field.

    • Click the Fill field value button to verify the selected field value.

    • Click Save to modify the relevant device or user identifier.

*Amplify Field selector supports the use of regular expressions for partial text matching. This enables the selection of specific parts of the string from the Selected field value. See the image below.

Refer to the Regular expression page from Wikipedia to learn more about this concept.

  1. Save the web application configuration.

Nexthink recommends pushing the single Nexthink instance configuration on all target devices using a group policy, configuration management solution or remote actions.

Integrating with web applications from the Nexthink web interface

Adding the locally configured integrations of web applications (from the Amplify extension) into the Nexthink web interface, allows all the devices with the Amplify browser extension to pull the configured integration from the Nexthink platform.

First, from the Amplify extension, you must complete the steps described before on this page:

  1. Ensure you have Manage Amplify permissions.

  2. Configure web application integration locally on your device.

  3. Copy the web application configuration fields: Web application URL, User or device identifier and String selector.

Then, from the Nexthink web interface:

  1. Select Administration > Amplify from the main menu.

  2. Add web application from the Amplify administration page.

  3. Paste the respective web application configuration fields from the Amplify extension (see step 3 above).

If you need to integrate with multiple web applications, add all web application configurations into the Nexthink platform.

Sorting web application configurations in the Nexthink web interface

Amplify reads the values of the fields in a sequence of configurations.

To change the selection sequence of the configured web applications, from the Nexthink web interface:

  • Hover over the relevant row and open the action menu to switch the order: Move up or Move down.

From the action menu, you can also Edit or Delete the web application configuration.

Configuring Amplify for multiple instances

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.

Before configuring Amplify for multiple instances, first:

Then, from the Amplify extension:

Adding multiple Nexthink instances

Locally add multiple Nexthink instances to Amplify:

  1. Open the browser where you installed the Amplify extension (Google Chrome or Microsoft Edge).

  2. Right-click on the Amplify extension in the browser extension bar.

  3. From the drop-down, click Options to open the Nexthink Amplify configuration page.

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

  1. Once the authentication is successful, the Amplify extension adds the instance to the configuration.

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

Configuring web applications for multiple instances

Once you have added the Nexthink instances, configure multiple Nexthink instances locally.

From the Amplify extension:

  1. Click New web application and follow the steps described in the Integrating with web applications from the Amplify extension section on this page.

  2. Optionally, Download configuration to export the web application configuration as a .reg registry file.

You cannot set up multi-instance configurations from the Nexthink web interface using the Amplify module. Therefore, the Amplify extension does not pull the central configuration from Nexthink for those multi-instance configurations.

See the section below for deployment details.

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

Configuring Amplify for specific ITSM solutions

The following guidelines outline what to do when an ITSM solution doesn’t support the out-of-the-box selector configuration due to version incompatibility or user interface design:


RELATED TASKS

Last updated