iPad policy assigned but not applying on one deviceSolved

Hi @ed_evans ,

If the policy is visible under the device but the configurations are not taking effect, first confirm that the device is checking in successfully. A successful remote restart or sync generally indicates that the device still has communication with Hexnode.

In this situation, try refreshing the policy association:

1. Open the affected iPad in Hexnode UEM.
2. Go to the Policies sub-tab.
3. Remove or disassociate the affected policy from the device.
4. Wait for the change to sync.
5. Associate the same policy with the device again.
6. Trigger a device sync or allow the device to check in.

This can help when the policy assignment is shown in the portal, but the device has not correctly processed the policy payload.

Regards,
Isabel Lora
Hexnode UEM

I had already restarted the iPad and synced it manually, but that didn’t help. Removing the policy and adding it back again worked. The policy applied right after that.

That behavior usually points to a policy synchronization mismatch rather than a connectivity issue, especially if remote actions and manual syncs are working.

For future cases, the recommended order is:

• Verify the policy is listed under the device.
• Confirm the device can receive commands or complete a sync.
• If the policy still does not apply, remove the policy association and add it again.

If the issue keeps recurring across multiple iPads or multiple policies, review whether the devices share the same enrollment state, supervision status, and policy priority. But for a single affected iPad, re-associating the policy is a valid workaround.

Regards,
Isabel Lora
Hexnode UEM