Replacing Horizon Managed Services: Open-Source and Commercial Tools to Manage VR Fleets

Facing the End of Horizon Managed Services? A Practical guide to replacing it in 2026

Hook: If your organization relied on Horizon managed services to provision, secure and monitor Quest headsets, Meta's late-2025/early-2026 product shift and the February 2026 shutdown of Horizon-managed offerings creates an operational gap you must close quickly. This guide gives a clear, technically practical roadmap — open-source and commercial tool options, migration templates, and configuration examples to get a VR fleet back to production fast.

Why this matters in 2026

Meta's strategic retrenchment in late 2025 and the discontinuation of Horizon-managed services in early 2026 removed a turnkey path for enterprise Quest management. Organizations now need to replace:

• Enrollment and provisioning workflows (zero-touch / bulk enrollment)
• App distribution and licensing (Managed Google Play or sideloading)
• Network and kiosk configuration (Wi‑Fi, captive portals)
• Monitoring, inventory and remote actions (wipe, reboot, logs)

The good news: by 2026 there are mature paths using Android Enterprise, the Android Management API, and both established commercial EMM/MDM vendors and a handful of open-source projects to cover nearly every enterprise need.

High-level strategy: Replace Horizon with a layered approach

Don't try to swap features 1:1. Instead split responsibilities and pick best-of-breed for each layer:

1. Enrollment & identity — use Android Enterprise (EMM) or ADB provisioning for bulk devices.
2. App distribution — Managed Google Play or a signed enterprise app catalog; consider private app stores for XR tooling.
3. Configuration & policies — MDM profiles, JSON policies via Android Management API, and Wi‑Fi/kiosk templates.
4. Monitoring & telemetry — EMM dashboards + custom telemetry agents/log collectors.
5. Firmware & updates — firmware control remains vendor-limited; rely on Meta’s OTA where possible and schedule app/OS testing pipelines.

Option matrix: Open-source vs Commercial choices

Below are practical options that teams have adopted in 2025–2026. Each entry lists strengths, limitations, and the typical scale where it fits best.

Commercial EMM/MDM (recommended for medium-to-large fleets)

• Microsoft Intune — Pros: Native Azure AD integration, broad Android Enterprise support, robust policy engine. Cons: May require custom scripts for certain Quest-only behaviors. Best for enterprises already on Microsoft 365.
• VMware Workspace ONE (UEM) — Pros: Enterprise-grade device lifecycle, strong kiosk and application management. Cons: Licensing complexity; integration work for XR-specific workflows.
• SOTI MobiControl — Pros: Strong in single-purpose-device fleets, remote view and kiosk modes. Cons: Less common in office-desktop-first shops.
• Ivanti / MobileIron — Pros: Mature Android support, good for regulated industries. Cons: Vendor consolidation has changed roadmaps — validate Quest/Meta support post-2025 changes.
• Scalefusion / Hexnode — Pros: Easier to pilot, straightforward pricing for smaller fleets. Cons: Feature sets vary; confirm Android API access for Quest models.

How these integrate with Quest: Most commercial MDMs support Android Enterprise or provide ADB-based enrollment options. Since Quest runs an Android variant, vendors typically manage apps, Wi‑Fi and kiosk mode, but firmware-level features (guardian, system updates) remain under Meta control.

Open-source and DIY combos (best for small fleets, labs, and cost-conscious orgs)

• Android Management API (Google) — Not a product but a platform: combine it with your own backend to create policies, push apps via Managed Google Play, and automate enrollment. Best where you have engineering resources.
• Flyve MDM — An open-source MDM platform built around Android, useful for labs and limited fleets. Pros: No license fees; extendable. Cons: Less polished UI and fewer enterprise integrations.
• ADB + scripts — For labs and one-off devices you can script provisioning over USB/Wi‑Fi (ADB), including sideloading APKs, setting up Wi‑Fi, and toggling developer settings. Cheap but fragile at scale.
• Custom telemetry + Prometheus/Grafana — Shipping a small agent (or using log-forwarding via ADB/adbkit) to collect headset health metrics and present them in dashboards is realistic for teams who need custom insights.

Practical migration roadmap (60–90 day plan)

This is a tactical, timeboxed plan we’ve used with enterprise clients migrating 100–2,000 headsets.

