BRIEF OVERVIEW
Overview of Meta HMS (Meta Horizon Managed Services)
- What It Is: Meta Horizon Managed Services (HMS) is Meta’s first-party device management (MDM) solution for Meta Quest headsets.
- Evolution: HMS replaces “Quest for Business” and unifies business and education device-management under one service.
- Partnership with Third-Party MDMs: Instead of being a full-featured MDM by itself, HMS is intended as the base layer of device enrollment; third-party, Meta-approved MDMs (like ArborXR or ManageXR) work on top of it.
- License / Pricing: For new devices bought through approved Meta resellers, 2 years of HMS is included. For existing devices, there’s a subscription cost.
Vendor:
Meta
Product Sheet
Product Deck
Licencing Details
| Licencing Model: | Work Education |
|---|---|
| Licencing Term: | 2 Year Annual |
| Licencing Profile: | Device |
| Pricing: | Fixed |
| Additional |
- Device Enrollment & Licensing: Devices must be enrolled via HMS before being managed by supported third-party MDMs.
- Shared or Individual Device Modes: Quest devices using HMS can operate in Shared Mode (no Meta account needed) or Individual Mode (with a Managed Meta account).
- Remote Configuration: Through HMS, organizations can provision Wi-Fi, certificates, and settings remotely.
- OS / Firmware Updates: Admins can manage or defer OS updates for their fleet via HMS
- App Deployment: You can upload apps to HMS and deploy them directly to enrolled devices.
- Basic MDM Capabilities: HMS provides “basic device management” — device enrolment, remote app installation, and some health reporting.
- Remote Management Integration: When used with third-party MDMs, you unlock more advanced management features (remote reboot, content scheduling, etc.).
- Security & Access Control: Part of a managed enterprise system — helps enforce secure, centralized device governance.
- Enterprise XR Deployment: Large-scale rollout of Quest headsets in businesses where you need centralized management and control.
- Education / Schools: Schools or universities managing Quest devices for student use want to standardize device settings, OS, and content.
- Training Programs: Organizations using VR for training (safety, soft skills, technical) can ensure all headsets use the same, controlled environment.
- Kiosk / Demonstration Use: For VR demo stations, shared headsets, or kiosks, HMS helps lock devices into managed modes.
- Fleet Management: Ongoing device maintenance at scale — ensuring devices remain enrolled, updated, and secure.
- IT / Ops Teams: Particularly in organizations that deploy many Meta Quest headsets and need a reliable, scalable way to manage them.
- Enterprise / L&D Managers: Teams running formal VR training programs who want control over device configuration and content.
- Educational Administrators: Schools or colleges using Quest as a learning tool for students.
- XR Program Leads: People planning long-term VR strategy and device lifecycle in their organization.
- Organisations Using Third-Party MDMs: Companies that already use or plan to use ArborXR, ManageXR, or another approved MDM — HMS is now a required component for enrollment.
Strengths & Considerations / Limitations
Strengths:
- Provides Meta-native management — no need for Meta accounts on Shared Mode.
- Seamless integration with enterprise-grade MDMs (ArborXR, ManageXR) for advanced control.
- Reduces friction in enrollment with zero-touch setup options.
Considerations / Drawbacks:
- Additional licensing cost once the free trial period expires.
- Some features (e.g., more advanced remote management) still require a third-party MDM.
- For legacy Meta Quest devices (pre-HMS), migrating involves factory reset and re-enrolment.
