New features


New features


Engage on Mac

To engage with Mac users in the same way as you do with Windows users, campaigns are now available on macOS with all the features you love:

  • One-off, recurring and continuous campaigns.
  • Single answer, multiple answer and opinion scale questions.
  • Workflows.
  • Internationalization and translations.
  • Links and placeholders in campaign descriptions.

Do not forget to add the Mac platform to the investigations on users for your campaigns and enable Engage when you install the Mac Collector.

Find out more

Engage on servers

Engage is supported on Citrix when a full desktop session is streamed.

  • Before 6.20, this was supported when the desktop was streamed from a non-server operating system (e.g. Windows 10).
  • From 6.20, this is also supported when the desktop is streamed from a server operating system (e.g. Windows server 2016).

Note however that environments based on single application streaming (where the whole desktop is not streamed but a single application is streamed) do not support Engage.

Enabling or disabling Engage

For some special devices on your corporate network, it may make sense to opt out of Engage. Choose whether to enable Engage, enable Engage only on non-server devices or completely disable Engage when installing the Collector.

Find out more

Portal scalability

Configurable maximum number of metrics

The maximum number of metrics supported is now configurable from the Web Console. The default is still 500 metrics, but you can go up to an absolute maximum of 1000 metrics. For customers that already contacted Nexthink Support to increase the maximum number of enabled metrics, the default maximum value when they upgrade to V6.20 is kept to their previously configured value.


When required, gradually increase the maximum number of metrics while ensuring that the Portal has enough disk space to store the data and that the time to compute the metrics is under control.

Find out more

Software metering improvements

The computation of Software Metering dashboards has been greatly improved in V6.20. Therefore, the previous limit of 2000 entities to setups with a Software Metering module is no longer imposed and the default maximum of 8000 entities is applicable to all setups instead. Take advantage of the new performance improvements in Software Metering computation without modifying any of your existent metrics or modules.

Beware however that the upgrade to V6.20 resets the cumulated binary usage data from your Software Metering metrics. This is relevant only if you specified a set of binaries when creating the Software Metering metrics. Although it is possible to recompute up to three days in the past, export your previous results to CSV files before upgrading to V6.20 to avoid losing any binary usage data that might have been stored (up to 30 days, by default). In any case, remember that you can always compute the cumulated execution time of a set of binaries on each device through the Finder.


Find out more


Impact of remote actions

To execute remote actions with higher confidence, see the number of impacted devices across all Engines when you save an automatically triggered remote action:


Find out more

Cross-Engine features

Exporting lists of results to CSV

When running a Cross-Engine investigation on the Finder, there is a limit on the number of entries that the Finder can display in the list of results. To overcome this limit, export the results to a CSV file for later analysis:


Find out more

Search across all Engines

Find any kind of item --and not only users or devices-- across all available Engines thanks to the new Search button on the starting page of the Finder:


Find out more

Configuration of auto-complete data

When fully enabling the Cross-Engine features of the Finder, configure the objects retrieved for auto-complete data by most recent for an optimal compromise between word completion and Finder responsiveness.

Find out more

Rule-based Collector assignment

Extended properties for assignment rules

In addition to the name and the IP address of devices, the rules to assign Collectors to Engines can now be based on the distinguished name, the Active Directory Site and the Collector tag of devices.

Find out more

Assignment of roaming Collectors

Devices that connect to different networks or subnetworks may switch from one Engine to another because of assignment rules depending on the IP address of the device, for instance. Configure a stickiness value for the Collector to avoid switching Engines too often.

Consider also the case of devices on VPN that are on the same subnetwork but that must report to a different Engine.

Find out more


Finding the visual representations of a metric

To visualize a metric in the Portal, you typically add it to a widget on your dashboards. When you have many dashboards displaying multiple widgets, it is easy however to lose track of the link between a metric and its visual representations.

From the Finder, find now the dashboards that display the values of a metric and drill-up to the Portal to see its related widgets.

Find out more

Centralized configuration to identify devices by name

Identifying devices exclusively by their name is useful in virtualized environments for Nexthink to correctly distinguish different virtual machines. From V6.20 on, the configuration to identify devices by name is centralized in the Web Console and not spread throughout the configuration files of the Engines.

Find out more

Support for the latest versions of Windows

The Collector supports the latest updates of Windows 10 and Windows Server operating systems:

  • Windows 10 1809
  • Windows Server 2019