1. Day 0–7: Inventory & risk assessment
   • Count devices by model and OS build.
   • Catalog apps, licensing, and integrations that depend on Horizon-managed services.
   • Identify compliance requirements (C2, HIPAA, FedRAMP, etc.).
2. Day 8–21: Select tooling & pilot (10–50 devices)
   • Choose 1 commercial MDM and/or open-source approach.
   • Run an enrollment pilot and test app distribution, Wi‑Fi, kiosk policies and remote wipe.
3. Day 22–45: Build templates & automation
   • Create deployment templates (below) and automated enrollment scripts.
   • Set up monitoring dashboards and alerting for offline/headset health.
4. Day 46–75: Staged rollout
   • Roll out to production groups in waves (25–30% increments).
   • Maintain a rollback plan to re-enroll devices or revert to earlier profiles.
5. Day 76–90: Optimize and document
   • Final operational runbook for helpdesk and security teams.
   • Budget for ongoing licensing, support and firmware testing cycles.

Actionable configuration templates

Below are templates you can adapt immediately. They assume Android Enterprise compatibility or ADB access.

1) Quick ADB provisioning script (USB batch for labs)

#!/bin/bash
# adb-provision.sh - basic provisioning for Quest dev/devices
ADB=adb
APK_PATH="./enterprise-app.apk"
WIFI_SSID="CorpWiFi"
WIFI_PSK="SuperSecretPass"

# Wait for device
$ADB wait-for-device

# Enable stay awake and set screen timeout
$ADB shell settings put global stay_on_while_plugged_in 3

# Push APK and install
$ADB push "$APK_PATH" /sdcard/
$ADB shell pm install -r /sdcard/enterprise-app.apk

# Add Wi-Fi config (Android 11+ uses wpa_supplicant or Wi-Fi suggestions API; this uses legacy for convenience)
$ADB shell "am start -a android.settings.WIFI_SETTINGS"
# For newer Quest images, use enterprise Wi-Fi provisioning via EMM or QR-config instead

# Reboot
$ADB reboot

Note: Use this pattern only for small labs. For fleets, use Android Enterprise provisioning (zero-touch or QR/AFW) to avoid developer mode and USB callbacks.

2) Android Management API policy example (JSON)

This sample policy is a starting point for deploying kiosk-style experiences and permitted apps via Managed Google Play.

{
  "name": "enterprises/XYZ/policies/kiosk_policy",
  "applications": [
    {
      "packageName": "com.company.vrapp",
      "installType": "FORCE_INSTALLED"
    }
  ],
  "passwordRequirements": {
    "passwordMinimumLength": 6,
    "passwordQuality": "SOMETHING"
  },
  "systemUpdate": {
    "type": "WINDOWED",
    "startMinutes": 1200,
    "endMinutes": 1440
  },
  "persistentPreferredActivities": [],
  "kioskCustomLauncherEnabled": true,
  "openNetworkConfiguration": "{...}" 
}

Replace package names and Wi‑Fi blobs with your Managed Google Play app and network configuration. Use the Google APIs client libraries to create and apply policies programmatically.

3) Intune checklist for Quest management

• Enable Android Enterprise in Intune tenant and configure Managed Google Play.
• Create an Android device configuration profile for kiosk mode (single-app or multi-app).
• Deploy Wi‑Fi profiles with certificate-based EAP if needed.
• Publish enterprise VR apps to Managed Google Play as private apps.
• Test remote wipe, remote lock, and device restart workflows.

Monitoring, telemetry and security considerations

Device health and telemetry are essential. Horizon provided a consolidated dashboard; you must rebuild that capability.

• Inventory: Use your MDM's inventory API. If you use Android Management API, poll device states regularly and store snapshots.
• Health metrics: Track battery cycles, Wi‑Fi signal, application crashes and storage. Send alerts for repeated app crashes or missing check-ins.
• Security: Enforce strong passwords/PINs, disable sideloading on production devices, and use certificate-based Wi‑Fi where possible.
• Privacy: Declare telemetry collection and comply with workplace privacy laws. Provide user consent flows when headsets are personal device / BYOD.

Firmware and the reality of limited system control

In 2026 Meta still controls the Quest firmware update channel. That means:

• Complete firmware pushes may require support coordination with Meta or controlled staged rollouts via Meta's OTA.
• MDMs can manage apps and configurations but cannot replace core system images or alter guardian/room-setup primitives at scale.

