Hi @pepijn,
Assigning multiple policies to the same device is supported in Hexnode. The final behavior depends on the type of configurations included in those policies.
In general:
– If the policies configure different items, they are applied together.
– If there is a conflict between restrictions, the most restrictive setting is enforced.
– For settings where only one value can be active, the most recently applied or updated configuration may take effect.
However, assigning two very similar policies can become difficult to manage and may lead to unexpected behavior if both policies contain overlapping payloads.
In your case, the app deletion during testing is likely related to the Required Apps setting called “Remove App on Policy Removal.” If this option is enabled, Hexnode removes the app when the policy that installed or managed it is removed. Since the cloned policy still contains the app, it may then reinstall the app again.
To avoid app removal when disassociating a policy, disable “Remove App on Policy Removal” for the app under Required Apps and save the policy before removing the policy from the device.
Regards,
Sienna Carter
Hexnode UEM