Nexthink is used to monitor endpoints like servers and Microsoft Windows devices, creating alerts for them if there is any binary crash or device issues, and then proactively resolving those issues.

I found there were many issues with disk space on the endpoint, and in my projects, more than 50% of devices were experiencing common device issues. I used Nexthink to clean profiles that were older than 30 days. This use case has helped me considerably, and we were able to increase the score for Nexthink.

I use Nexthink daily to view reports through the dashboard to see how things are performing. I observe what is happening in my environment, find these issues, and provide reports to my SCCM and Intune team. Accordingly, I connect with the EUC team, helping them by clearing data. There are many use cases, and daily, I remain proactive regarding various aspects including applications and different telemetry data such as endpoints, applications, networks, and user data.

Nexthink has positively impacted our organization by enabling us to properly perform OS upgrades and other Windows updates by clearing spaces and being proactive for applications and endpoints. This helps us considerably, as it is not only assisting the users but also the endpoint EUC teams. It is very useful, and the clients are happy; they want more and more, and we inform them about what is coming.

After creating use cases for my environment, I usually check the past tickets and next month's tickets and compare them. I found it very useful, and we have reduced the number of tickets for my service desk team, as they are receiving fewer tickets for password resets. This is very helpful in the case of incident tickets compared to the use cases. Additionally, users are feeling happy because they are proactively receiving alerts that are very good, and we configure them according to our needs. It is not basic, normal, or boring alerts; the users are also connecting with the IT teams and Nexthink team, providing their data, and accordingly, we are helping them. Nexthink is not only proactive, but users are also providing their data, which is beneficial.

We are saving a considerable amount of time for our service desk staff. We are clearing 60 TB of data from 15,000 user accounts, which I believe is very effective. It is saving man-hours, as we can schedule tasks to clear data automatically. This is very helpful, saving both time and money since we are not deploying resources for that function. Nexthink alone is helping considerably, and we are clearing more than 50 TB of data per month using our use cases.

The best feature of Nexthink combines endpoint data, providing the DEX Score, Digital Experience Score, by combining both the endpoint score and user sentiment score, which is a best feature for Nexthink.

Regularly, whenever I see the scores, by examining the scores, I can determine if devices are performing well and how the users are feeling. Accordingly, I can be proactive and create scripts, which is how it is helpful.

There are many more features in Nexthink, including support for mobile devices apart from endpoints such as laptops. Now, we can also see who the support engineers are who are working on many other things, helping them resolve issues on their mobile devices. These features are very helpful, as well as features including AI tools where we can monitor how companies are using AI tools. There are many features available.

Nexthink can be improved. From my experience with Workspaces, there is a component called Workspaces, and I believe there is an AI performance issue. After three to four prompts, it is not providing proper data, in my opinion, as I usually do not receive good, proper data from the prompts.

I have been using Nexthink for the last two years.

Nexthink is very stable from my experience.

Nexthink's scalability is good; we can scale at any time if we have the licenses. In that sense, it is scalable and very useful.

Whenever my team has to reach out to Nexthink's support team for help with technical issues, troubleshooting, or general inquiries, they are very helpful.

I have used 1E Tachyon before Nexthink.

I would give one recommendation and one tip: I would ask others to focus on the data. They need to understand the data and classify it properly while creating the dashboard or something similar. They have to set up user data, endpoint telemetry data, and then they can investigate or set up alerts for the application data. By also investigating the networking data, this is how I would recommend creating alerts, dashboards, and other things. Then they will be able to use Nexthink properly and be proactive. I would rate this review a 9.

Recently, our organization has been facing some application crashes. I run remote actions on a few devices to collect logs from the affected devices, and I check if there is any application fault or issue to get the exception code through Nexthink to help troubleshoot the issue.

We use Nexthink as real-time analytics, a performance measurement tool, diagnosis tool, compliance tool, and for checking hardware and software issues, application monitoring, and managing device scores and endpoint scores.

Because I work remotely as an endpoint management engineer, I find it very helpful to connect to devices remotely through Nexthink, which requires Nexthink collector to be installed on every device in our organization for communication.

Nexthink manages devices in real time, which is one of the best features, and it also allows searching for any feature through the search bar, where AI provides helpful information related to Nexthink data or devices.

Nexthink helps us manage devices and troubleshoot issues related to device performance and application performance. Additionally, we can run PowerShell queries through Nexthink. The impact of Nexthink on our organization is very positive, making device management easy.

I suggest a more flexible dashboard and AI-generated query capabilities as needed improvements for Nexthink.

