Android device still shows original policy after assigning cloned test policySolved

Hello,

Thanks for reaching out to Hexnode Connect.

This usually happens when the policy is still being inherited from another assignment source. In Hexnode, assigning a cloned policy directly to a device does not automatically remove the original policy if it is still being applied at a higher level. A device can receive the same policy through multiple associations, including:

• Direct device assignment
• Device group assignment
• User assignment
• User group assignment

To find out exactly where the policy is coming from, open the device details page and check the Policies tab. It will list the source for each policy. To completely isolate your test tablet, you will need to address the group and user assignments:

1. Device Group Assignments

If the original policy is assigned through a device group, removing the test device from that group will stop it from inheriting the policy.

(Note: If the device is part of a Dynamic Device Group, it may automatically rejoin the group upon the next sync. In that case, you must either update the group criteria or add a specific exclusion for the test device).

2. User Assignments (The “Default User” Case)

Often, organizations assign all devices to the same default user during enrollment. If your devices share a default user, the test tablet will continue to inherit any policies associated with that user. To isolate it, you must assign the device to a separate owner:

1. Navigate to Manage > Users and create a new local user specifically for testing.
2. Navigate to the Manage tab and click on your test Android tablet to open its device details page.
3. Click on Actions > Edit > Change Owner.
4. Select the local domain and assign the newly created test user as the owner.

Once you change the owner and remove it from the associated groups, the original policy will drop off, and the tablet will only use your cloned test setup.

I hope this helps or resolves your issue. Feel free to reach out if you have any more doubts or need further assistance.

Best regards,
George,
Hexnode UEM