We’ve configured a password policy requiring uppercase letters, but the user set a password without any uppercase. The device still shows as compliant. Even after restart and re-login, no prompt to change the password. Any idea why?
8 Views
Replies (2)
Marked SolutionPending Review
Participant
5 days ago
May 21, 2026
Marked SolutionPending Review
Yeah, seen something similar. Just setting complexity rules alone doesn’t always force an immediate compliance check on macOS.
Marked SolutionPending Review
Hexnode Expert
5 days ago
May 21, 2026
Marked SolutionPending Review
Hi all!
@ame-lie, what’s happening here is tied to how the compliance status gets evaluated in the portal. The system updates and reflects non-compliance only when one of the following conditions is configured:
-
No passcode is set on the device
-
“Change passcode at next login” is enabled
-
Passcode age is configured
To make sure the device is marked non-compliant and the user is prompted to update their password, enable “Change passcode at next login.”
Best Regards,
Isabel Lora
Hexnode UEM
Save
