A running Netskope Client service does not necessarily mean that traffic is being steered as expected.
Administrators may see the agent/services running normally while the client is not effectively steering traffic due to conditions such as:
- Enrollment or token issues
- User not included in the applicable steering configuration/group
- Client disabled
- Other user-specific enrollment or client-state issues
To improve visibility, we are leveraging: nsdiag.exe -f
which return the result ; Client status:: enable./disable
We collect this result through our endpoint/client management custom inventory and create a report showing the actual reported client status across managed endpoints.
