Has anyone managed to enroll a Meta Quest 3 with Hexnode? I found a few references suggesting it might be possible because the headset is Android-based, but the information is scattered and I haven’t been able to make much progress. Looking for the best supported approach, or at least whether there is a workable enrollment method.
Can Meta Quest 3 be enrolled in Hexnode UEM?Solved
Replies (3)
Hello @leo_scott ,
Meta Quest and other Android-based VR headsets are not officially supported by Hexnode UEM at this time. Hexnode’s officially supported immersive endpoint platform is currently visionOS for Apple Vision Pro.
Since Meta Quest runs on an Android-based operating system, some administrators have attempted to test enrollment by installing the Hexnode for Android TV app on the headset. However, this should be treated only as an experimental workaround.
Important limitations to keep in mind:
- Meta Quest enrollment is not a validated or officially supported deployment method.
- Hexnode cannot guarantee successful enrollment or stable device administration on Meta Quest devices.
- Core management features such as kiosk lockdown, remote actions, policy enforcement, and app management may fail or behave unpredictably.
- Device admin permission prompts and enrollment behavior may differ from supported Android or Android TV devices.
If the goal is production management of Meta Quest devices, there is currently no officially supported Hexnode enrollment path. If you are only testing, you may try the Android TV app route, but it should not be considered a reliable management solution.
Regards,
Simon Scott
Hexnode UEM
We tested a similar setup briefly. The app could be installed in some cases, but the management behavior was inconsistent, especially around lockdown-style controls. I wouldn’t use it for anything that needs guaranteed kiosk or compliance behavior.
Okayy got it. I was running into with device admin permissions issue. I was hoping the Android base would make it manageable like a normal Android device, but it sounds like the headset OS is different enough that policies may not apply properly.