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.

I use Nexthink for monitoring security incidents or traffic in my network and the user's behavior, the software installed on the devices, and all security related events or types of events.

I use Nexthink to track the user's behavior or the traffic when they try to access a malicious website or try to bypass the proxy, or when they try to open a website that is malicious or prohibited by our organization. I also use it when they try to install software that is not allowed in our network or try to gain admin access on their machines.

Nexthink has positively impacted our organization by giving us more control over the users, more understanding of any live actions, and more visibility to our network. Beyond the other products, it provided us with add-on features.

Nexthink has helped us save time in the analysis of what is happening. Whenever I see a specific user or any malicious activity within the network, it gives me real-time assistance.

The best features Nexthink offers, in my opinion, are the traffic and user behavior of the internal network with the interaction with the outside network. That is mainly from my perspective the most useful thing that Nexthink adds.

The traffic behavior feature in Nexthink gives a deeper understanding of traffic analysis. Similar to Wireshark, it captures packets, but Nexthink gives me an overview of the whole traffic from the user to the end in the outside network. It gives me a deeper understanding of the behavior and the analysis of the users.

Nexthink has positively impacted our organization by giving us more control over the users, more understanding of any live actions, and more visibility to our network. Beyond the other products, it provided us with add-on features.

I would appreciate the ability to integrate Nexthink with other products that I work with, such as Google SecOps and SOC products in general. It would be useful to integrate in this manner.

Integrating Nexthink with other security monitoring tools such as SOC tools, QRadar, Google SecOps, Splunk, and LogRhythm would be beneficial. That would be particularly helpful in my field specifically because I work as a security operations or SOC consultant, and it would help me greatly.

I started using Nexthink in 2019. It was purchased by a previous company, and I received a two-day full-day training on it, and since then I have been using it.

Nexthink is stable in my experience, and in sizing, whenever we need extra sizing, the support has helped us.

Nexthink's scalability can handle growth and changing needs easily.

Customer support for Nexthink is helpful and supportive, and they help us with any request.

Nexthink was my first experience with these types of products in this specific area.

Nexthink is deployed in our organization using a hybrid cloud.

We use GCP for our deployment of Nexthink.

I did not purchase Nexthink through the Google Cloud Marketplace; I obtained it from Nexthink itself, and they helped us to host it.

I obtained Nexthink from Nexthink itself, and they helped us to host it.

Nexthink helps us significantly with ROI, reports, and visibility to management.

I believe the pricing, setup cost, and licensing for Nexthink are reasonable according to the current market prices.

Nexthink was my first experience with these types of products in this specific area.

I would rate Nexthink an eight out of ten because it is truly helpful, and not higher because it needs some improvement in the integration with our products that would benefit me in my work.

My advice to others looking into using Nexthink is to make a POC in the environment and see the return on investments at the beginning, and I am sure Nexthink will help them to choose it.

My main use case for Nexthink that we are currently working on is battery replacement and MS Office continuity.

For battery replacement with Nexthink, we check the battery cycles and based on the data we receive from remote action, we target those end users and they decide whether they have to replace the device or not.

For MS Office continuity, Nexthink helps us by having multiple applications associated with MS Office, and I will provide the example of OneDrive. In OneDrive, first of all, it checks the sync to determine whether the sync is working or not. If not, it initiates a restart. If that does not work, then we proceed with a reinstall and then sync again. If it is repaired, then it is resolved. If not, then a ticket is logged.

Nexthink has positively impacted my organization by reducing handle times, reducing ticket volumes, improving employee experience of software, workstation replacements, battery replacements, alerting users about password expiration, any upcoming changes, project changes, targeted campaigns, and more. There are multiple use cases that have benefited from this solution.

Regarding specific numbers, we have reduced around ten to fifteen percent of incoming volume via chats and calls overall, and apart from that, end users are able to help themselves using the chatbot, which accounts for around six percent.

