New features


New features

Improved boot and logon duration metrics

We have introduced several changes to improve the accuracy and usefulness of boot and logon duration metrics: boot values are now more precise and for user logon we now distinguish between an objective measurement representing the desktop being shown and a subjective measurement representing the device being optimally ready for use. More details are available in the Data-model changes page.

More granularity for visualizing CPU activity

In V6.4 we introduced a new device warning event called High overall CPU usage to better represent situations of high CPU consumption. This event is triggered when 70% of all logical processors are used, or in other words, when at least 70% of the total CPU capacity of the device is consumed.

In V6.5 we have modified the user and device views to include this event.

High cpu views V6.5.png

In the case of long lasting blue warnings: specific applications are consuming a large amount of CPU, but the overall device experience is not compromised. It can be interesting to investigate these situations because the high CPU usage might be abnormal and indicate an issue with specific applications. Moreover, battery life of laptops may be drastically compromised by applications that consume an elevated amount of CPU for long periods of time.

In the case of long lasting yellow warnings: the user experience is likely to be impacted and further analysis is recommended to identify and resolve the problem.

In both cases, the tooltips might offer additional insights into the applications causing the issues.

Find out more

Other changes

Metrics access rights

A new configuration setting allows you to more precisely control which Portal metrics users are allowed to access.

Metrics access rights v1.2.png

Migration considerations: the system will automatically choose a value to ensure that no user is given access to metrics that he could not access before the upgrade.

Find out more

New hardware requirements

The hardware requirements for the Nexthink Engine have been increased to accommodate upcoming features. Beginning with V6.6 (September 2016), up to 2GB of RAM and 2 CPUs should be added depending on your configuration.

Find out more

New connectivity requirements

Beginning with this version, both the Nexthink Engine and the Portal will connect to the Nexthink Application Library (in previous versions only the Engine was connecting).

Find out more

New Engine certificate

The default Engine certificate used to establish secure connections between the Web API, Finder, and Portal has been updated. For installations using the default certificates, users who saved the certificate in Finder or in the web-browsers will now again be asked to add an exception.

New Finder install and update mechanism, in beta

Installing the Finder has never been so easy thanks to our new install & update mechanism. Nexthink users with Finder access just need to log in to the Portal and select Install Nexthink Finder after clicking on their username.

Install finder v1.0.png

After that, it is just a question of launching the downloaded installer, which will then directly start the Finder and configure it to connect to the right Portal.

Finder installer v1.0.png

From this point forward, the Finder will be automatically and transparently updated, even in case of new releases of the Portal and the Engine.

Find out more about installing the Finder and updating the Finder.