How to optimize local streaming from a CloudXR Server Workstation
These troubleshooting steps apply to local streaming setups between a CloudXR server workstation and a headset (e.g., Apple Vision Pro). For general recommendation regarding CloudXR streaming, please refer to this section.
Verify firewall configuration
Ensure your firewall allows communication between the CloudXR server and connected devices. You may need to open dedicated ports and/or whitelist IP addresses, take a look to this article listing all required ports.
Check for security software interference
Some corporate security or endpoint protection tools can block Innoactive executables or network traffic, preventing local streaming.
Common causes include:
Standard antivirus or endpoint protection rules.
Windows Defender Advanced (Enterprise layer), which can block local UDP traffic even when the standard Defender allows it.
If you notice that executables stop shortly after starting or connections fail to establish, contact your IT administrator to:
Whitelist or exclude:
cloudxr-service.exePortal-VRED-Plugin-Helper.exe
Verify that no network-level policies (such as Defender Advanced) are restricting local connections.
Review network and Wi-Fi configuration
Connection instability is often related to Wi-Fi or network setup.
Make sure to:
Use only one active Network Interface (disable others).
Change the Network Interface Card (NIC) profile type from Public to Private.
Connect both the headset and server to the same 5 GHz Wi-Fi.
Disable 2.4 GHz on your router.
Select a stable, uncongested 5 GHz channel:
Start with auto; if unstable, try 44 or 149 (149 = US/Canada only).
In areas near airports or radar sources, channels 44 and 149 are usually more stable.
Retest if performance drops
If streaming performance suddenly degrades, your router may have switched channels.
Re-evaluate your setup starting from step 3 and manually select another clear channel.l.
Apple Vision Pro configuration for CloudXR server connectivity
In enterprise environments, default visionOS settings—especially privacy and network-related features—may conflict with corporate IT policies and significantly delay onboarding if not identified early.
A common example is Private Wi-Fi Address (randomized MAC address), which is enabled by default in visionOS. Some corporate networks require a fixed MAC address per device for network access control. If not adjusted, this can block connectivity until policies are aligned.
Apple’s Platform Deployment Guide provides a central overview of supported deployment and management options:
https://support.apple.com/guide/deployment/welcome/web
Vision Pro–specific restrictions, payloads, and commands for visionOS are documented here:
https://support.apple.com/guide/deployment/deploy-apple-vision-pro-dep18daf732d/web
These capabilities are exposed via Apple’s MDM API, but availability depends on the MDM vendor’s level of visionOS support:
https://developer.apple.com/documentation/devicemanagement