Who can use this feature?
š¤ Organizations Owners, Admins, and custom roles with the "Create Wi-Fi Networks" permission.
š© Available on all plans.
Overview
ArborXR supports the configuration and remote provisioning of open networks, WPA, as well as the personal and enterprise modes for both WPA2 and WPA3. For the enterprise modes various encryption protocols and authentication types are supported, including certificate-based authentication. See Supported WiFi Configurations for more information.
Some Wi-Fi networks require a certificate which can be created in your Configuration Presets library then attached to the Wi-Fi Configuration Preset. For example, if you are configuring a EAP-TLS network, you may need to attach an Auth Certificate and CA Certificate. These certificates must be created first in order to attach them to the Wi-Fi Configuration Preset.
Step 1: Create the Preset
Navigate to Configuration Presets in the side navigation menu.
Click on Wi-Fi Networks to expand the section.
Select Create Wi-Fi Network.
ā
Configure network details.
ā
š” Some Wi-Fi networks require a certificate which can be created in your Configuration Presets library then attached to the Wi-Fi Configuration Preset. For example, if you are configuring a EAP-TLS network, you may need to attach an Auth Certificate and CA Certificate. These certificates must be created first in order to attach them to the Wi-Fi Configuration Preset.
Once configured, click Add.
Step 2: Assign the preset
Assign the preset from the Configuration Presets library. You can assign it to up to 100 groups or ungrouped devices in a single operation.
Navigate to Configuration Presets in the left sidebar.
Select the checkbox next to the Wi-Fi Network preset you want to assign.
Click Assign.
Choose either Assign to Groups or Assign to Ungrouped Devices.
Select the target groups or ungrouped devices, then click Assign.
š” You can also assign a preset from a single group or ungrouped device: open its Settings tab, click Manage Presets in the top right corner, select the Security preset, and click Assign Presets.
See Configuration Presets for full details, including how to view a preset's assignments, switch or detach a preset, and how sub-groups and ungrouped devices receive their settings.
Troubleshooting: Wi-Fi preset not applying to devices
Preset assigned but network never appears on the headset
Preset assigned but network never appears on the headset
Wi-Fi settings are delivered over the device's existing connection. A headset that is offline cannot receive the preset you deployed ā it is a bootstrap problem. Confirm whether this is the cause:
The device shows as offline in the ArborXR portal (check its Last Online time).
The deployed network does not appear in the headset's own Wi-Fi settings.
Other online devices in the same group received the preset successfully.
If the device is offline, you have two options:
Add the network on the headset manually. Exit to the headset's native Wi-Fi settings and join the network from there. Once online, ArborXR syncs the preset down automatically.
Connect the device to any temporary network (a phone hotspot works). Once it checks in, it will receive the configured preset and can switch to it.
For full detail on this scenario, see Why isn't the WiFi network I added in ArborXR showing up on my headset?
Preset applied but profile changes or launcher settings still not syncing on a corporate network
Preset applied but profile changes or launcher settings still not syncing on a corporate network
If your devices can connect and install apps over a corporate or managed network but profile changes, launcher updates, or other configurations are not applying, the cause is often network validation. Android requires the network to pass a connectivity check before it will run managed background tasks. On restrictive corporate networks, the check endpoints are frequently blocked.
Signs this is affecting your devices:
Apps download and install correctly, but launcher or profile changes do not apply.
The same device works immediately when connected to a phone hotspot.
The device's network capabilities show TRUSTED but not VALIDATED.
Interim fix: ask your network team to allowlist the following connectivity check endpoints (exempt from SSL/TLS inspection):
connectivitycheck.gstatic.com (HTTP, port 80)
www.google.com (HTTPS, port 443)
captive.apple.com (HTTP, port 80 - Android fallback)
www.msftconnecttest.com (HTTP, port 80 - Android fallback)
ArborXR is working on a fix that writes the captive portal check URLs directly to device settings so they no longer depend on Meta's OEM Config API applying them correctly. If you are on a corporate network and experiencing this issue, contact support so we can track impact and notify you when the fix ships.