What advice do you have for others considering Nexthink?

For specific metrics, I have avoided 10,000 tickets in six months. This usage has resulted in considerable time savings, money savings, and reduced employee hassle since investing in Nexthink.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 advice for others looking into using Nexthink is to look at the pricing, negotiate for better deals, and plan for adequate support, which should help in getting timely and accurate assistance. I would rate this review an 8 overall.

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.

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 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 advice for others looking into using Nexthink is that they should use it to make their work faster. Nexthink saves a lot of time. I would rate this product a 9 out of 10.

I rate Nexthink ten out of ten. Although there is room for improvement regarding monitoring user sentiments, it is not a significant issue.

Overall, I would recommend Nexthink as a first priority and rate it ten out of ten.

I would recommend Nexthink for its monitoring and proactive support capabilities. I rate it a ten out of ten.

If you want to integrate with ServiceNow, for instance, it'll be more work. Nexthink can support home use and promote its advantages, even on local networks. This enables us to gain insights into Wi-Fi or home network setups, allowing us to assist phone users in improving their setups. I recommend the solution as it enables using Nexthink across various services, preventing the concentration of knowledge in one person or small team. This spreads the benefits of Nexthink throughout the entire company. Overall, I rate the solution a nine out of ten.

There is a different team consisting of seven to eight people, a mix of engineers and administrators in my company, who maintain and upgrade the application. I recommend the solution to those planning to use it. Nexthink provides its users with a very good point of overview and presentation. There are many benefits of Nexthink since it allows a person to check in seconds which applications are running or if there are any crashes, thereby giving a good overview to the user that can be helpful during troubleshooting. Instead of connecting to a tool remotely, from Nexthink itself, you can see what works fine. I rate the overall solution a nine out of ten.

I would rate the product an eight out of ten. We have enterprise clients for the tool. The solution is recommended for enterprises and not for small-scale customers.

I would recommend carrying out due diligence in the environment where they're going to deploy the solution. This will provide them with key information about the product suitability. I would rate this solution an eight out of ten.

I would rate Nexthink an eight out of ten.

It is a very good solution. We're satisfied with Nexthink. You just need to try it out. It works well. It has a couple of competitors, and you should just see which one suits you more. I would rate it an eight out of ten.

I would recommend this tool to anyone considering getting it. This tool will work within your environment to help reduce the number of incidents and problems within the environment. I would rate this solution a ten out of ten.

I rate Nexthink eight out of 10. I think Nexthink is a good product, but there are some issues with API integration of devices from vendors, such as VMware, Microsoft, and Dell EMC. If you are thinking of adopting Nexthink. I recommend studying the documentation and all the other materials. The more familiar we are with this product and its features, the more we can recommend it to our clients.

I would recommend the cloud platform. The on-premise solution we are using will be phased out at some point. I rate Nexthink a seven out of ten.

Whatever you investigate, don't keep it on Nexthink Finder. Only put it on a dashboard so it is always available whenever you want it. If you want to save time and reduce some effort for whatever you are investigating or whenever you create a tag/category, just put it on a dashboard so you can just fetch the data and run with it. It is currently mandatory for our compliance management. If you don't manage the compliance, updating your compliance's baseline threshold, then you might lag behind. This might have an impact on production. After managing the applications, we knew that there was one application that needed to be upgraded. Once that was upgraded, it made some improvements in the bandwidth usage. We are not using the Act or Engage modules yet. That is still in discussion with the client. I have been working on it for quite a time now, so I know what scores are based on what thresholds, e.g., what parameters this particular score is being derived with. So, I quickly look at those parameters and the performance of those particular parameters only. We are doing this on a weekly basis and only have analytics. Therefore, we have a lot of missing due to the absence of Act or Engage. The drill-down is the thing that we have to do, which takes a lot of time. With the help of Act and Engage, it is possible to send some surveys to users. You can create some parameters and put in conditions. For example, if a user reaches an overall device usage of more than 80 percent, you can push the survey to that particular end user asking, "Your device has reached 80 percent of its overall system usage. Would you like a system cleanup?" There, you can put in "Yes" or "No". If the user says, "Yes," then Nexthink can implement that action. If "No," then you can put in further questions asking, "Do you want us to give us to do it a little later?" or "Will you do it on your own?" The analytics are as perfect as they can be. They keep on improving them with every version upgrade. They keep on adding new fields. If they want to retire something, then they do. I don't think the analytics need any improvement because they have improved a lot with the implementation of Act and Engage. Act and Engage puts it on the next level. We are moving forward with the cloud sometime in the next couple of weeks. Our longer-term strategic vision for Nexthink is in sync with where our IT department is headed. Apart from me, the IT guys are using it on a daily basis. Our vision is that we wouldn't need anybody for tech support. We can reduce the strength of the OSs folks, who wouldn't have to worry about troubleshooting on the endpoint until it was a hardware problem. Everything on the software and system, we should be able to fix it remotely. So far, we have not been doing this because everybody is not there on the system due to the open networks problem. Once that has been fixed, anything related to software would come to us only. The OSs folks have a lot of other things to deal with, such as logistics, asset management, allocations, etc., but they should only deal with hardware problems, not software. I would rate Nexthink as 10 out of 10.

