VR MDM: When You Need One, and When VR Session Control Software Is Enough

    An MDM is used to configure. OmnicastVR is used to act. Where the two layers of VR device management split, and which one the trainer standing in the room actually needs.

    Download for freeView pricingFree plan · 1–2 headsets · no credit card
    Stéphane Brainville

    Stéphane Brainville

    Academy Manager - OmnicastVR

    OmnicastVR is developed by NOVALAB, the company behind VR Académie, a French organization specializing in VR deployment and training.

    Updated:

    Key takeaways

    VR MDM is not one tool — it is two layers. The first layer is upstream IT configuration: device enrollment, OS and firmware control, security policies, kiosk mode, remote content deployment. ArborXR and ManageXR are built for that layer. The second layer is live session control: launching apps in real time, seeing what learners see, shutting everything down when the session ends. ArborXR (Remote Assistance) and ManageXR (Rooms add-on) also offer live features through cloud services. OmnicastVR does it on the local network: no internet during the session, no device enrollment, no headset account or cloud console required during the session. One computer running OmnicastVR controls up to 16 headsets. The distinction is simple: an MDM is used to configure. OmnicastVR is used to act. In practice: up to about 20 headsets with a trainer present, VR session control software is enough; beyond that, with reliable internet, use an MDM for the fleet and VR session control software for the sessions.

    01Definition

    What Is VR MDM?

    A VR MDM (mobile device management for virtual reality) is software that enrolls VR headsets into a central console and configures them remotely - apps, Wi-Fi, security policies, kiosk mode - so one IT administrator can manage an entire fleet from one place.

    That definition is accurate, and incomplete. Two distinct jobs hide under the label "VR MDM", and they are performed by different people, at different times, with different tools.

    The first job is upstream fleet configuration, and it belongs to IT. Headsets are enrolled in a console, Wi-Fi profiles and certificates are pushed, OS and firmware updates are controlled, security settings and kiosk mode are applied, and apps or 360° content are deployed to devices that may sit in another building. This is the layer ArborXR and ManageXR are built for. It runs from a web console, it needs an internet connection, and it happens days or weeks before anyone puts a headset on.

    The second job is live session control, and it belongs to the trainer standing in the room. It begins when the headsets go on: launching the same app across the group in one click, watching every screen side by side, checking battery levels, restarting a headset, shutting the fleet down when the session ends. All of it happens in real time, and it has to work on the network the room actually has.

    Those two jobs share a label. They are not done in the same place, at the same time, or by the same person.

    02Two layers

    The Two Layers of VR Device Management

    Layer 1

    Upstream Configuration

    IT Admin's Domain

    A cloud platform communicates with every enrolled headset over the internet. From a central web console, an IT administrator can:

    • Enroll devices and organize them into groups
    • Configure Wi-Fi networks and certificates
    • Control OS and firmware updates on supported devices
    • Apply security settings: block system menus, disable USB file transfer and developer mode
    • Lock headsets into a single app (kiosk mode) or a custom launcher
    • Deploy apps, 360° videos, files and WebXR links remotely
    • Remotely factory-reset a device
    • Track device status, location and usage analytics

    Features vary by plan.

    The key word is upstream. This work happens before training starts - often days or weeks before. It requires an internet connection and an administrator account. The people doing it are IT administrators, not trainers.

    Two established platforms in this layer: ArborXR and ManageXR. Both are cloud platforms billed per device.

    Layer 2

    Live Session Control

    Trainer's Domain

    ArborXR and ManageXR have both added live features - Remote Assistance for ArborXR, the Rooms add-on for ManageXR - delivered through cloud services. OmnicastVR takes the opposite approach: session control and video stay on the local network.

    With OmnicastVR, from a single Windows laptop or tablet, the trainer can:

    • See live video streams from up to 16 headsets simultaneously
    • Launch an app on all headsets with one click - or headset by headset if a learner needs more time
    • Monitor battery levels across the entire fleet
    • Shut down or reboot any headset remotely
    • Install custom APKs locally, headset by headset

    No internet required during the session - a local Wi-Fi network is enough (the licence needs an internet check at least once every 30 days). No headset login. No cloud console. No two-factor authentication blocking the session. The licence is machine-bound: open the app, see the headsets, control them.

    Why Both Layers Matter

    The two layers are not competing - they are complementary.

    Which layer you need depends on your fleet size, your network and how your headsets are used: the next section is a short decision guide.

    The session layer is also where research on VR training has a blind spot: see why VR training programs fail to scale.

    “

    Think of it this way: the MDM manages the fleet, OmnicastVR drives the experience.

    03When to choose an MDM

    Do You Need a VR MDM? The Situations That Decide

    An MDM is not required to run VR training sessions: OmnicastVR covers preparation and session control on its own (installing apps locally on each headset, launching, live supervision, shutting down). The situations below make an MDM the right choice.

    1. Your fleet is larger than about 20 headsets

    Beyond about 20 headsets, an MDM's remote deployment of content and updates saves real time, provided you have internet access.

    → With OmnicastVR, apps are installed locally, headset by headset: quick for a fleet of 16 headsets, much less so for 50 or 100.

    2. Your training sites have a reliable internet connection

    A cloud MDM needs the internet to act on headsets, including for live screen viewing: according to their documentation, this is the case for ArborXR and ManageXR. With good Wi-Fi connected to the internet, this works. Without reliable internet on site (factory, construction site, client's meeting room, filtered network), these features are not available during the session.

    → OmnicastVR works on the site's Wi-Fi with or without internet: if the internet connection fails, a simple local Wi-Fi router is enough for the session.

    3. Your headsets are used without a trainer, in self-service

    Kiosk mode, which locks a headset into one app, and security policies (blocking menus, developer mode…) are MDM features.

    → OmnicastVR does not offer them: it is designed for sessions led by a trainer.

    4. Your IT department sets rules for the headsets

    Some organizations require every device to be inventoried and managed: enterprise Wi-Fi with certificates, USB or developer mode blocked, controlled system updates, remote reset of a lost headset. These are MDM features.

    → OmnicastVR does not manage these rules. If your IT department blocks developer mode on Meta Quest headsets, OmnicastVR cannot connect to them: check this before rolling out.

    5. Your trainers administer the MDM themselves, or will be trained on the platform

    An MDM is an administration tool: its console is used to enroll headsets, create groups and configurations, and apply rules. It is the right choice when the people who run sessions also master that console, or when your organization plans to train them on it.

    → OmnicastVR takes almost no training to learn: one window, with every session action available from the streaming view. It suits trainers new to VR as well as experts.

    6. You will use the full range of MDM features, and your budget allows it

    MDMs cover the whole of fleet management: enrollment, remote deployment, kiosk mode, security policies, analytics. They are priced per headset. If you will use these features, this is the option to choose.

    → If you only need session control, OmnicastVR is priced per computer, by fleet size (up to 16 headsets), with a free plan for 1 to 2 headsets: compare both models in the pricing section.

    If one of these situations applies to you, here is how the two MDM platforms named above, ArborXR and ManageXR, compare with OmnicastVR.

    Comparison Table

    ArborXRManageXROmnicastVR
    Main purposeFleet management (MDM)Fleet management (MDM) + Rooms add-on for live sessionsLive session control
    Internet needed for remote control & live viewYes (cloud platform)Yes (for these cloud functions, per ManageXR documentation)No - local Wi-Fi only (licence check at least every 30 days)
    Live viewRemote Assistance (Essential plan and above)Premium: screen streaming · Rooms add-on: up to 30 headsets on one dashboardUp to 16 headsets on one screen
    Video streaming pathWebRTC using documented Cloudflare STUN/TURN services; direct or relayed depending on network conditionsWebRTC using documented relay infrastructure; direct or relayed depending on network conditionsLocal network only - never leaves the room
    Device enrollmentRequiredRequiredNone - nothing installed on headsets (Meta Quest: developer mode enabled once)
    Kiosk mode & security policiesYesYesNo
    Sign-inWeb portal account (2FA available)Console account · a Room can be started via link or QR code without sign-inNo headset account or cloud console during the session - machine-bound licence
    Pricing modelPer device, billed annuallyPer device, monthly or annual · Rooms is a paid per-device add-onFlat price per computer, by fleet size (Direct Access)

    Sources: arborxr.com/pricing, managexr.com/pricing, ArborXR and ManageXR help centers (network requirements), checked on 7 October 2026. Features and public prices vary by plan and may change.

    04Session control only

    When Is VR Session Control Software Enough, Without an MDM?

    If your situation matches one or more of the cases below, OmnicastVR covers your sessions on its own, without an MDM.

    1. You need to run sessions, not manage a fleet

    Seeing what each learner sees, launching the same content on every headset, adjusting the volume and shutting the headsets down at the end of the session: these are session control tasks. OmnicastVR handles them from one screen, for up to 16 headsets per computer.

    2. Your fleet stays under about 20 headsets

    At this scale, installing your apps locally on each headset stays quick, and it is a one-time task done before your sessions.

    3. Your sites have no reliable internet, or you often change sites

    The headsets and the computer only need to be connected to the same Wi-Fi network. Without internet on site, a simple local Wi-Fi router is enough: at a client's premises, in a factory, at an event. The licence needs an online check at least once every 30 days.

    4. A trainer always leads the session

    Kiosk mode and security policies are useful when headsets are used without supervision. When a trainer is present at every session, you do not need them.

    5. Your trainers work without IT support

    Nothing is installed on the headsets and no device enrollment is needed; Meta Quest headsets only need developer mode enabled once. There is no sign-in in the software: open OmnicastVR and the paired headsets appear. Another trainer can take over the same computer with no credentials to hand over.

    6. You want a tool designed for on-site VR session control

    OmnicastVR was designed for trainers in the field: a clean interface, limited to the functions needed to run a session, with every action available from the streaming view.

    7. Session images must stay on site (GDPR)

    Headset video streams stay on the local network, between the computer and the headsets. They are not sent to OmnicastVR's servers or to any third-party service. OmnicastVR collects no personal learner data from the headsets and no video: its only exchanges with its servers are licence activation and verification, and anonymous usage statistics (number of streams, streaming time). For your GDPR records, session video therefore involves no transfer to a third party.

    8. You prefer pricing per computer rather than per headset

    OmnicastVR Direct Access is priced per control computer, by number of headsets, with a free plan for 1 to 2 headsets. Both pricing models are compared in the pricing section below.

    If one of the situations in the previous section also applies to you, the two tools work together: see the next section.

    05Both together

    When to Combine a VR MDM and VR Session Control Software

    Illustration of a server rack with a cloud upload icon, representing remote fleet management

    Fleet management

    Remote, before the session

    (MDM — ArborXR, ManageXR…)

    Illustration of hands holding a tablet showing several VR views and a play button, representing on-site session control

    VR session control

    On site, during the session

    (OmnicastVR)

    Use case: a large headset fleet spread across several sites

    Take a large fleet spread across several sites, with 4 to 15 headsets per site. The MDM keeps the whole fleet ready remotely: enrollment, content, updates, settings. On each site, the trainer runs the session with OmnicastVR: no sign-in in the software, no IT intervention, an interface focused on what the session needs. IT manages the fleet; the trainer runs the session. Before rolling out, check the configuration on one headset: an MDM can enable or disable developer mode, which OmnicastVR needs to connect to Meta Quest headsets.

    Diagram: the VR MDM, managed by the IT department, remotely prepares a fleet of 100 headsets spread across several sites; on each site, the trainer runs the session with OmnicastVR.

    Example: a 100-headset VR fleet · several sites

    Two layers, two jobs

    Fleet · IT departmentSession · Trainer

    VR MDM · IT department

    Keeps the whole fleet ready, remotely

    EnrollmentContentUpdatesSettings

    Site A

    15 headsets

    Trainer · OmnicastVR

    Runs the session

    Site B

    8 headsets

    Trainer · OmnicastVR

    Runs the session

    Site C

    4 headsets

    Trainer · OmnicastVR

    Runs the session

    Other sites

    4 to 15 headsets per site

    100 headsets in total

    No sign-in in the softwareNo IT interventionAn interface focused on the session

    IT manages the fleet.The trainer runs the session.

    Before rolling out: test the configuration on one headset. An MDM can enable or disable developer mode, which OmnicastVR needs to connect to Meta Quest headsets.

    06The product

    How OmnicastVR Works: Live Control of Up to 16 VR Headsets From One PC

    The trainer walks into the room. No sign-in in the software. No password to find. No two-factor authentication blocking the session. They open the laptop: the headsets are there. That's it.

    1

    The Streaming View - Everything From One Screen

    Every session control action happens from within the streaming view. You don't leave the screen during the session.

    All 16 headsets appear as live video tiles. You see what every learner sees, in real time. From that same view - without switching tabs, without opening a separate menu - you can launch an app on one headset or all of them simultaneously, check battery levels, shut down a headset, or reboot it.

    This is not passive monitoring. You see all 16 screens and act directly from that same interface. The result of every action is immediately visible in the stream - you know instantly whether the app launched, whether a headset is responding, whether a learner is stuck.

    OmnicastVR streaming view showing live tiles from multiple VR headsets
    2

    Synchronized App Launch

    One click launches the same app on all connected headsets simultaneously. No relay server: the command goes from the control PC directly to each headset over the local network.

    If a learner is behind - still reading the safety briefing, still adjusting the headset - you can launch on the remaining headsets individually, without disrupting the others.

    OmnicastVR is designed for Android-based standalone VR headsets, including Meta Quest, PICO and HTC VIVE Focus. No ecosystem lock-in. Not sure about your model? Test it with the free plan.

    Meta QuestPICOHTC VIVE
    3

    Local APK Install - The SideQuest Alternative

    If your training app is not on the Meta Quest store or the Pico store, you can install it directly from OmnicastVR - headset by headset, locally. Think of it as what SideQuest used to do for individual developers, rebuilt into a professional training interface designed for fleet deployment. APK installation is a one-time setup task, done before your sessions.

    Apps already installed from the store are also accessible. The App Selector feature lets you pre-select which apps appear in the launch menu before the session starts. No scrolling through a full library of 40 APKs when you have 10 learners waiting. The session menu shows exactly what you prepared.

    4

    Network Independence

    OmnicastVR does not require an internet connection during sessions. A local Wi-Fi network - even a travel router - is enough. It also works on internet-connected networks.

    What matters is where the video streams go: they stay local, between the control PC and the headsets. They never pass through any cloud server. OmnicastVR's only exchanges with its servers are licence activation and verification, plus anonymous usage statistics (number of streams, streaming time). Licences work offline for up to 30 days between checks.

    No internet in your client's concrete bunker? No network in the factory? Your session still runs: control and video stay on the local network.

    5

    Data Privacy & Cybersecurity

    No personal learner data is collected from headsets. No video or content data is collected. The only usage metrics OmnicastVR collects are anonymous: number of streams and streaming time.

    Privacy by design: video streams never transit through the cloud - they stay on the local network. This follows from how the software works.

    07Pricing

    Pricing: Per Headset (MDM) vs Per Computer (OmnicastVR)

    Direct Access Plans (SMB / Education) for OmnicastVR

    OmnicastVR Direct Access is straightforward: one price per fleet size, no per-headset fees, no per-user fees, unlimited trainers.

    PlanHeadsetsMonthly (no commitment)Monthly (annual)Annual total
    FREE1–2€0€0€0
    Omni5Up to 5€29/month€20/month€240/year
    Omni10Up to 10€55/month€39/month€468/year
    Omni16Up to 16€115/month€79/month€948/year

    Payment is by credit card via Stripe. No Orga Manager on Direct Access plans.

    Enterprise Plan (Large Accounts & Multi-Site)

    For corporate groups, universities, distributors, and multi-site deployments, OmnicastVR offers an Enterprise plan built around Orga Manager - a multi-site license management console.

    Orga Manager lets a central administrator create sub-organizations by campus, business unit, subsidiary, or department. Licenses are purchased in bulk and distributed to sub-orgs with one click. Local managers activate their licenses remotely - no physical access needed, no IT visit required. Usage stats roll up per sub-org and across the entire group.

    Manage licenses across multiple sites from a central console. Distribute to subsidiaries, track usage per BU, activate remotely - without ever being on-site.

    The Enterprise plan also includes a dedicated account manager, priority support packs (10, 20, or 40 tickets per year), and granular per-headset licensing from Omni3 to Omni16. Payment by bank transfer or purchase order. Enterprise pricing is on request - contact us for a quote.

    How the Pricing Models Differ

    ArborXR and ManageXR are priced per headset. OmnicastVR Direct Access is priced per control computer, by fleet size, up to 16 headsets per computer. The table shows, for each product, the entry plan that includes live viewing of headset screens.

    Pricing unitEntry plan with live viewPublic list priceBilling
    ArborXRPer headsetEssential (Remote Assistance included)$10 per headset per monthAnnual (other cycles on request)
    ManageXRPer headsetPremium + Rooms add-on$13.50 per headset per month on annual billing ($10 + $3.50) · $16 on monthly billing ($12 + $4)Monthly or annual
    OmnicastVRPer control computerOmni5 · Omni10 · Omni16€20 · €39 · €79 per month on annual billing · €29 · €55 · €115 on monthly billingMonthly or annual

    Read this table with four limits in mind:

    • Scope. ArborXR and ManageXR plans also include fleet management (MDM) features that OmnicastVR does not provide: enrollment, kiosk mode, security policies, remote content deployment, analytics.
    • Discounts. Both vendors offer education pricing (for example ArborXR Classroom Pro, $6 per headset per month on annual billing), plus volume and negotiated pricing, not shown here.
    • Currency. Competitor prices are in US dollars; OmnicastVR prices are in euros, excluding VAT. No currency conversion is applied.
    • Competitor prices change. The competitor prices below are public list prices shown on the vendors' websites on 7 October 2026, in US dollars, excluding taxes. They can change at any time and do not include education, volume or negotiated discounts. Always check the official pricing pages: arborxr.com/pricing · managexr.com/pricing.
    08In the field

    Use Cases by Sector: Corporate Training, Education, Industry, Secure Sites

    Participants wearing VR headsets during a professional demonstration, with a trainer holding a tablet

    Corporate VR Training

    Safety training, onboarding, product demonstrations. A trainer manages 5–16 headsets in a training center, a conference room, or on a factory floor. No internet dependency during the session means it runs whether or not the site Wi-Fi has outbound access. Video streams stay on the local network, a point that matters to IT security teams. See corporate training use cases.

    Group of adults wearing VR headsets during a training session

    VR Labs in Schools and Universities

    VR labs, STEM programs, medical simulation. School networks are often filtered: restricted outbound traffic, captive portals. OmnicastVR works on the school's local Wi-Fi without using the internet during the session. Education coordinators get full live session control without filing an IT ticket. For a step-by-step guide, see classroom VR management.

    VR headsets and a laptop on a table at a demonstration stand

    Offline VR Training on Industrial and Remote Sites

    Oil rigs, construction sites, military training facilities. Sessions often have to run without internet. Cloud MDM platforms such as ArborXR and ManageXR need internet for remote commands and live viewing. OmnicastVR runs on a travel router with no internet connection; the licence needs to go online at least once every 30 days.

    Trainer holding a tablet in a meeting room while participants wear VR headsets

    VR Training in Secure and Regulated Facilities

    Government agencies, defense contractors, regulated industries. No video leaves the premises and no personal learner data is collected. The only outbound traffic is licence activation and verification plus anonymous usage statistics. Session control and streaming stay on the local network, which the facility already controls.

    09Getting started

    Getting Started in 3 Steps

    VR fleet management does not have to mean a week of IT setup.

    1

    Download OmnicastVR for free. No credit card. No account creation. The free plan includes 1–2 headsets and full access to every feature.

    2

    Pair your headsets once via USB-C. The connection takes about 5 seconds per headset. After that, the pairing is wireless - you never need the cable again. No OmnicastVR headset app is installed for supported devices. Meta Quest headsets only need developer mode enabled once.

    3

    Open OmnicastVR. The headsets appear. You control them. No sign-in in the software, no IT setup. The real-time headset control interface is ready immediately.

    Upgrade to Omni5, Omni10, or Omni16 when your fleet grows. Activate the license in the app. Done.

    Frequently Asked Questions

    Further reading

    VR in Education

    Run your next session without signing in.

    Free plan, 1–2 headsets, every feature included. No credit card, no sign-in in the software.

    Download for free

    At Omnicast, we respect your peace of mind

    We use cookies to improve your experience and analyze our site usage. We respect your privacy and give you the choice.

    Privacy Policy