Devices being flagged as non-compliant (even with required apps)Solved

Participant
Discussion
1 day ago Apr 16, 2026

Hey guys, could use some help here. A bunch of our iPads are getting flagged as non-compliant in the portal. The weird thing is, they definitely have the 3 required apps installed, so application compliance shouldn’t be the issue. 

I was looking through our compliance config and I’m wondering if it’s the passcode requirement tripping it up. Should I just remove the password rule from the list? Anyone run into this?

Replies (1)

Marked SolutionPending Review
Hexnode Expert
19 hours ago Apr 16, 2026
Marked SolutionPending Review

Hi @timo-liam, you’re likely on the right track with the passcode rule. A device will get flagged as non-compliant if it fails any rule in your active policy, even if the required apps are perfectly installed. 

To be 100% sure that’s what is causing it, you can check the exact reason on a specific device: 

  1. Go to Manage and click on one of the affected iPads. 

  1. Head over to the Device Summary tab. 

  1. Check the Compliance Info section—it will tell you exactly what triggered the flag. 

If it says “Device is not passcode compliant,” it just means those iPads don’t currently have a passcode set or that they do not meet the passcode requirements defined in the password policy, and Hexnode is flagging them to enforce your policy. 

To fix it, you basically have two options depending on how you want to manage these devices: 

  • Option 1: If these iPads don’t actually need a passcode, you can just edit the policy (Manage > Policies > Modify) and uncheck the passcode compliance requirement. 

  • Option 2: If your security setup requires passcodes, you’ll need to set one on those devices to get them back into a compliant status. 

One last tip: While you are in the policy settings, take a quick moment to cross-check other compliance criteria (such as “Encrypted” or other “Application Compliance” rules) to ensure no other settings are inadvertently flagging your devices. 

We’ll double-check this specific case on our end if you submit a ticket, but adjusting that policy based on the options above should resolve the immediate inconsistency for you! Let us know if you have any more questions. 

Save