I chose seven out of ten for Nexthink because it acts as a device management tool, but we cannot manage all devices through Nexthink due to some missing features when compared to other tools like Intune.

I would advise others looking into using Nexthink to start with a clear understanding that it is a very powerful tool that reduces tickets. It automates many tasks for us and provides visibility into application performance. I recommend everyone to use Nexthink at least once to see how many tasks are reduced in their organization, which will help them manage their endpoint devices.

I give this product a rating of seven out of ten.

My main use case for Nexthink is measuring the digital experience for the users in organizations, and it is also used to automate incident resolution.

A specific example of how I have used Nexthink to measure digital experience or automate incident resolution is that it shows a score calculated by measuring application-related experiences, system-related experiences, and individual perception of how the system is performing. All these measurements are processed to calculate a Digital Experience Score. Monitoring this score signifies how the digital experience is for the employees of the company. I create PowerShell scripts that run from Nexthink to resolve certain issues, which is done through analyzing existing tickets or issues where a known resolution can be automated using a script.

I have seen specific outcomes from using Nexthink such as saving almost 30% of time when automating tasks for the service desk, which reduces issue resolution time from 10 to 15 minutes manually to just one to two minutes with automation, providing significant time, effort, and cost savings.

The best features Nexthink offers in my experience include the Live Dashboards, which give real-time data or insights about my organization, the automations, and system and application health monitoring and network monitoring.

I find myself relying most on the Device View module in Nexthink because it gives granular level insights of the systems. It also includes a time scale so I can look back in time to see what kind of issues could lead to a bigger problem. It includes data such as applications running on the system, resource utilization such as RAM and CPU usage, and how the network bandwidth looks. These details allow me to analyze and figure out the root cause of incidents or find solutions for system-level performance.

I would also like to mention that Nexthink has an AI Assistant option, which is a very good feature that provides insights into existing issues, helps understand how the tool works, and guides me in creating queries.

My main use case for Nexthink is to resolve and analyze problems, identify devices, identify running applications, and much more.

A specific example of how I have used Nexthink to analyze problems and identify devices is when a system issue occurs on a user's system and a user has logged a complaint. I connect with the user, take their hostname, input it into Nexthink, and trigger Amplifier. Once Amplifier runs, it provides me with complete diagnostic results.

I use Nexthink daily to identify issues and determine the next course of action, primarily to resolve fixes including updates or configuration issues that can be resolved immediately.

The best features Nexthink offers include Amplifier, which provides a detailed view in the form of a report.

What I appreciate most about Amplifier or the detailed reports it provides is that it helps me see complete data and analysis reports from whatever Amplifier I am running or executing on the user system, and that gives me the results. This is the best feature I find very valuable.

Initially, resolution used to take more than two to three days, but after using Nexthink, it has been immensely reduced, and with an immediate click, it has helped resolve the issue in a single action. This is a very powerful transition that has occurred due to Nexthink.

Nexthink can be improved based on how we choose to take it forward upon the requirement, which does depend on the project and project complexity. If a project requires complex analysis, we need to program Nexthink accordingly.

An additional improvement I would like to suggest is that if we have more scope for analysis or in terms of running Amplifier that currently tells me only a few reports, I would like it to bring more reports and a more detailed view, which will help us analyze the next course of complex issues to be resolved.

I have been using Nexthink for more than six months.

Nexthink is stable in my experience.

Nexthink can scale up easily and handles growth well when my organization adds more users or devices.

The customer support is very good.

It was very easy for my team to learn and adopt Nexthink because it is very user-friendly.

I would like to add that the features have a continuous improvement aspect, so anything that we find needs to be added, we implement accordingly, conduct testing, and upon that, we bring that implementation into production.

Nexthink is helping to reduce the resolution time, which positively impacts us by receiving very good feedback from clients.

I believe Nexthink has strong security features, and it also depends on how the administrator has configured it to capture data. I think it is safe and secure, particularly since the organization is already secured in terms of implementing configurations.

I find the reporting and analytics capabilities in Nexthink not really detailed, but they provide what is actually required. They do not always meet our exact expectations, but they are vital enough.

The performance and speed of Nexthink when running analyses or reports are medium; it is not really fast, but it is fast enough compared to human interaction in resolving issues.

I would describe the user interface and overall user experience with Nexthink as friendly.

The level of documentation and resources available for Nexthink is satisfactory; I have gone through tutorials up to an intermediate level and am progressing toward the advanced level.

I will definitely recommend Nexthink to others looking into using it.