Overview
You provisioned a WiFi network to a device or group via ArborXR, but the headset never picks it up. The network doesn't appear in the headset's WiFi list, and the device may show as offline in the portal.
Why this happens
WiFi settings are delivered to the headset over its existing connection. A headset with no working network can't receive the WiFi credentials you just deployed. It's a chicken-and-egg problem: the settings that would get the device online can only arrive once the device is online.
This usually shows up when a headset was enrolled without WiFi included, moved to a new location or network, or sat offline long enough that its saved network no longer exists.
How to confirm this is what you're hitting
The device shows offline in the portal (check its Last Online time).
The deployed network never appears in the headset's own WiFi settings.
Other devices that were already online received the same network fine.
How to fix it
Option 1: add the network on the headset manually. Exit to the headset's native settings and join the network there. Once it's online, everything you deployed in ArborXR syncs down, including any other WiFi networks. If the device is locked in Kiosk Mode, see How do I manually connect to a WiFi network on my Meta Quest device in ArborXR Kiosk Mode.
Option 2: connect it to any temporary network. A phone hotspot works. The device only needs a connection long enough to check in and pull its configuration; after that it will know about the networks you deployed and can switch to them.
How to prevent it
When changing networks (a new SSID or password), deploy the new network while devices are still connected to the old one, and only retire the old network after devices have picked up the new one. If the old network goes away first, every affected headset needs the manual treatment above.
Still stuck?
If the device is online but a deployed network still doesn't appear, send us the device serial number and the network name and we'll take a look.