Yes @diane_. If a policy is directly associated with the individual device, that policy can remain applied even after the device is removed from the device group.
The key point is how the policy is targeted:
- If a policy is applied only through the device group, removing the device from that group removes that policy association from the device.
- If the same policy is also directly associated with the device, the policy remains targeted to the device even after it is removed from the group.
- Any separate policy that was directly assigned to the device and not tied to the group should also remain applied.
Recommended workaround:
- Identify the policies currently applied to the device through the device group.
- Go to Policies in the Hexnode portal.
- Open each required policy.
- Go to Manage > Associate Targets, or open the policy, click Modify, and go to Policy Targets.
- Add the individual device as a target under Devices.
- Save the policy.
- After confirming the required policies are directly associated with the device, remove the device from the device group.
This way, the policy configurations remain applied because the device is still an explicit target. It is best to validate the workflow with a test device before making the same change for production devices.
Best regards,
Isabel Lora
Hexnode UEM