VR headset fleet management is the ongoing work of provisioning, configuring, monitoring and eventually retiring every headset a company owns, not a single purchase decision. Past a handful of shared devices, it means an IT team enrolling headsets into a device-management platform, pushing training apps and kiosk locks to every unit at once, and checking battery, storage and software version from a dashboard instead of walking the floor. None of the three biggest VR platforms (Meta Quest, PICO, HTC VIVE) hands this to IT ready-made for a training rollout. It has to be planned before headsets arrive, not after the third one goes missing.
What fleet management actually covers
Fleet management is four separate jobs, not one: enrolling a new headset without touching it individually, pushing apps and configuration to a whole group at once, watching device health from a single dashboard, and cleanly wiping a unit when it is reassigned or returned. A platform that only handles one of these still leaves someone walking room to room.
- Enrollment. Registering a headset with the management platform, usually via QR code, USB or an account tied to the manufacturer, so it checks in automatically from then on.
- Configuration push. Deploying the same app, Wi-Fi profile and locked settings to one headset or to every headset in a site at once, rather than opening each device's settings menu by hand.
- Monitoring. A dashboard showing which devices are up to date, low on battery, out of storage or offline, so a fault turns up before a trainee reports a dead headset.
- Offboarding. Wiping a headset and clearing its enrollment when it moves to another team, goes in for repair or leaves the fleet, so the next user does not inherit someone else's account and files.
Why none of the headsets manage themselves
Meta Quest has no built-in kiosk mode or fleet console. To lock a Quest to one training app and manage it alongside other units, you enroll it through Meta Horizon Managed Services (HMS) and run day-to-day management from a third-party MDM; ArborXR and ManageXR are the two most established (ArborXR, 2026). HMS handles enrollment; the MDM becomes what the guide calls "the system of record for device configuration, content delivery, updates, and fleet operations" once a headset is enrolled. We cover the mechanics of the lock itself in how VR kiosk mode works for training headsets.
PICO takes a different approach: its enterprise headsets ship with a first-party console, Business Manager, that already includes live device monitoring, remote reboot, shutdown, data wipe and factory reset, batch enrollment, and home-screen kiosk locking, without a separate vendor in the loop (PICO Business, 2026). That is the practical trade-off for IT: a single-vendor Pico fleet can stay inside Pico's own console, while a Quest fleet, or a mixed one, needs a cross-platform MDM from day one.
What changed for Meta Quest fleets in 2026
Meta reshaped its enterprise Quest program in early 2026. Starting February 20, 2026, HMS licenses became free (organizations no longer pay to enroll Quest devices into an MDM), but Meta also stopped selling commercial Quest SKUs and put HMS itself into maintenance mode: no new features, with security updates continuing only through the regular Meta Horizon OS update process, and support running through January 4, 2030 (Meta, 2026; ArborXR, 2026).
For a company planning a fleet, the practical read is: enrollment still works exactly the same way and now costs nothing, but Meta itself is not actively developing the enterprise layer any further. The third-party MDM carries more of the ongoing weight than it used to: configuration, content delivery and fleet-wide updates are entirely on ArborXR's or ManageXR's roadmap, not Meta's. We go through which enterprise headsets fill that gap in enterprise VR headsets after Meta's exit.
A rollout checklist before headsets arrive
- 1Pick the MDM before you buy hardware. Check the platform's supported-device list against the headsets you are considering — a cross-platform MDM like ArborXR covers Quest, PICO and VIVE from one console; a single-brand fleet can lean on a first-party console like PICO Business Manager instead.
- 2Set up enrollment accounts ahead of shipping. A Quest fleet needs an HMS account created before headsets reach a site; a Pico fleet needs a Business Manager organization set up the same way.
- 3Build one configuration package and test it on a single unit — kiosk app, Wi-Fi profile, locked settings — before pushing it to the rest of the group.
- 4Write down the offboarding step. Decide who wipes and re-enrolls a headset when it changes teams, goes for repair, or leaves the fleet, so the process does not depend on one person remembering it.
- 5Assign someone to the health dashboard weekly. Battery wear and storage fill up silently over months of shared use; nobody notices until a session opens with a headset at 8% charge.
Fleet management and your training program
None of this touches what a training app records. A headset locked into kiosk mode through ArborXR, ManageXR or PICO Business Manager still reports completions, scores and time-on-task to your training platform exactly as before. Fleet management controls what the device can run, not what your LMS sees. Our help center walks through connecting a managed headset so completions land against the right trainee, and the VR training catalog shows which scenarios are ready to push to a locked-down fleet. Planning device management before the headsets arrive is what keeps a ten-unit rollout from turning into ten separate part-time jobs.
