As we expand out the number of devices running the Netskope client, we are seeing a percentage of devices that have issues where it appears that the client is enabled, but has not communicated in days. we generally see this after an automatic update. Has anyone else run into this? What processes do admins use for monitoring the health of the Netskope agents and ensuring that they are Enabled and reporting correctly.
+6
I would recommend starting with API queries. You can easily pull a list of clients and filter for those that have not had a status change in a given time period. From there, you can see the user name and machine information and address it accordingly with the endpoint tools available to you or by direct action at the machine.
Yes, I think we are missing a critical piece with the Netskope Client. Clients should at least report in daily and log into the portal that it is healthy. There is no real way an admin can check if devices have fallen off as both healthy/not healthy devices don't check in for weeks at a time.
Reply
Login to the community
If you haven't already registered, now is a good time to do so. After you register, you can post to the community, receive email notifications, and lots more. It's quick and it's free! Create an account
Login with SSO
Employee Partneror
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.