Device Fleet Management

Manage multiple VR headsets across your organization

Manage VR headsets at scale for your organization using device management platforms.

Overview

For organizations with multiple Quest headsets, device management helps you:

  • Deploy apps to all devices centrally
  • Configure settings remotely
  • Track device inventory
  • Manage updates

Meta Horizon Workrooms (Managed Devices)

Meta’s enterprise solution for Quest device management.

Setup

  1. Create a Meta Work account at work.meta.com
  2. Set up your organization
  3. Enroll headsets into managed mode
  4. Deploy Vrex via the app catalog

See Meta Horizon Setup for detailed steps.

Capabilities

FeatureSupported
App deployment
App updates
Device groups
Remote wipe
Kiosk mode
Usage analytics

Device Groups

Organize headsets by:

  • Location: HQ, Site A, Site B
  • Team: Design, Construction, Client demos
  • Purpose: Training, Production

Apps can be deployed to specific groups.

Third-Party MDM

Quest devices also work with enterprise MDM solutions:

VMware Workspace ONE

  1. Enroll Quest devices in Workspace ONE
  2. Deploy Vrex APK via app catalog
  3. Configure policies

Microsoft Intune

  1. Add Quest devices to Intune
  2. Deploy Vrex as Android app
  3. Apply configuration profiles

SOTI MobiControl

  1. Enroll Quest devices
  2. Push Vrex application
  3. Monitor device status

Deployment Strategies

Centralized IT

IT team manages all devices:

  • Devices stored in IT
  • Loaned out for sessions
  • Returned and recharged
  • Software updated centrally

Pros: Consistent configuration, easy updates Cons: Logistics overhead

Distributed Ownership

Devices assigned to teams/individuals:

  • Each team manages their devices
  • IT provides initial setup
  • Users handle day-to-day

Pros: Less IT burden, faster access Cons: Configuration drift

Hybrid

Mix of centralized and distributed:

  • Pool of shared devices for training
  • Dedicated devices for power users
  • IT maintains critical policies

Best Practices

Naming Convention

Use consistent device names:

VREX-{Location}-{Number}
Example: VREX-HQ-001, VREX-SITE-A-005

Charging

  • Deploy charging stations
  • Establish charging schedules
  • Track battery health

Updates

  • Test updates on one device first
  • Schedule updates during off-hours
  • Keep update logs

Security

  • Enable device passcodes
  • Set auto-lock timeouts
  • Enable remote wipe capability
  • Audit device access regularly

Inventory Tracking

Track for each device:

FieldExample
Serial number1WMHH12345
Device nameVREX-HQ-001
LocationHeadquarters
Assigned toDesign Team
Purchase date2024-06-15
Warranty expires2026-06-15

Troubleshooting

IssueSolution
Device won’t enrollCheck Wi-Fi, reset device
App won’t installVerify device is in correct group
Updates stuckCheck storage space
Device lostUse remote locate/wipe