What problems is Nexthink solving and how is that benefiting you?
The core problem Nexthink solves for us is closing the gap between seeing an issue on our endpoints and actually fixing it, at scale, without touching machines individually. We manage a fleet of Windows workstations, both physical and virtual, and before Nexthink that work was spread across a mix of tools like SCCM, Intune, and GPO. That meant stitching together several systems and often still remoting into hosts one at a time to run scripts by hand, hoping we caught every affected machine. Now we detect state and remediate it programmatically across the whole estate from one place.
Concretely, we've used it to automate things that used to be painful manual jobs. We deregister retired devices from Autopilot automatically instead of clicking through the portal. We keep application packages current on our AVD session hosts by having workflows download, verify, and swap them in on login, with integrity checks and rollback so a bad download never leaves a machine broken. We check connectivity and agent state, validate configuration, flatten group membership for access management through Graph API calls, and remediate drift, all as automated workflows rather than one-off scripts. Because a workflow can chain Remote Actions, branch on their output, loop, and call external APIs, we can build a process that adapts to what it finds and acts on it end to end.
The benefit shows up in a few ways. The obvious one is time. Jobs that took an engineer hours of investigation and hands-on remediation now run on their own and finish consistently. The less obvious one is reliability. Automated workflows do the same thing every time, so we've cut out the human error that creeps in when you're doing repetitive fleet work manually. And the real-time endpoint visibility means we can catch and diagnose intermittent problems that would otherwise be gone by the time a user files a ticket. For a small team, that combination lets us cover a lot more ground than our headcount would normally allow, and it's shifted us from reacting to problems one machine at a time to solving them across the fleet in a single, repeatable process. Review collected by and hosted on G2.com.