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.

My main use case for Nexthink is as a desktop analytical tool. We have used it primarily to conduct proactive ticketing for different issues that are reported on the desk and also to analyze the complete environment and identify which applications or particular sectors are affecting overall user experience.

One specific example of how I have used Nexthink for proactive analysis and troubleshooting involved a situation where VPN was not working for most employees in the environment and they were unable to connect to VPN. We received an alert from Nexthink about this issue. After that, we enabled self-remediation using Nexthink remote action and deployed those remote actions to all devices experiencing this problem. This is a high-level overview of how we resolved an issue before it started impacting different users.

Nexthink is not limited to investigations and providing insight of the environment. It has also helped us to manage the licensing aspect through license optimization, where we identified whether users were not using particular licenses and coordinated with software asset management to optimize that component.

Out of all those features, I find myself using L1 checklist the most because it is very helpful when we are providing proactive solutions to the first level of contact. Now they are equipped with a tool where they can use it very quickly while they are on call with the customer and make their experience far better than before.

Nexthink has positively impacted my organization by helping us achieve a high user satisfaction ratio. We have performed user surveys and gathered feedback from user sentiments, and the results improved significantly after the deployment of Nexthink because application crashes are minimized and users are not getting frequent issues on their devices. This really helps any end user because if they are not struggling with day-to-day issues with applications, it is a win situation for both IT and customers.

When talking about specific outcomes or metrics, we started with a user score of 65 out of 100 and now we are at 85 out of 100. This is a very substantial improvement over the last year.

Nexthink offers excellent features starting with proactive analysis, then providing insight of the complete environment, creating alerts, helping with software optimization, and automating the task of L1 checklist where we can directly enable short troubleshooting directly to any ITSM tools. Everything appears to be well-implemented.

Nexthink has positively impacted my organization by helping us achieve a high user satisfaction ratio. We have performed user surveys and gathered feedback from user sentiments, and the results improved significantly after the deployment of Nexthink because application crashes are minimized and users are not getting frequent issues on their devices. This really helps any end user because if they are not struggling with day-to-day issues with applications, it is a win situation for both IT and customers.

Nexthink still has more capabilities, and we are still struggling with new use cases because sometimes out-of-box solutions are not optimized according to our needs. However, I have expertise in PowerShell where I can customize any offering that Nexthink provides and modify it accordingly. This is feedback to Nexthink; otherwise, it is good and we can still work around it with our skills.

One thing I have noticed about needed improvements is that Nexthink learning platform only has text content. When someone new is starting with Nexthink, the learning experience is entirely text-based documentation. This should have something interactive where they can have an instructor who can guide them through what is happening or what methods they should use, such as a video platform where we can have live sessions demonstrating how it works. This would help newcomers who are trying to explore this tool.

I chose eight out of ten just because of the two things I mentioned: the learning material is not up to standard and they still need to improve on that side. The documentation part is acceptable, but sometimes it is confusing because we need to go ahead and dig through different documents to find all the information. Since everything is moving toward AI, Nexthink should also incorporate AI methodology into their documentation where we can get short answers or receive answers quickly from their documentation site and learning platform.

I have been using the solution for about six years.

Nexthink is very stable; we have not faced any downtime with the products that we are using. They have regular updates on their portals related to improvements in their metrics, improvements in their remote actions, and dashboard enhancements. This is quite good.

Nexthink scalability is based on a per-user license model, so when we need it, we get it.

Customer support is also very good. I already confirmed in my first interactions that I am a reseller, so sometimes I need support on particular things where my customer requires help on their Nexthink environment. When there is a bug or some functionality issue with the portal, I raise a ticket with Nexthink and the support is quite good, with resolutions coming very quickly. I have contacts in the team handling these queries, so it is quite easy for me to get hold of them and receive support.

I have not previously used a different solution; I have been working with this particular tool for the last six years.

Nexthink is deployed in my organization as a private cloud.

We did not purchase Nexthink through the AWS Marketplace; we are a reseller of that particular product. We have a contract directly with Nexthink and we sell it on behalf of Nexthink to our customers, to different projects, and to different organizations.

I have seen a return on investment because when you optimize licensing, there are many users who previously required heavy applications costing the organization around $300 to $400 and were not using them. With the help of Nexthink software license optimization, we identified those users and removed the licenses. Over a year, we have saved more than 2 lakh dollars. When it comes to fewer employees needed, it is because we can see that if a task is being done by one agent effectively, it will also help us reduce headcount.

