Policy vs Automate for app installation in Hexnode: when to use eachSolved

Participant
Discussion
2 months ago Sep 28, 2026

I’m setting up app deployments in Hexnode for macOS and iOS devices and I’m confused about the difference between installing an app through a policy and installing it through Automate or a remote action. Both seem to push the app to devices, so when should one be used over the other?

Replies (1)

Marked SolutionPending Review
Hexnode Expert
2 months ago Sep 28, 2026
Marked SolutionPending Review

Hi @harold,

The main difference is enforcement.

Required Apps policy is used when the app must remain installed on the targeted devices. Hexnode continuously checks the policy target and enforces the app installation. If a device is newly added to the policy target, the app is deployed to that device. If the app is removed from a managed device, Hexnode attempts to install it again.

This is best for required apps such as business tools, security apps, VPN clients, or any application that should always be present.

Automate or Remote Action > Install Application performs a one-time app installation command based on the workflow or action you run. It deploys the app at that moment, but it does not continuously enforce the app afterward. If the app is later removed, Hexnode will not reinstall it unless the automation runs again or another install action is triggered.

This is better for one-time deployments, onboarding workflows, conditional app pushes, or non-mandatory applications.

Regards,
Sienna Carter
Hexnode UEM

Save