The best features Nexthink offers, as of now, are Campaigns, Workflows which I find useful, and Remote Actions are also beneficial. Recently, we got hands-on with the virtualization module as well. I think all the modules are helpful, but it depends on the use case which we are working on.

Out of those features, I would say I find myself using Remote Actions the most or relying on it most heavily.

I think Nexthink should introduce longer character limits for remote session outputs and a better data repository to collect different files from end-user devices on a centralized storage. Apart from that, in workflow thinklets, there are some issues reported from time to time, so that needs to be addressed.

Customer support is one thing which needs to be improved; support team members are slow to respond, and they take a lot of time to get back to us, even if it is an urgent case. This is the thing which needs to be improved the most, and if the services are improved, then I would have probably given a ten.

I have been using Nexthink for around three and a half to four years.

Nexthink is stable. Everything is currently stable, and I have nothing to add on this matter.

Nexthink's scalability is sufficient; it is scalable enough for wider organizations. There are different towers that we can target with ample use cases in the library and custom ones.

Customer support is one thing which needs to be improved; support team members are slow to respond, and they take a lot of time to get back to us, even if it is an urgent case. This is the thing which needs to be improved the most, and if the services are improved, then I would have probably given a ten.

I have not used any other solution before Nexthink.

Before choosing Nexthink, I did not evaluate other options.

I have seen a return on investment with Nexthink. As I mentioned earlier, we have reduced volume, so that impacted the headcount and relates to money savings.

I have not used any other solution before Nexthink. Before choosing Nexthink, I did not evaluate other options.

To others looking into using Nexthink, I would suggest implementing Nexthink solution in the environment, assess where your environment is, and align use cases as per your requirements. Then you would definitely see an improvement if you are on the right track. My overall rating for this product is eight out of ten.

Main use cases have been campaigns and remote executions, either scheduled or manual, and Nexthink Query Language.

The best features Nexthink offers are the DEX scores and the ability to walk through an application that is on a browser.

The DEX scores help because they give an overview of how well an organization is doing across the industry compared to other organizations.

It helps to see what users are experiencing before they call the service desk.

In the past, when there have been issues that were global, it was easier to tell all users what the impact was and advise them not to call the service desk while we were working on the issue remotely.

The biggest limitation in features is the limited amount of metrics collected to use for Nexthink queries and investigations.

Nexthink can be improved by allowing collection of more metrics. For example, if there is the Print Spooler remote action, it would be helpful if the metric for the print queue was available when doing an NQL query to decide whether or not to run a remote action on a regular basis. Some of the metrics being collected are good, but they seem limited and are not as useful when running queries to decide whether or not to run a remote action.

There is a lot of improvement that can be made on the documentation side, the licensing side, and some of the backend side, including collection of metrics, ease of use to set up workflows, and more documentation on how to build custom remote actions.

I have been using Nexthink for around three and a half years.

There are no stability issues.

There are no scalability issues.

There are no customer service issues.

When Nexthink is implemented in a company, it should not be sold as just an IT tool. The people who support the applications need to be involved more. The tool can be adopted quicker and brought more broadly if the support groups of the applications are involved when it is purchased.

One of the biggest pieces of advice would be to purchase all the licensing needed to get the full functionality of the product. I would rate this review as a nine.

My main use case for Nexthink is improving digital experience for end users.

A quick, specific example of how I use Nexthink to improve digital experience for users is that we have a dashboard in place, so we proactively check what are the areas we need to improve upon, be it performance factors, endpoint factors, such as slow login, high boot time, application crashes, system crashes, and any network events where we have noticed latency.

These are the main observations about my main use case. Our objective is to improve our digital experience score, which consists of various factors as I mentioned, such as performance, endpoint scoring, and collaboration tools. We want to make sure that our tools are working seamlessly with minimal user impact, so that is how we track them with the help of Nexthink.