My experience with pricing, setup cost, and licensing has been quite good. The pricing is somewhat high, but as compared to the outcomes that we achieve, it is good to invest in.

I have not evaluated other options before choosing Nexthink as I was part of Nexthink from the era when Nexthink was launched. I have been there from that time with Nexthink product, with different companies altogether.

I would rate Nexthink overall as eight out of ten because nothing is perfect in this world.

I would advise others looking into using Nexthink to first evaluate the environment and go with the pilot phase on a few devices that they want to start with. After that, proceed with a complete fleet of their devices on Nexthink because it is not an OEM dependent tool and they can onboard all the devices that they have. Make sure that you do the license analysis to determine how much license you need in priority because it is required to have enough license so that you can get a complete picture. Assume you have 10,000 devices in your environment and you have only purchased 10,000 licenses and have not done prediction for other devices coming in the next quarter or next year. If you are going to buy it separately after a few days, it is acceptable. However, having license predictions or having a setup ready for newly onboarded devices is good to have. Whenever they switch on the computer, whenever a new device comes into the environment, it should be on Nexthink so that you get the telemetry data from the first boot itself.

I mostly use Nexthink for analytics of IT tickets, which reduces the number of repeated tickets. We monitor which tickets are repeated and the issues occurring, giving priority to those issues.

For a customer who was receiving continuously one major and critical alarm that was causing service impact, Nexthink helped us monitor it and create separate monitoring for that customer, which helped us reduce the alarm and it no longer causes service impact to them.

Nexthink really reduces a huge amount of work through automation skills and automation steps, which saves considerable time. This is very useful in today's environment.

The best features Nexthink offers include the ability to integrate with ServiceNow or Salesforce to extract information, which is faster and enhances productivity. The faster extraction helps my daily work and my team because issues we have identified and resolved would be very difficult to find manually. When using a tool, it reduces that work to very few minutes, allowing us to find repeating issues.

Nexthink has impacted my organization positively, mainly in reducing repeated tickets. We can monitor and document a huge number of tickets, thousands of them, which is a positive aspect from Nexthink.

Nexthink can be improved. It is already an excellent tool with many features and is the best tool in the ITSM field.

If you add more AI features to Nexthink, particularly automation for resolving tickets, it would be helpful because AI is everywhere now. Some additional features in Nexthink that would improve the product would be beneficial.

Nexthink was a better option that I used to work on, and I did not depend on other options.

Nexthink is stable.

When I increase the work that can be done, it would be slow and not accurate.

Nexthink's customer support is good.

We have not used any different solution before Nexthink in my organization.

I have seen a return on investment. Time has been saved and work has been reduced.

My experience with pricing, setup cost, and licensing is that it seems a bit costly, but effective.

For a particular customer, the numbers show that more than 1,000 tickets were coming a month, which are now reduced to hundreds; this has saved my team considerable time and effort.

Since we are using Nexthink, we are not fully depending on it; sometimes we need manual intervention to check further, so I rate it as a 9 out of 10.

I would advise others looking to use Nexthink to proceed with Nexthink without considering other options.

My main use case for Nexthink is using Windows Hello for Business, which helps our users receive the Windows Hello notification on their system so that they can set up their PIN.

A specific example of how I use Nexthink with Windows Hello for Business is through a campaign that runs on users' systems and lets them know they need to set up a PIN to log in easily during their daily login.

Nexthink has positively impacted my organization by helping our service desk in many different ways. We used to receive numerous calls, but now, since we have the API and self-troubleshooting available in the catalog or portal, users can address common issues with Microsoft Teams or Microsoft Outlook, which reduces customer contact for our organization.

We used to receive around 22,000 customer contacts in a month last year, which has reduced to 14,000 in a month currently.

The best features that Nexthink offers are the campaign and the workflow within our environment, which helps users easily replace their systems and self-troubleshoot without reaching out to any IT service desk.

The campaign and workflow features help users self-troubleshoot by reminding them when they are using a retired machine and informing them that the life cycle of this machine has expired, allowing them to either continue using it for the next month or raise a request for a replacement machine, which benefits both the user and the company in complying with asset data.

I appreciate the ability to check their life cycle date via Nexthink on a monthly basis, as we roll out some kind of campaign for them.

Nexthink is solid, but I see that the upcoming updates include Spark, which will help our company easily gather data regarding user responses to our campaigns.

