What is your primary use case for Nexthink?

My main use case for Nexthink is to manage the endpoint devices, run remote actions on the devices, and check the performance of the devices in our organization.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.

I have been using Nexthink for the last three years.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.

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.

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.

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.

My main use case for Nexthink is access remote control. I use Nexthink for remote control in my day-to-day work by searching about the user ID, finding their desktop, and sending the request to remote their access.

I mainly use Nexthink for end-user device monitoring, which includes desktops, laptops, or any virtual devices, focusing predominantly on virtual desktops. The agent is deployed on these devices to monitor applications, and it is primarily used for AI operations.

The primary use case of Nexthink is for IT service management and ticket time reduction. We use it to get real-time data, as Nexthink provides data in real-time with a maximum delay of five minutes.

We use the product to analyze systems and devices through the console, identify issues affecting the environment, and provide proactive support to prevent these problems. It helps us investigate and analyze frequent VSODs, memory utilization, and CPU usage.

We use the solution for compliance and experience scoring.

I use Nexthink to monitor application crashes of processes or how the device works in our environment. We monitor more than 1,00,000 devices in our company with Nexthink. Our company also creates campaigns and helps create campaigns for some end users of Nexthink. If sometimes a user runs low on space, in our company, we send an automated notification with the help of the tool asking them to delete some files from their device, along with the ability to send some scripts as well. In our company, we can use Nexthink to monitor the performance of applications and send some PowerShell scripts to check whether the services are running. You can perform an investigation if sometimes something is not working fine. Without taking remote access, you can capture all the logs from a particular application in the back-end to see how it behaves and what applications. Sometimes, you can see what is wrong or enhanced with the solution's taskbar before collecting all the data from this tool.

This solution is for end users. If the end user is using a laptop and they face any issues on a daily basis such as their browser not working or Outlook running out of memory, this solution helps with the upgrading of capabilities. It has AI capabilities that automatically detect problems before the end user becomes aware of them. This product is suitable for small, medium and large companies because the way it is designed.

We mainly use Nexthink as a help desk tool for individuals, level one support, and responding to whoever complains from his PC.

We have Nexthink for end-user devices. Nexthink is a client that monitors end-user devices for what's happening with them. We are using its latest version. This is a subscription-based solution, and we upgrade it all the time.

Nexthink is a product for end-users to collect, monitor, report, and analyze information about their IT infrastructure. We recommended it to a customer who wanted to monitor all the end-user infrastructure. Nexthink was a good fit because it allowed them to monitor security and report on the infrastructure from all end-users at all of their branches. Many customers our customers have multiple branches.

We are using Nexthink for proactive monitoring of the performance of services on our endpoints. We are using the on-premise version but we will be moving to the cloud in the near future.

The use cases are based on transformation projects. For example, if clients are trying to implement some new deployments in SCCM, they use this solution and we help them with the migration. We are currently helping with a Windows 10 migration. Clients use it for application and system crashes in order to maintain the compliance status for their business applications. On individual machines, we can see the performance and what is going wrong as well as what can be improved in order to enhance the performance of the machine. This is very useful when we get any queries from a VIP user or someone from our project's top management. So if they get into any trouble, then we are able to fix it as soon as possible. Because if an agent is unable to work for two hours or even for two days, that won't make much big of an impact. Whereas, if someone from higher management is unable to work on the system for about two hours, then they would lose a lot. Initially, we were just looking at it in order to maintain compliances, and we were using it only for that. The guy managing this tool before me was more or less concentrated on device compliances. Later on, we started getting into the application and system crashes (when I started). In our environment, we need to put a proxy server in place. Currently, devices are connected via the corporate network or the VPN. We don't have machines reporting from the open network. This is something that we are working on. Once that is in place, we will get all the machines reporting in our environment.

We use Nexthink to give us information on events on end-user laptops. We turn that into several use cases, such as more intelligent hardware refresh purchasing, and we have established a proactive support model. But really, it's about understanding the digital experience by creating a digital experience score and using that score to create a happier and more productive employee base. We're still quite young in that respect, but we're in the process right now of creating a customer experience analytics team, whose job it will be to measure and enhance the digital experience score. We deploy it on-premises. We have a number of virtual machines within our environment that host the Nexthink engines. The laptops have a collector, a small agent that's very lightweight, that sends information up to the engines.