Several Android devices are showing as out of compliance under the Default Android Compliance Policy. The confusing part is that when I open the compliance alert, there are no violations listed for those devices.
As far as I can tell, the devices are actually compliant. Is there a way to force Hexnode to recheck compliance instead of waiting for the status to update on its own?
30 Views
Hi @jayceon,
You can force a compliance recheck by initiating a Scan Device action on the affected Android devices.
To do this:
If a device is shown as out of compliance but the alert details do not list any active violations, the status may not have refreshed yet after the device became compliant. Running a device scan prompts Hexnode to fetch the latest device state and re-evaluate compliance.
Regards,
Sienna Carter
Hexnode UEM
I tried Scan Device on a few of them. Two devices changed back to compliant, but the Scan Device action still shows as Pending on several devices. Does Pending mean the scan is not working?
Hi @jayceon,
A Pending status for Scan Device usually means the command has been queued but the device has not completed processing it yet. This can happen if the device has not checked in recently, is offline, has limited network access, or is temporarily unable to communicate with the UEM.
If some devices became compliant after the scan, the action is having the expected effect. For the remaining devices, wait for the next device check-in or make sure the devices are powered on and connected to the internet. Once the scan is processed, the compliance status should update if there are no actual violations.
Regards,
Sienna Carter
Hexnode UEM
Don't have an account? Sign up
What's new 
