Need to keep Android demo phones passcode-free, but compliance says noSolved

Participant
Discussion
1 week ago

Hey everyone,

Quick one, we have Android demo phones deployed in a big mall. They’re tethered to security tags, so we don’t want any passcode or password set (staff need quick access for demos).

But the devices keep showing “Device not compliant”. Is there a way to exempt these demo devices from the compliance policy without affecting the rest of our fleet?

Replies (3)

Marked SolutionPending Review
Participant
1 week ago
Marked SolutionPending Review

Hey @yuudai ,

Demo devices are a special case. If your compliance policy enforces a passcode, any device without one will be flagged as non-compliant.

One option is to create a separate policy or device group for the demo units, so you can relax the passcode rule just for them. That way, your production devices stay secure while the demo phones remain passcode-free.

Marked SolutionPending Review
Participant
1 week ago
Marked SolutionPending Review

Thank you for the suggestion, @porter .
But in our case, we don’t want to create a new policy, and these demo units are actually the only Android devices we manage. So, we’re hoping for another way to handle this.

Marked SolutionPending Review
Hexnode Expert
1 week ago
Marked SolutionPending Review

Hello @yuudai ,

Thank you for reaching out. Just to clarify, the passcode compliance check only applies if a passcode policy has been associated with the device. You can either remove the passcode policy, or if you wish to keep it and still avoid the compliance message, follow the steps below.

  1. Log in to your Hexnode UEM console.
  2. Go to Policies > Compliance Policies.
  3. Next to your Default Android Compliance Policy, click Edit Policy.
  4. Under Basic Settings, uncheck the option Device is not password compliant, which enforces the passcode requirement.
  5. Click Save.

This will stop those demo devices from being marked as non-compliant.

Please feel free to reach out if you encounter any issues.

Cheers,
John Cooper
Hexnode UEM

Save