I have been using Nexthink for more than one and a half years.

Nexthink is stable in my experience.

Nexthink's scalability is good.

The customer support is very easy to contact, and they respond instantly whenever we have issues with remote actions or workflows.

We did not use any solution before Nexthink; this is the first time we are using it.

I am not really aware of the pricing, but I can say that it is very easy to set up the extension in our browser, allowing us to troubleshoot from there.

Nexthink has helped with license reclamation use cases, where many software applications are already installed on user machines that our vendor pays for, and rolling out the campaign has allowed us to identify unnecessary software and remove those licenses, saving costs.

Prior to choosing Nexthink, we evaluated SysTrack, but it did not help in service desk operations, which is why we moved to Nexthink.

I would advise others looking into using Nexthink to create use cases as much as possible, as this helps the vendor improve their business operations and run smoothly.

I give this product a rating of 10 out of 10.

Nexthink is used for DEX score analysis, vulnerability remediation, and device performance monitoring. The primary use case is improving DEX scores.

Nexthink completely scans devices and their performance, providing reports in the Nexthink portal that allow us to identify issues before customers report them. Based on identified issues, we can push remediation through Nexthink to resolve problems before clients notice or raise tickets. For vulnerabilities, we can also push remediation scripts or actions through Nexthink.

The tool is very fast, providing live updates to the Nexthink portal within seconds, which helps our company significantly.

The best feature is that it helps us improve DEX scores, which is our major focus, along with vulnerability remediation. For both cases, we push remote actions based on reports from Nexthink, allowing us to remediate vulnerabilities and improve DEX scores very quickly.

DEX scoring is the feature I rely on most day-to-day, as it is a unique and advanced feature in Nexthink.

The dashboard feature in Nexthink is also very good, allowing us to customize it based on our requirements through NQL scripts.

The NQL script and default templates for creating remote actions are quite complex and require time to adapt. It would be better if Nexthink provided more graphical user interface options, as the tool is mostly based on NQL queries and PowerShell scripts.

Nexthink has been in use for the last two years.

Nexthink is stable.

Nexthink can definitely scale up based on user or device improvements, and we are not facing any challenges.

For customer support, we have a dedicated engineer from Nexthink who is helping us significantly, making support very good.

We have not used any other solution for improving DEX scores; Nexthink is the first tool. We tried using a device analytics feature in InTune, but we found Nexthink to be more powerful, so we chose Nexthink.

Nexthink helps us improve DEX scores and end-user performance experience on devices, providing strong return on investment.

The price is somewhat high, but it is flexible based on requirements and is worth the cost.

Nexthink is a powerful tool capable of remediating issues within a short period. When compared to InTune, the time to remediate through Nexthink is very short because its communication is through the agent, making it a better tool. Nexthink is a better option if you want to improve end-user device experience. I rate this review an 8 out of 10.

We are using Nexthink primarily for device monitoring, and we have 28,000+ endpoints that we wanted to monitor. Nexthink provides that monitoring capability, not just monitoring, but also remediation. We monitor our devices via Nexthink, and if we need to apply any kind of remediation or fixes to any of the devices, we use remote action to do it via Nexthink.

The most common use case is disk cleanup. We have a bot, a user support bot, that our associates can reach out to with their issues. If they have any kind of disk usage issue, if their disk size is full, they report it, and with the help of Nexthink, we monitor it. At a certain threshold, we get an alert via Nexthink, and after a certain time, such as weekly, we have a remediation with a remote action that runs which takes care of the disk cleanup.

We are using Nexthink as a source of truth for our device-based information, as all our devices have the Nexthink agent and are onboarded with Nexthink. We have dashboards created for monitoring purposes, and we use Nexthink as a single source of truth. If there is any network outage on the sites, we refer to Nexthink to identify what devices have been impacted by that network outage. If there are any global outages with M365 services, such as Teams or Outlook not functioning properly, we leverage Nexthink for that as well for collaboration tools monitoring and other purposes. We have been using Nexthink as a source of truth for our endpoint monitoring and to apply fixes if we can.

The fact that we can easily have webhooks created in Nexthink to be able to receive alerts directly in our Teams is one of the standout features that I find in Nexthink. Then we can get the data from Nexthink via data exporter to Azure data lake, and we can go 90 days back, which is also one of the cool features that we as an organization find useful because we eliminate the limitation of retaining data. Nexthink retains data for I believe 30 days or 60 days, so we can go even beyond that. The other integration and recent addition of AI is quite nice. Spark, the latest AI agent that Nexthink is introducing, is also a cool feature. In totality, I find Nexthink very useful, and we as an organization find Nexthink very useful.

