The XR Network Survival Guide: The Essential Wi-Fi Strategy for Successful Deployments
Deploying AR and VR at scale, whether in a classroom, hospital, enterprise training center, or museum, opens up transformative possibilities. However, no matter how compelling your XR content is, none of it can work without a stable and well-configured network. Network issues can be the most significant source of friction in XR deployments.
This serves as your comprehensive survival guide to deploying networks to your devices. Whether you're a technical IT professional or a non-technical stakeholder leading a virtual reality initiative, this guide will help you avoid pitfalls, build a solid foundation, and ensure your headsets connect smoothly every time.
Why Deploying XR Content is Unique (and Tricky)
Deploying VR content is not like deploying normal files. The applications are larger, and VR experiences require greater bandwidth. Tools like remote screen streaming and realtime commands need low-latency, high-speed internet.
The Ideal Network Scenario
Ideally, your deployment has an independent Wi-Fi network dedicated to your devices. This network should have the maximum bandwidth and speed available to accommodate the large size of VR applications. AR devices typically require less bandwidth than VR, but it is still strongly recommended to use an independent Wi-Fi network. Though AR content tends to be smaller than VR applications, AR device networks still need to be powerful enough to support app downloads and video calling.
1. An Independent Wi-Fi Network (Just for your VR and AR Devices)
An independent Wi-Fi network is a hidden, non-enterprise network that is only accessible to VR devices. This is what will be used as your deployed network. Rather than compete with other devices on the network, VR devices have their own “lane” to connect to the internet. By giving these devices their own dedicated Wi-Fi connection, you avoid network congestion, reduce connection issues, and ensure more reliable performance. This is the foundation for a smooth, frictionless user experience.
2. Maximum Bandwidth and Speed
The network should offer a 5GHz frequency band to give your fleet a reliable bandwidth, and therefore more reliable downloads. It should also have a minimum download speed of 200mpbs to support large downloads.
Most routers support a dual-band connection (5GHz or 2.4GHz). Android devices can see and choose between the two, typically displaying them as separate networks if the SSIDs differ. If the SSID is the same for both bands, the device automatically picks one using its own algorithm. However, 2.4GHz should mainly be used to support older devices or longer-range connections. Disabling the 2.4GHz option will guarantee the device is connecting to the optimal network for XR devices, which is 5GHz.
3. Clear and Documented Requirements
Of course, in an ideal world, you can simply type in the name of your Wi-Fi network and password, and then your devices are ready for action. However, this introduces security risks where users may access content they should not be able to.
Often, organizations have specific Wi-Fi requirements in order to protect their users and their data. It’s important to work with IT to gather all the information you need about deploying Wi-Fi networks. Here’s a list of what to look out for:
- All ManageXR (and needed content provider or hardware manufacturer) endpoints are added to the network allowlist and firewall exceptions. This ensures your VR content is not blocked from your devices. See our network requirements (endpoint list) here.
- Peer-to-peer connections are allowed (optional, but helpful for casting)
- You know exactly what certificates are required for a device to correctly function on your network, and IT can upload them to ManageXR. If your network is an Enterprise Network, it will often require a certificate to be deployed via ManageXR along with the WIFi network to successfully connect. If your network deploys a content filtering system, it is common to require installing additional certificates as well. This is often the case in school deployments. Learn more about the different types of certificates here.
- IT should share what information is needed to authenticate devices on a network. For example, this could be identity and password-based, user certificate-based, or MAC filtering-based.
If you are not sure what some of these terms mean, don’t worry! The main takeaway is to communicate with your IT team about your organization’s requirements for putting your VR devices onto your organization’s network.
From Planning to Provisioning: 3 Steps to Set Up Your Network
Setting up a network for your devices can be broken down into three steps: preparation, validation, and provisioning. These steps are meant to guide you through the key considerations and avoid common pitfalls of deploying networks to devices.
Step 1: Prepare your Network and Talk to IT
Collaborating with your network administrators is one of the most crucial steps to configure a network for your VR devices efficiently. Before receiving your VR devices, contact your IT department with the following questions.
Identifying possible networks:
“Can we set up a network specifically for our XR devices? If not, what networks are available for use?”
In the ideal scenario, you should set up a network solely for your XR devices. Otherwise, try to find a network that does not already have many devices on it.
Early evaluation of networks:
“What are the expected download speeds? How many active devices could the network support? Is that sufficient for our use case?”
Since VR applications are large, the network should support a download speed of at least 200 Mbps. You should also have an estimate for the number of devices your program will need, and confirm that the network can support that number before experiencing any delays or slowdowns.
Understanding authentication requirements:
Wi-Fi authentication is the process your network uses to determine which devices are allowed to connect. Some networks are simple and only require the network name and password to connect. Others are more secure and complex. You should ask the following questions to ensure your devices can authenticate and connect to your network smoothly.
“What kind of authentication do we use to bring devices onto this network? Can you provide me with this information now so I can enter it in our MDM for faster network provisioning?”
Depending on your network’s level of security, your devices may have different methods of connecting to it. Some common options include:
- WPA2 with a shared password for all devices
- WPA2-Enterprise with a username and password for each device
- Certificate-based authentication (each device needs its own digital certificate)
- MAC address filtering (only known devices are allowed to connect)
Suppose your IT team can share the right login method and any necessary credentials (such as the Wi-Fi password, certificates, or authentication settings). In that case, you can add this information onto ManageXR to deploy to your devices so they can be set up automatically.
See how to configure Wi-Fi networks on ManageXR here.
“Will our Wi-Fi passwords change, and can we be informed before that happens?”
Some organizations rotate their Wi-Fi passwords or update their certificates regularly for security. If the Wi-Fi credentials change without warning, your VR devices could be forced offline, interrupting in-headset users and your VR program.
Uncover any other network restrictions that require action:
Once your VR headsets connect to a Wi-Fi network, the job isn’t done yet. You still need to make sure it can actually talk to the internet and reach the content it depends on, like ManageXR, web-based VR apps, casting tools, and more.
Even if the device says “connected,” it might be silently blocked from accessing the sites your devices need.
Here’s what to ask IT:
“Do we have a firewall or content filtering system that prevents access to certain endpoints, including endpoints from our VR program? Can you add these endpoints to the allow list?”
What are firewalls and blocked endpoints? A firewall decides which websites, services, and servers (called endpoints) your devices can talk to. Endpoints are the specific internet addresses or domains your VR devices will need access to sync with ManageXR, download apps and files, get firmware updates, and more. Many networks (especially in Education) already block hardware and software-specific websites. For example, most schools already block Facebook (Meta) and TikTok (ByteDance) servers, which can disallow casting and firmware updates and potentially cause other issues with Meta Quest and Pico VR devices (owned by ByteDance).
“Do we have a content filtering system in place that would require us to install a certificate on the device? Can you provide this certificate in PEM format?”
What is a content filtering system? Think of it like a filter that inspects all internet traffic. Schools, hospitals, and enterprises often use these to block inappropriate or unwanted content. These systems intercept the connection between the device and the internet, which can cause trust issues for the headset. If the VR device doesn't recognize the content filter, it may assume the internet connection is unsafe and block it entirely, even if the device is technically online.
What is a PEM certificate? This is a digital “hall pass” that tells the VR device to trust the content filtering system. PEM format is a standard file format used for these certificates.
If your IT department is having trouble understanding XR devices, you can also ask how you would connect an Android device to your network and mirror the authentication requirements!
Here’s a recap of what to ask your IT team:
Pro Tip: Use a Provisioning Network
When first setting up VR devices, it’s best to use a provisioning network. A provisioning network is any simple network that you can connect to as a temporary step (even a hotspot will do the trick). Often, there is an open network at your school or business that can be used for this purpose. This enables you to bypass any complications you may encounter when connecting to your deployment network and simplifies your device setup process. This provisioning network should have no restrictions and should not include certificates, firewalls, filtering, or any other credentials. Then, once setup is complete, you can troubleshoot any additional network requirements, and isolate any issues solely to the network you plan to use.
Once connected to the provisioning network, your device can sync with ManageXR and pull down the more complex Wi-Fi network profile. To connect your device to a provisioning network:
Once connected to the provisioning network, your device can sync with ManageXR and pull down the more complex Wi-Fi network profile. To connect your device to a provisioning network:
1. Install ManageXR on your device
2. Connect the device to your provisioning network.
This can be done by selecting the Add Wi-Fi Network option from the Advanced Action menu in the Device Setup Tool or in-headset.
You can also add the provisioning network as a network profile in the ManageXR web console, add the network to a configuration, and remotely deploy the configuration to your device. This process requires that your device is already connected to a network that is not the provisioning network.
Now, you can be sure your device will communicate with ManageXR and receive updates.
Step 2: Validate your Deployment Network
At this point, your network is set up, your device is connected to the provisioning network, and your device has ManageXR downloaded. Before your full fleet of devices arrives, we strongly recommend testing your network on a single device so you can get comfortable with the provisioning workflow and catch potential issues ahead of time. This will avoid a delayed deployment.
The following steps will walk you through testing your deployment network, assuming ManageXR is already downloaded to your device. Follow the get started guide here if you have not downloaded ManageXR to your device, and connect your device to the provisioning network.
Here is what you will need to test your network:
- A headset that is the same model as your deployment, with ManageXR already downloaded to it and connected to a provisioning network.
- Your deployment network, including all necessary credentials and relevant information.
- A computer to access the ManageXR Web Console.
1. Create your deployment Wi-Fi network profile on ManageXR. You will need to fill in key information about your deployment network, such as a nickname, SSID, whether it is a hidden network, the network type, and proxy type.
2. Assign your deployment network to a configuration, and deploy the configuration to your device.
3. Confirm the headset can properly communicate with the internet once on the network. If your device says it is connected but it is not receiving any communication from the internet, it is likely missing a certificate. You can test this by opening a browser in headset, and navigating to a common website, like www.google.com. If it fails to load, talk to your IT team and ManageXR support to get this certificate deployed to your device.
4. Confirm the headset can properly communicate with ManageXR once on the network. If the device can access other applications but not ManageXR, check that ManageXR endpoints are allowed by your firewall. A quick way to troubleshoot this is by connecting to the network on any device you use and trying to access this test site which is on the ManageXR server. Information about blocked endpoints will either show up on your ManageXR Dashboard as an Alert or in-headset in Admin Settings. Send our Network Requirements article to your IT department. Ask your IT admins to confirm once they have allowed all required endpoints on your network.
5. Confirm the headset can properly communicate with any of your other apps’ servers once on the network. Ask your content providers for a list of endpoints required for their content and check that your firewall allows them.
Step 3: Provision your Devices with your Deployment Network
Now that you have confirmed your network is ready for your devices, you can bulk provision your VR fleet with your network!
You will need your devices, a cable to install ManageXR onto your devices (Meta devices follow a different process: read this help article to understand how to get ManageXR onto Meta devices), and your computer to access the ManageXR web console.
- Create and save your deployment Wi-Fi network profile in ManageXR. This will be the primary network your devices will save and remain connected to after the provisioning step.
- Assign your deployment network to a configuration.
- Download ManageXR to your device. Follow the get started guide here. You will want to use your provisioning network to connect your device to the internet first so you can be sure that your device is synced with ManageXR.
Tip! If you're installing ManageXR using the Device Setup Tool, you can set the Provisioning Mode to ManageXR + Configuration Content to directly load your deployment network credentials during the installation process. This will allow you to skip using a provisioning network, though we still recommend using one so your device will always sync with ManageXR if issues arise with your deployment network.
- Ensure your devices sync with the deployed configuration. You can do this by checking that your devices’ sync status in ManageXR is “Up To Date.”
If you add the provisioning network and deployment network to the same configuration, use ManageXR to mark the deployment network as “Always connect if available” so your devices connect to the right network by default, instead of the provisioning network.
Troubleshooting Common Issues
You may run into some of these common issues with network setup. Here is how you can troubleshoot them.
Blocked Endpoints
You will know if your network has blocked endpoints to ManageXR if: A) you cannot access this ManageXR endpoint test website, B) you see in-headset alerts in the admin settings, or C) you see Network Error alerts on the ManageXR Dashboard.
To fix this, send this document of required ManageXR endpoints to your IT team, so they can allow the endpoints on your network.
Certificate Issues
Devices might connect to a network, but still have no internet connection. This might be due to a missing certificate or certification deployment issue. In this case, work with your IT team to understand if you have a content filtering system or reverse proxy. Then, work with ManageXR support to get your network certificate deployed!
Slow or Unstable Downloads
Your network might not be reliable for large downloads if A) devices repeatedly fail to complete downloads, B) average download speeds are extremely slow when downloading content, or C) devices regularly have Network Issue alerts for Unstable Network Connection.
To solve for a slow or unstable network, consider switching to a stronger network or a dedicated network for your devices. For downloads, you can also consider offline options such as pushing configuration updates via the Device Setup Tool (not applicable for HMS Meta devices) or requesting a USB offline update package.
Conclusion
A reliable network is the backbone of any successful VR deployment. By following the best practices outlined in this guide, you can sidestep common issues, streamline your setup, and create a seamless experience for your users. With the right network strategy in place, your VR program will be set up for long-term success.
Need an extra hand? You can always reach out to ManageXR’s support team to get hands-on help with your network provisioning.
Resources
For more guided walkthroughs and additional resources, check out ManageXR’s help articles on deploying Wi-Fi networks:
Configure Wi-Fi Network Profiles
Enterprise Network Certificates: What Are They and What Are They Used For?
Deploying Enterprise Wi-Fi Certificates on ManageXR
Dynamic Device Wi-Fi Configurations
How to Connect your Device to Wi-Fi (In-Headset)
Network Requirements (Endpoint List)
FAQs
Where can I find information about my network issues?
Device alerts are especially useful in identifying network issues that occur within your fleet of devices. As a note, device alerts can be found on the dashboard and the device detail page.
Why does my device keep connecting to the wrong network?
If your device continues connecting to the provisioning network or the user-selected network rather than the deployed enterprise network, you can:
- Remove the provisioning network from the deployed networks on your configuration
- Use the Remove Wi-Fi Network command to forget unapproved networks
- Use Advanced Wi-Fi options on your configuration to select “Always connect if available” on the desired network. This will force devices to connect to your network of choice. Learn more
My Wi-Fi Network says "Synced" - why isn't my device connecting to it?
ManageXR will always let you add a Wi-Fi network to a configuration. A Wi-Fi Network can successfully save to the device without necessarily having the correct credentials. If your credentials are incorrect, the device(s) will be unable to connect to the network when in range. Always ensure the device has successfully connected to the specified network when deploying a new Wi-Fi network.
If my device has multiple Wi-Fi networks saved to its list of remembered networks, how does it decide which one to connect to?
Android decides which Wi-Fi network to connect to based on several factors when multiple saved networks are available. The key factors include:
- Signal Strength: Android typically prioritizes the network with the strongest signal when scanning. It will connect to a network with better signal quality to ensure a reliable connection.
- Network Priority: Depending on the version of Android, a network saved more recently might sometimes be prioritized over older ones. In some versions of Android, a network can be assigned as a priority. To force devices to connect to one device over all other networks, you can use the Always connect setting on ManageXR.
- Network Security: Android prefers more secure networks (such as WPA2 or WPA3) over less secure ones (such as WEP or open networks). This helps ensure the device is connected to a safer network when multiple options are available.
- User Preferences: If a user manually connects to a specific network, Android may prioritize that network in the future, even if others are available. This can also create a "default" network based on usage patterns.
- Frequency Band (2.4 GHz vs. 5 GHz): If both 2.4 GHz and 5 GHz bands are available, Android might favor the 5 GHz network because it generally offers better performance. However, it may switch to 2.4 GHz if that band has a stronger signal or is more stable in specific environments.
On ManageXR, you can mark “Always connect if available” on your preferred network so your devices connect to the right network by default. If your preferred network is unavailable, your device will try to connect to the next best option.
Can I connect my device to Wi-Fi through captive portals?
Yes. Hotels, airports, conferences, coffee shops, and other establishments often use captive portals to facilitate internet connections. ManageXR's Home Screen natively supports captive portal WiFi networks, and the ManageXR kiosk mode can also support these networks, but the shortcut menu must be turned on. Connecting to a captive portal network will open a web browser to complete the captive portal authentication. See the full help docs on captive portals here.
Does ManageXR work with closed/on-prem networks?
ManageXR is a cloud-based platform and will not work on closed/on-prem networks. If security is a concern, we recommend reviewing our Security Policy and addendums. If you have specific questions about a complex deployment, reach out to support@managexr.com.