Overall, it has helped save us time. You have to make a time investment to get the skills within your organization to make best use of the tool. My recommendation is that if organizations want to take digital experience management seriously, they need to have people in place whose job it is to do that. You do have to make that type of time and financial investment. But we have saved time using Nexthink. We're actually in the process right now of building the team, those dedicated people, around it. We spent the last two to three years doing it as more of a side-of-desk activity. We've managed to achieve what we've achieved just with that. By putting people in place to do it, we're going to be able to achieve much more, and actually tie some process around it to make sure that we're measuring the value by time and money. If you are implementing Nexthink, make sure that you've got people who are able to take ownership of the tool internally, who will be its internal ambassadors, and spend the time to learn the tool to make sure that you do it right. Don't look at the tool as a siloed operation. Don't only look at it from the point of view of improving your security or your end-user computing team, or your service desk. Look at the bigger picture. There are tons of use cases for Nexthink. It often comes down to only being limited by the ideas you can generate. There's a lot in there. The people who are going to use the tool on a day to day basis should go through the Nexthink Academy and learn as much as they can there. They should also pay attention to the Nexthink Library, to understand what out-of-the-box packs are available there. For us, the lessons we've learned are less about Nexthink and more about experience management. Nexthink is one of the major tools we're using in our experience management strategy. The mistake we've made from the experience management perspective is not having a senior owner of experience, like a chief experience officer. That's really been a mistake because we have had no unity across IT, or enabling functions. As a result of that, we've had lots of different people doing lots of different things. You need a senior-level owner and you need a strategy. Those are really our two lessons learned. At the moment, we've got a strategy, and we have people at the senior level who want us to do great things with it, but we still don't have a senior owner of experience, which is where Nexthink does its best work. We use it across Windows and Mac machines. The Windows collector can do a lot more than the Mac. However, each new version that Nexthink releases brings Mac closer to parity with Windows. We don't use it on mobile and we have limited use across different types of applications. For example, we're not really using it to its max potential for SaaS products right now. But if we move to the cloud product, which we would like to do, then we'll make better use of it, at that point, for SaaS solutions. Nexthink provides you with real-time and actionable insights into the IT experience of all employees, but you need to make sure you've got people with the requisite skills to interpret that. There are the two types of data: the hard data and the soft data. You have the events coming from the machine, and then you've got more of the sentiment-type stuff where you're engaging with your customer base to hear what they have to say. Nexthink comes with a digital experience score out-of-the-box, but we have found that we are having to optimize that for our environment to get a score that actually represents what the user is experiencing. It provides analytics for detailed event data to help you pinpoint issues and find the root cause. However, the basic analytics won't necessarily tell you the solution. They will tell you what's going on, but you still need to find a solution. Nexthink do have playbooks in their repertoire that give you recommendations for what the solution may be, but we're not using those right now. We do have some involvement with the solution's AI-driven insights, but we haven't really achieved many great successes with it just yet. That's an area that we're still exploring. We're looking a lot at the AI-driven, proactive and predictive support elements. I struggle to say 10 out of 10, because that seems almost impossible for any company. But, yes, I would say it's a 10. They've got the people and the culture within the company. They are growing and are ambitious and they're very focused on product enhancements. They listen to the customer, and they will develop the tool, generally speaking, in the way that the customer wants. They are adaptable to our operating model. The tool itself does tons of stuff.