This is a fantastic question and a very common concern when managing devices at scale. The short answer is: No, the app will not re-download. Hexnode operates on a declarative architecture using a concept called Idempotency. In simple terms, idempotency ensures that applying a configuration multiple times results in the exact same target state without causing redundant downloads or repeated actions.
Because you are using a Required Apps policy (rather than a one-time script), Hexnode automatically handles this logic for you:
-
Drift Detection: When you save the policy with the new Wi-Fi password, Hexnode does trigger an evaluation across the 5,000 devices.
-
Comparing States: The Hexnode agent on each endpoint cross-references the “Desired State” (what the policy mandates) against the “Live State” (what is actually on the device).
-
The Delta Execution: Hexnode checks the app’s internal manifest (the Bundle Identifier and Version Number). If it sees that com.company.fieldapp Version 2.0 is already installed, it completely ignores the app payload and only pushes the updated Wi-Fi payload.
Pro-Tip for macOS/Windows: To make this process even more bulletproof on desktop operating systems, you can define exact Success Criteria within the policy. You can tell Hexnode to verify the installation by checking if the specific Bundle ID exists or if the executable file is present at a specific directory path (e.g., /Applications/Microsoft Teams.app).
So go ahead and update that Wi-Fi password with confidence! Only devices that are missing the app will trigger a download.
10 Views