Webhooks are a very underrated feature that Nexthink supports because if you utilize webhooks properly, you will be able to get your alerts in real-time in your Teams or wherever you would like to receive it. ServiceNow Amplify is also one of the underrated features because it is a browser-based extension that you configure, and the configuration is also pretty straightforward.

Our device outage is very reduced with the help of the great monitoring that Nexthink has to offer, which is the major thing. Our incident management team can utilize their time with other issues or other burning issues that are happening in the organization. On the endpoint side, we would say that we are much more covered than we were earlier. We have eliminated some major outages, issues, and impacts and have reduced them with the help of Nexthink.

Initially, for every single outage, we were not aware of what exactly the numbers were and how many devices were impacted. We had to spend time finding out how many devices were impacted. Now, we simply go to Nexthink. We do not even have to write the NQL query, which is the best part. You do not need to know Nexthink query language. You can use Nexthink Assist to help you with that, and with a single query, you can find all the devices which are impacted by the outage, and that much amount of time is saved from gathering data on the impacted devices. You are saving time in gathering the data, and then applying fixes is also quite seamless via remote action, so you are saving time there as well. From two to three days of time that we used to invest in gathering the details of the impacted devices and then two to three days again for applying the fixes, that time has been substantially reduced with the help of Nexthink.

The device details need improvement. Even though Nexthink has custom tagging that you can use to gather the data and you can do custom tags on the devices and bring the data that you want on Nexthink, people still feel kind of hesitant. If someone is not familiar with SQL that much, even though you have Nexthink Assist, you need to have the documentation side of it, which I believe needs improvement. There was an instance when I was troubleshooting certain issues, and I found that the step that actually fixes the issue was missing from the Nexthink documentation.

I believe Nexthink product team is already on top of it. We receive daily notifications about what product enhancements the Nexthink team is doing, so we are on top of it. They regularly take feedback from us. Nexthink is aware of the organization gaps and the needs are, and they are trying to implement it, which is good.

I have been using Nexthink for a year.

Nexthink is very much stable.

The scalability is decent.

Customer support is good and could be better.

We were completely on Intune and we still are. For monitoring purposes, we needed a better monitoring and remediation solution, so we have Nexthink. Initially, we did have Absolute, and I believe it was not that convincing. Our organization decided to switch to Nexthink.

We were made aware of the Nexthink product. We did our research about this product, and in the POC as well, we were quite convinced with the data that we saw from Nexthink and the kind of capability it had. For our 20,000+ endpoints, since it works on query language, there was no better tool than Nexthink. It was pretty straightforward for us that we have to go for Nexthink.

I was part of the implementation team.

There is definitely ROI. As I said earlier, there is time which has been spent less compared to earlier without Nexthink. If time is spent less, the money is automatically saved. Unfortunately, I could not help you with the numbers because I am not part of the commercials.

We directly purchased Nexthink from Nexthink itself, the Nexthink product team. We reached out to Nexthink and we procured Nexthink from Nexthink itself.

I am not quite sure about the licensing part because it was taken care of by upper management. My role was on the technical side of it. I was in charge of doing the POC and onboarding Nexthink to my organization. I was not involved in the licensing part of it, such as the negotiations with Nexthink. I was not part of the commercials.

See if your organization really needs Nexthink. I am saying this because Nexthink is useful when you have a large number of endpoints. If you are a small business, I would not recommend you to invest because Nexthink is not cheaper, which is what I have heard from my leadership. If your organization has more than 10,000+ endpoints, you need Nexthink because the data monitoring that it offers is really seamless and quite efficient. The remediation mechanism offered by Nexthink is also pretty seamless and robust, so if your organization has 10,000+ endpoints, you should go for Nexthink if your budget allows it. If you are a small business, I would not recommend going for Nexthink.

Nexthink served as an enhanced version of disk cleanup for our organization. Earlier, disk cleanup used to clear only the recycle bin and temp files, whereas we moved the files to OneDrive. Any file on the device that is beyond a certain size is moved to a OneDrive folder, creating the file with the same name and logo. On the user's machine, it creates a 2KB shortcut with the same name and logo, so whenever the end user clicks on that file to open it, they are redirected directly to OneDrive. We saved a lot of disk space, clearing up more than 90 terabytes of free disk space.