Nexthink has impacted my organization positively by helping us to a great extent, improving the end user experience in terms of enhancing device performance, reducing system crashes, and improving device reliability. Overall it has been good.

There are a variety of features Nexthink offers, starting with the ability to send campaigns to users, enable alerts for any specific application crashes or any network issues, and leverage proactive incident generation by integrating with ServiceNow for alarming issues such as system crashes or devices with low disk space. Another feature is creating remote actions, some of which are manual and reduce the manual effort of our engineers to fix a problem, while others can be automated and scheduled to run on an hourly or weekly basis across all devices. These actions not only capture information but also remediate issues, so if they identify an issue, a remote action will trigger at a scheduled time to fix it, so that the end user does not need to contact us to fix those issues.

The feature I find most helpful day-to-day is the digital experience dashboard, which gives us clarity or a holistic picture of how our devices are operating in our environment and how we can further improve it.

There are features such as remote actions, campaigns, and alerts, which are pretty good to use. Lately, we got Nexthink Assist, which helps us investigate as a layman; you just need to write your query in Assist, and it generates the investigations for you, so it is an AI which is pretty useful.

I think Nexthink can be improved to bring deeper investigations; for example, Nexthink does not give us the exact solution, but it provides what it sees on the device during that time frame. If Nexthink also has the capability to provide us with solutions, such as suggesting to run a disk cleanup or look for a particular folder to remedy a problem, that would be really helpful. If Nexthink Assist can be empowered more to identify and remediate on its own, that would be useful.

Regarding improvements needed for Nexthink, I would like to leverage software licensing reporting, but it requires a lot of manual intervention to feed in all that data, such as determining what kind of license is a perpetual license or what enterprise license. In that context, some improvement is required.

The reason I chose an eight is because there are still areas to improve, and not many people are fully aware of the capabilities of Nexthink. With the recent introduction of Assist, it does give people the ability to use it more easily, but some enhancements can be made to make it more user-friendly.

I have been using Nexthink for four and a half years.

Nexthink is stable.

The tool's scalability works fine; we rarely see any outages with Nexthink, so it performs well and is pretty stable.

Customer support is okay; it is fine and I do not face many challenges with the support, as it is good.

I used ControlUp in my previous organization before using Nexthink.

I definitely see a return on investment with Nexthink as it helps in the reduction of incidents, thus saving manpower. We can also see the reliability in the devices, helping us identify which device will be end of life and which devices can continue to work, leading to potential savings for us.

My advice to others looking into using Nexthink would be that it is a go-to solution if you want a proactive analysis of your infrastructure to ensure the scalability and reliability of your infrastructure; you should choose Nexthink. I would rate this review an eight.

I have not developed a practical use case because my experience with Nexthink was limited to certification training. I worked with some features during my training, but it was planned education rather than practical application.

Nexthink is a complete package where you can dive deep into how applications and IT infrastructure are working. The visual presentation is better than other products I have explored, so I really appreciated using Nexthink.

When I reflect on my experience, I remember that it was more intuitive to work with Nexthink compared to other solutions.

I am unable to provide recommendations on how Nexthink can be improved because I did not engage in any actual practical work with the platform. My experience was limited to certification training.

I used Nexthink approximately two and a half years ago, though it has been about two years since I had any experience with the platform.

I am unable to assess whether Nexthink is stable based on my experience during certification or training.

I cannot recall information about Nexthink's scalability from what I learned during certification or training.

I do not recall how Nexthink's customer support operates based on my training or any experience I may have had interacting with them.

I have worked with several solutions including AppDynamics, though this experience was also limited to certification training.

I did not receive any insights into pricing, setup cost, and licensing during my certification or training.

I did not have an implementation team involved in my experience with Nexthink.

I have not seen a return on investment from Nexthink, as I cannot share any relevant metrics from my training or certification experience.

I did not receive any insights into pricing, setup cost, and licensing during my certification or training.

Nexthink was the only platform evaluated as part of my training, with no other options considered.