Plan a firmware testing pipeline: a small canary group, regression test scripts for enterprise apps, and a rollback playbook if a firmware release breaks workflows.

Cost expectations and staffing

Budget considerations in 2026:

• Commercial MDM: Expect $3–$15/device/month depending on feature tier and support. Enterprise bundles and annual contracts apply.
• Open-source/DYI: Lower direct license costs, but plan for 0.25–0.5 FTE to operate per ~250 devices initially (automation reduces this).
• Support: Create a small 1st/2nd line support playbook; VR troubleshooting is different (guardian, passthrough, sensors).

Real-world case: Migrating 300 Quest headsets to Intune + Android Management API (summary)

We worked with a services client in late 2025 to migrate 300 headsets after Horizon's deprecation announcement. Key outcomes:

• Pilot (30 devices) validated Managed Google Play private apps and Wi‑Fi certificates in two weeks.
• Enrollment used QR provisioning (Android Enterprise) to avoid USB/developer mode work.
• We automated policy enforcement via the Android Management API for kiosk mode and used Intune for identity and conditional access.
• Operations reduced mean time to repair (MTTR) by 40% after implementing remote wipe/reboot and standardized telemetry alerts.

Checklist: What to validate before Horizon service shutdown

• Have you exported your device inventory and app license records?
• Do you have a tested enrollment path (QR, zero-touch or USB/ADB) for bulk devices?
• Is your private enterprise app published in Managed Google Play or packaged for sideloading with enterprise signing?
• Do your security and legal teams accept the new telemetry and privacy flows?
• Is a firmware testing and canary plan in place?

Trends & predictions for 2026–2028

Expect these developments as the XR device ecosystem matures:

• Stronger EMM integration for XR: By late 2026 more major MDMs will publish explicit Quest connectors and templates, reducing custom work.
• Standardized XR policies: Industry groups will push for standardized configuration objects for guardian/playspace metadata and anchored enterprise experiences.
• Cloud-managed XR telemetry: Vendors will offer richer device telemetry, spatial logs and app performance traces for XR-specific debugging.
• Marketplace for enterprise XR apps: Private marketplaces integrated into MDMs will simplify app lifecycle and licensing.

Meta's decision to discontinue Horizon managed services is forcing organizations to treat VR headsets as first-class endpoints — and that opens opportunities for tailored device management strategies.

Final recommendations — choose based on scale and risk

• Small fleets / labs (<=50 devices): Use ADB + scripts or Flyve MDM while you validate Android Management API; invest in automation early.
• Medium fleets (50–500 devices): Choose a mid-market MDM (Scalefusion, Hexnode) or start with Intune if you already use Microsoft 365; adopt Android Management API policies for automation.
• Large fleets (>500 devices): Standardize on an enterprise MDM (Intune, Workspace ONE or SOTI), combine with Android Management API for policy-as-code, and staff a 0.5–1.0 FTE operations owner.

Takeaways and next steps

• Horizon managed services sunset is a near-term operational risk — act now to inventory and pilot alternatives.
• Android Enterprise + Managed Google Play is the modern backbone for Quest management; pair it with commercial MDM for fastest enterprise readiness.
• Open-source approaches are viable for labs and early-stage projects, but require automation effort to scale.
• Expect limited firmware control; build canary groups and regression tests for every system update.

Resources to apply immediately

Start with:

• Export your Horizon device inventory and app lists (CSV) — do this today.
• Run a 10-device pilot using Android Management API or your preferred MDM.
• Build a single-runbook for enrollment, app deployment and a remote wipe/reboot test.

Call to action

If you need deployment templates, a tested Intune policy bundle, or a custom Android Management API policy for kiosk-mode Quest fleets, we publish configurable templates and migration checklists for IT teams. Contact our Enterprise Tooling team at Tecksite or download the ready-to-run policy templates to accelerate your migration off Horizon managed services.

Related Reading

• Animal Crossing Takedowns: When Nintendo Deletes Fan Islands — Ethics, Moderation, and Creator Grief
• Step-by-Step: Use USDA Export Data as a Leading Indicator for Short-Term Gold Trades
• Studio-Backlot Weekends: Visit the Sets Behind Disney+ and EO Media Hits
• Operationalizing Hundreds of Micro Apps: Governance, Observability and Hosting Costs
• From Pitch to Premiere: A Starter Checklist for Producing Short Nature Films for Streaming Platforms