The out-of-the-box remote action from Nexthink, which is disk cleanup or system cleanup, did not make those drastic changes. We came up with an idea since just clearing the recycle bin and temp files would not work. The temp folder restores data as soon as we delete everything and the browser refreshes, so we needed a permanent solution and thought that if disk space is being used, we should save the files on OneDrive rather than keeping them on the device itself. The challenges we faced during the implementation included the device having to be online and connected to the internet to sync with OneDrive. If the files are not syncing, we face a problem, and if the device is offline during transfer, the process can get corrupted or fail.

Nexthink has been helpful in many scenarios, such as when a web application is not performing well in a certain location. We can configure the application to capture the data and go through the performance, see the network reliability, and based on that, we can sort out the data using live dashboards, identifying the root cause. For example, there were almost 1,500 devices in our environment using WhatsApp, which is unauthorized software. We created a custom script, got approval from the customer, and deployed a campaign to all the users.

Nexthink offers many features, with the best being Flow, which encompasses almost everything. We have Nexthink Workspace and Spark, allowing integration with Teams so users can find solutions without going to the service desk, rectifying issues in chat. Nexthink Infinity has brought a lot of benefits to us.

There has been a very good change from integration. Integrating ServiceNow with Nexthink automates problem ticket and incident generation, enabling the team to proactively know the kinds of problem statements we are receiving. For the integration with Teams, we have not completed it yet, but we are in the planning phase, and once done, we will observe the results.

Nexthink has the capability of integrating with most third-party applications, which is a great feature.

With the remediation actions we have in Nexthink, it has provided great self-heal capabilities along with proactiveness. By looking at the dashboards and identifying problem statements, we can share this information with the end-user computing teams to fix issues. Nexthink has significantly helped us enhance our DEX score from 74 to 80.

When I talk about features that led to the improvement of our score from 74 to 80, there were earlier issues with device performance and reliability not being addressed. Noting these, we identified devices lacking free disk space and low RAM capacity contributing to high memory usage or excessive CPU usage. Disabling unnecessary startup applications brought us to a new DEX score of almost 80.

Nexthink still lags in several areas. Firstly, in software metering, where it focuses on the configured application rather than understanding the users utilizing the licenses. Not everyone clicking on an executable file is a licensed user, and we need effectiveness in identifying the exact user with the license based on usage. Secondly, Nexthink lags in identifying network problems such as latency, and these are features I wish to see improved in upcoming releases.

I have been using Nexthink for almost six years.

Nexthink is stable, though not 100 percent, but mostly it is stable.

Nexthink's scalability is pretty high. We can scale it significantly, not just for creating and updating incidents in ServiceNow but many more applications can be integrated, and it can fetch data and convert it into manageable dashboards.

Customer support for Nexthink is a pain point due to unclear SLAs and requests for logs that are not needed. We have checked things from our end, but sometimes simple solutions are made overly complex.

Overall, my experience with pricing, setup cost, and licensing was adequate. Nexthink requires a license for almost everything, with different licenses for collaboration, Flow, Experience Central, and Application Experience, leading to licensing problems. However, the overall experience with setup cost and pricing has not been that high.

We have seen a return on investment based on issues resolved by using Repair OneDrive, clearing Outlook OST problems, and clearing Teams cache, showing man-hour savings. Considering 25 dollars for every saved hour, we have saved a significant amount. Consequently, manpower can also be reduced since AI is taking care of tasks, with Spark and everything coming into the picture, making Nexthink very useful.

Overall, my experience with pricing, setup cost, and licensing was adequate. Nexthink requires a license for almost everything, with different licenses for collaboration, Flow, Experience Central, and Application Experience, leading to licensing problems. However, the overall experience with setup cost and pricing has not been that high.

Before choosing Nexthink, we evaluated other options such as Systrack, ControlUp, 1E Tachyon, and Aternity. After examining these options and the Gartner reports to determine industry leaders in digital employee experience, we finalized on Nexthink.

Nexthink is deployed in our organization on a public cloud, and we use Azure as our cloud provider. Nexthink is a great tool for device analytics, providing complete insight into devices and great solutions with many integrations that simplify work. However, it is essential to have a licensing tool alongside it, such as Microsoft Office 365 or Flexera, to monitor license usage. I would rate Nexthink an 8 out of 10 because there are many pros in Nexthink, but a couple of cons as well, so I have deducted two points.

