Relay servers cache and distribute internal apps to Windows devices on a local network. Instead of each device downloading content directly from the cloud, a relay server downloads the app once and delivers it to nearby devices. This reduces bandwidth consumption and improves delivery speed, making it well-suited for low-bandwidth environments or offline sites such as stores and factories. For more informaton on Relay Servers and their configuration, see Relay Servers.
Supported Apps and Formats
Relay Server delivery supports apps distributed through Software Distribution (SFD), in the following formats: MSI, ZIP, and EXE. The following app types are also eligible for Relay Server delivery:
- Internal apps
- EAR apps
- Apps imported using a link to Workspace ONE UEM, provided the app binary is hosted on UEM
Unsupported apps and formats: Apps delivered through Device Management including Appx, MSIX, and Office apps are not supported. Apps uploaded as a direct link without the Download and Distribute through Workspace ONE UEM Platform option enabled are also not delivered through Relay Server.
Enabling Relay Server Delivery
Relay delivery is disabled by default and must be explicitly enabled for each app using the Relay Server Content Transfer toggle. Enabling Relay delivery for one app does not automatically apply it to other apps. Push, Pull, and RSCC Relay Servers are all supported
Note: App delivery is never blocked. There is no option to restrict delivery only to a Relay Server. Devices always fall back to other sources such as CDN/P2P/DS if the Relay Server is unavailable or seeding is incomplete. So, if the delivery through Relay Servers is critical, it is recommended to let the app complete the seeding to Relay Servers before before assigning the app to devices.
Benefits of Relay Server Support for Internal Windows Apps
- Reduced bandwidth consumption: Large application packages are cached locally on Relay Servers, significantly reducing Internet usage and WAN traffic. Devices download from a nearby server instead of pulling from the cloud individually.
- Faster app delivery: Devices receive apps from a local Relay Server on the same network rather than downloading over the WAN, speeding up deployment times.
- Support for low-bandwidth or offline environments: Stores, factories, airports, and similar sites with limited connectivity benefit from local content distribution.
- Admin-controlled delivery: Admins can selectively activate relay delivery per app using a toggle, giving precise control rather than applying relay behavior to all apps by default.
Configure Relay Server for Internal Windows Applications
You can activate relay server delivery for internal applications. This configuration allows you to control exactly which applications use the relay server network.
Prerequisites
Before you can deliver internal applications through a relay server, ensure that your environment meets the following requirements:
- Workspace ONE UEM 2607 or later.
- Workspace ONE Intelligent Hub 26.07 or later installed on target devices. Devices on the older Intelligent Hub version will continue to skip download through Relay Server.
- Relay servers (Push, Pull, or Relay Server Cloud Connector) are configured and active at the appropriate organization group levels.
Procedure
-
Navigate to Resources > Apps > Native Apps > Add and click Application File.
-
In the Add Application window, click Upload and choose the application file and click Save.
-
In the Add Application window, enter all the mandatory fields and click Continue.
-
Select the Deployment option, enter all the mandatory fields, activate Relay Server Content Transfer by changing the toggle setting to Yes. For more information, see Deploy Internal Applications on your Devices topic.
Note: If you activate this setting but no relay servers are configured for the organization group, a warning appears. You can still continue, and devices will fall back to downloading the application from the Content Delivery Network (CDN), Peer-to-Peer (P2P), or Device Services.
-
Click Save and Assign to begin seeding the application to all applicable relay servers in the OG hierarchy. Omnissa recommends you click Save and Assign and wait for the app to get seeded before assigning the app to the smart groups or devices.
-
In the Distribution screen, enter the mandatory fields and save the details.
Relay Server Seeding Status
To view the status of apps across all the applicable Relay Servers, navigate to Resources > Native Apps > Apps > List View and select the application and click Relay Server Status. The queue number will always start from 1 and goes to 0 when seeding is completed. The following image shows a snapshot of a Relay Server seeding status.
Important Considerations
- Fastlane delivery is triggered for apps distributed through a Relay Server. To ensure Fastlane works as expected, Omnissa recommends completing the seeding process before assigning the app to devices.
- Only the app binary is delivered through the Relay Server. App configurations and scripts are downloaded directly from Workspace ONE UEM at device check-in.
- Workflow-delivered apps with Relay Server enabled continue to use the Relay Server for delivery.
- When an app is deleted or retired from the console, it is automatically queued for removal from all associated Relay Servers to free up storage space.
¿Le resultó útil esta página?