Android File Management policy leaves folders after disassociationSolved

This is the current expected behavior for folders created through a File Management policy. When a File Management policy is removed or disassociated from a device, Hexnode removes the files deployed through that policy. However, the folder created by the policy is not automatically deleted from the device. At the moment, cleanup of those folders needs to be done manually. For individual devices, you can use the File Explorer option in Hexnode to browse the device storage and delete the leftover folder if it is no longer required. For fleet-wide cleanup, automatic removal of empty policy-created folders after policy disassociation is not currently available. This has been treated as a feature requirement for product evaluation.

That explains what I’m seeing. The files disappear, but the folder stays empty. Manual cleanup through File Explorer works for one device, but it’s not really practical when the same policy was applied to many devices.

Yes, that is the main limitation with the current behavior. File Explorer can help with one-off cleanup, but it is not a scalable replacement for automatic folder removal across multiple managed devices.

The reusable takeaway is:

• File Management policy removed/disassociated: policy-deployed files are removed.
• Folder created by that policy: remains on the device.
• Current workaround: delete the folder manually using File Explorer on the device record.
• Automated cleanup of empty policy-created folders: not supported currently and would require a product enhancement.

If automatic folder deletion is introduced in a future release, it would likely need to account for cases where the same folder may contain files not deployed by the policy.