Centralized Management of Appliances and Engines

Contents

Centralized Management of Appliances and Engines

Appliances and Engines can be managed individually from the Appliance Web Console. If you have several appliances, the Centralized Management solution will allow you to configure them centrally.

To access the Centralized Management of Appliances in the Portal, select the Administration module, then the Appliances dashboard under the section Central Management.

The Appliances and Engines can be configured centrally from here, allowing you to perform an action on all the Appliance(s) or Engine(s) you select.

Centralized Appliance Management

Enable Appliance for centralized management

Connect to the Appliance Web Console with the admin user as shown in Installing the Appliance. Enable the Appliance Remote Account of the Appliance by checking the Enable option of the Account status. The Set new password field is not mandatory. If no value is entered, the default password is api.

Adding an Appliance for centralized management

In the Appliances section:

  1. Click on the plus icon
  2. Enter the Appliance Name, IP Address and Port, the Remote management password and Description. Note that in the IP address field, one should enter either the IP address or the DNS name in order to match what was entered in the Address field of the Engines dashboard in the Nexthink Portal section (refer to Connecting The Portal To The Engines). Validate your entry to add the appliance to the centralized management.

Central configuration of Appliances

Select the Appliances to configure and press on the configuration icon. You have several configuration options:

Enable Web Console
Allow the connection of users to the Web Console in the Appliance.
Disable Web Console
Prevent users from connecting to the Web Console in the Appliance.
Configure SMTP
Nexthink uses the Simple Mail Transfer Protocol (SMTP) for sending reports and alerts to a mail server for relaying to the Nexthink administrator. Enter or update the SMTP settings requested.
Configure NTP
Nexthink synchronizes with NTP servers using the Network Time Protocol. Enter the list of NTP server addresses seperated by a space. One option is to use the NTP servers offered by http://www.pool.ntp.org/en/, such as 0.pool.ntp.org, 1.pool.ntp.org, etc.
Update
Check and update the Nexthink Appliance.
Reboot
Reboot the machine that hosts the Appliance.

Add or remove Engines related to an Appliance

  1. Click on the information icon corresponding to the Appliance of interest.
  2. Click on the chain icon to start or stop the central management of an Engine. If the central management is started, the Engine will show up in the Engines section of the Appliances dashboard.

Edit or remove an Appliance from centralized management

  • To edit an Appliance, click on the corresponding pencil icon
  • To delete an Appliance, click on the corresponding trashcan icon

Centralized Engine Management

The Engines section shows the Engines associated to the Appliances managed centrally. Select the Engine to configure and press on the configuration icon. You have several configuration options:

Configure LDAP
Set up your LDAP servers to get Active Directory information for Nexthink objects.
Information
Displays a table with the different configuration settings and general information on the Engine.
Refresh DNS
Use this option to refresh DNS information on the Engine. This can be necessary if you wish to reflect changes on a DNS server (configuration changes or updates in the resolution of a particular destination). The Engine resolves new Destinations, but it does not refresh their DNS automatically if it changes.
Refresh LDAP
This option is generally used in a scenario where the LDAP server integration is performed after Engine installation. In this case, launch this option to trigger the Engine refresh of its LDAP information. The Engine gets information from the configured LDAP servers on every new user detected.
Restart
Stop and restart the Engine. Note that restarting the Engine results in a temporal loss of data received from Collectors during the time of starting up.