Android BYOD Profile Owner enrollment installs Hexnode UEM instead of Hexnode for WorkSolved

Participant
Discussion
2 months ago May 27, 2026

Hi everyone. We are enrolling personal Android devices as BYOD (Profile Owner) so users get a work container. However, during enrollment, users keep downloading the standard Hexnode UEM app instead of Hexnode for Work. This stops the enrollment flow because the work profile does not get created correctly.

Is there a way to make Hexnode automatically install or push Hexnode for Work to the device so users don’t manually install the wrong app?

Replies (1)

Marked SolutionPending Review
Hexnode Expert
2 months ago May 27, 2026
Marked SolutionPending Review

Hello,

Thanks for reaching out to Hexnode Connect.

Currently, there is no way to automatically push the Hexnode for Work app to an unmanaged personal device before the enrollment process begins. Because the device is user-owned and not yet managed, the user must initiate the process by manually installing the correct app.

To clarify the difference between the apps:

  • Hexnode UEM is used for Android Enterprise Device Owner (fully managed) enrollments.
  • Hexnode for Work is strictly used for Android Enterprise Profile Owner (BYOD) enrollments to securely create and manage the separate work profile container.

The most practical workaround is to update your internal enrollment instructions to be very explicit. We recommend providing users with the exact app name (Hexnode for Work) or a direct app store link, and specifically advising them not to install the standard Hexnode UEM app.

Once the user completes the enrollment through the Hexnode for Work app, the Android work profile will be successfully created, and you can begin deploying approved work apps into that container.

I hope this helps clarify the BYOD enrollment flow. Feel free to reach out if you have any more doubts or need further assistance.

Best regards,
George,
Hexnode UEM

Save