sure, 60 min as default, then i changed it to 20 min ... same
how can I troubleshoot Device classification issues on end user?
What is the correct form of troubleshooting Device classification issues ?
@maxkor the devices page should include details on when the Device Classification changed similar to:
From there, we can look at the client logs to see which checks are failing. The logs will reflect individual checks and their success or failure with entries similar to:
Success:
deviceId Disk encryption check: name bitlocker, status 1
Failure
deviceId Disk encryption check: name bitlocker, status 0
perfect!!
nsdebuglog.txt is it the file ?
@maxkor ,
That is correct. The log entries should exist in the nsdebuglog.log file. If you have custom labels or some of the newer checks for OS versions and Anti-virus/EDR then you may find that the logs vary a bit but will still be in that file.
@maxkor ,
That is correct. The log entries should exist in the nsdebuglog.log file. If you have custom labels or some of the newer checks for OS versions and Anti-virus/EDR then you may find that the logs vary a bit but will still be in that file.
OK , thank you.
I’m don't find in the log these lines
Same here - I am having a hard time troubleshooting device classification errors. Is there a documentation for each OS where to look exactly when a device is classified as unmanaged? I want to understand which check fails? At least for Macs, I cannot find any checks done in nsdebuglog.log?
Same here - I am having a hard time troubleshooting device classification errors. Is there a documentation for each OS where to look exactly when a device is classified as unmanaged? I want to understand which check fails? At least for Macs, I cannot find any checks done in nsdebuglog.log?
example: from my log file
nsUtils From Registry - Windows Edition: Windows 10 Enterprise BuildVersion:22631 >> thats the OS
2024/10/18 10:28:30.976 stAgentSvc p18a4 t393c info osUtils.cpp:892 nsUtil isAVRunning check
2024/10/18 10:28:30.998 stAgentSvc p18a4 t393c info osUtils.cpp:993 nsUtil AVRunning status: 0 >>0 mean failed and 1 means Success.
Hopefully this helps!
IF you cannot find the below snippet of text in the nsdebuglog.log, it is because there is a backend flag enabled which encrypts the device management logs so it is unreadable.
I had the same issue and it made troubleshooting extremely difficult for the helpdesk teams. I have raised a Netskope idea to get this information present in the Netskope admin portal.
Success:
deviceId Disk encryption check: name bitlocker, status 1
Failure
deviceId Disk encryption check: name bitlocker, status 0
Badges Winner
Davide Molinohas earned the badge Content Contributor - 5
Davide Molinohas earned the badge Content Contributor - 1
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! By registering, you agree to our Terms and Conditions available https://www.netskope.com/terms-of-use Create an account.