I use Nexthink for monitoring, root cause analysis, and fixing issues. It acts as an MDM in similar cases, and the Nexthink agent helps us understand system issues to prevent OS-related or driver-related issues. We conduct a reactive setup instead of a proactive one.

Regarding root cause analysis, we usually perform a regular user checklist, checking end-user devices. While running that, we can see if user devices have a lower version of applications, lower driver issues, or any BIOS that needs updating. We monitor such issues and drive health check-ups through the Nexthink agent, alerting users as needed and running device diagnostics. By doing that, we conduct root cause analysis and prevent issues from occurring, making Nexthink very useful. Overall, my experience with Nexthink is that it is great, and I have recommended it to colleagues in my previous organization.

The main use case is to always try to prevent issues with a device history check. If there is a blue screen error, we can determine the cause through Nexthink, and also monitor how many devices are trying to log in with the same user. This is a major use case, and an added advantage that Nexthink provides us is the ability to take past history into account, allowing us to prevent potential future issues.

We commonly use all of Nexthink's features, such as real-time monitoring, automated device health check-ups, and root cause analysis. Through root cause analysis, we aim to prevent issues, and we also conduct user experience analysis through Nexthink.

Nexthink has a positive impact on my organization. We use Nexthink for endpoint device monitoring, security and compliance, and to enhance user experience. The major positive aspect is that it provides more accurate real-time monitoring, and it has helped my team reduce requests by preventing issues before they occur through normal health check-ups.

By doing that, we can reduce almost 30% of requested tickets because, initially, there are major issues, especially with Windows updates. By deploying new updates and receiving system feedback through Nexthink during root cause analysis and monitoring, we can prevent such issues. We must always keep BIOS and drivers up-to-date, and by proactively analyzing devices, we achieve better outcomes and prevent system issues from occurring.

I feel there is some gap in the application interfaces of Nexthink. If the user interface were improved, it would be an added advantage since it would provide a simpler way for users to work, especially for new users who may face challenges if they aren't hands-on with the tool.

I chose eight out of ten because of data utilization and visibility where I see a gap. Other than that, everything is fulfilling, but I feel proactive issue detection from the tool side needs focus. This includes setting up early warning alerts for CPU spikes or disk issues. Monitoring is essential for identifying problems when they arise, and proactive issue detection should be prioritized. Improving automation and self-healing capabilities would also make a significant impact, as reducing helpdesk tickets with automated fixes is crucial.

I have been using Nexthink for the past three years and have completed the Nexthink certification as well.

Nexthink is currently stable. Initially, we experienced issues due to setups, but it is stable now. However, as mentioned before, there are improvement areas that should still be explored.

In my experience, Nexthink handles scaling up very effectively. It has the capability to manage an increased number of end-user devices, and we can still scale up without encountering issues.

We haven't needed to reach out to customer support for Nexthink. However, my colleagues who use it inform me that the support is good, and there is also a community available for inquiries.

From day one, I have used Nexthink without switching from another solution.

With the investment in Nexthink, we save time for the IT team. If the IT team acts proactively due to Nexthink, employee productivity improves as well. Thus, this investment is quite beneficial for our organization.

Pricing, setup costs, and licensing for Nexthink depend on the budget and are not straightforward or affordable. They vary based on the number of end-users onboarded to Nexthink servers, which impacts the license cost.

I currently evaluate Nexthink as the tool that performs monitoring and health check-ups effectively. We already have an MDM, and while some MDMs provide monitoring agents, Nexthink stands out as the best option. We attempted a POC with Ivanti and other tools like InTune, but they are primarily ITAM tools. Nexthink meets our business needs effectively.

My advice for anyone looking to use Nexthink is to conduct a POC tailored to their organizational structure, metrics, and end-user devices. They must validate Nexthink's features against their specific requirements. It is crucial to follow an RFA process and onboard multiple devices for testing before deciding if Nexthink meets their needs. I recommend always testing first to ensure it works for their scenario.

I believe Nexthink can improve data-driven decision-making by using insights to influence business decisions. For example, when conducting campaigns to understand devices, the IT team can validate procurement decisions based on data from Nexthink regarding common issues and root causes related to hardware. This capability would help improve the purchasing process, ensuring better models are chosen based on actual user experiences and device performance.

I have rated this review as an eight out of ten.