Accelerating Resource Delivery with Fast Lane Deployment

In modern Workspace ONE UEM environments, resources are delivered to devices when they check into the system, which usually happens once every 4 hours as part of their natural check in cycle. This design provides significant performance advantages for large-scale deployments compared to traditional Workspace ONE UEM.

However, this also means that a resource might not be available on a device for up to four hours because the installation or removal only occurs during the device’s check-in, which happens every four hours. There are scenarios where waiting for the standard 4-hour check-in cycle can impact business operations. These scenarios include new device enrollments, checkout of shared devices, delivery of critical security patches, and testing resource delivery in UAT environments. Therefore, a faster resource delivery mechanism is essential to address these critical needs.

The Fast Lane Deployment feature in Workspace ONE UEM addresses this need by enabling accelerated resource delivery during time‑sensitive scenarios. 

Fast Lane Deployment

Fast Lane Deployment accelerates the delivery of resources to devices, ensuring they reach their desired state without waiting for them to naturally check in.

For use cases eligible for Fast Lane delivery, UEM sends notifications to relevant devices to check in. Once devices check into the system, they are brought to their desired state.

Eligible Use Cases for Fast Lane Deployment

Fast Lane Deployment is initiated in the listed scenarios.

• Admin Actions - When an admin force-installs or removes a resource from a device. Admin can perform these actions either from the Workspace ONE UEM Console or through Workspace ONE UEM APIs.

• Device User Actions - When a device user removes or installs a resource through the Intelligent Hub on the device.

• Device Enrollments - For newly enrolled devices, to ensure all assigned resources are installed. This guarantees that the device reaches its desired state immediately, without waiting for the standard check-in interval.

• Tag or OG Updates - When devices undergo tag or Organization Group (OG) updates. This applies to updates made through various sources, including the UEM console, APIs, and Intelligence automations, and is not restricted by the number of devices involved.

• Freestyle Workflows Actions - When resources are to be installed or removed through Intelligence automations or Freestyle workflows.

• Compliance Actions - When either resource(s) must be removed, or a compliance profile must be installed on a device based on compliance policy evaluation.

• Check in check out of Shared Devices - When an end user uses a shared device, resources assigned to that user are sent to the device immediately. This happens by prompting the device to check into UEM. Similarly, all resources assigned to the user are removed from the device when the user checks in the device.

• Device Actions - When an admin performs a Query or Sync Device action from the UEM Console or when an end user performs a Sync Device action from the Intelligent Hub app.

• Applications and Profiles Publish - When devices added and removed during assignment updates are 20,000 or fewer for Internal Applications, Public Applications, and Profiles.

  1. Publishing new resources - When a new internal application, public application, or profile configured for ‘Auto’ delivery is published to 20,000 devices or fewer.

  2. Updating assignments - When updating assignments for existing applications and profiles that impact 20,000 devices or fewer. This is irrespective of whether the overall number of devices assigned to the resource exceeds 20,000.

     • Updating application deployment parameters
     • Creating and deleting assignments
     • Adding and removing assignment groups from existing assignments
     • Updating exclusion criteria

  3. Updating profile payloads - When updates are made to the payloads of existing profiles set to Auto delivery, provided the profile is assigned to 20,000 devices or fewer.

  4. Changing delivery type - When the delivery type of an Internal app, Public app, or Profile is changed from ‘Optional’ or ‘On-demand’ to ‘Auto’ and the number of devices assigned to the resource is 20,000 or fewer.

  5. Changing resource status - Fast Lane deployment is initiated when the status of an Internal App, Public App, or Profile changes (for example, retire, unretire, activate, deactivate, or delete) and the resource is assigned to 20,000 devices or fewer.

• Smart Group Rule Updates - When Smart Group rules are updated, such that the devices added and removed from the group are less than 20,000.

• Other Resource Types - Fast Lane deployment is initiated for Scripts, Sensors, Workflows, Windows MTD Profiles, SCEP and Credentials Profiles if they are assigned to 2000 devices or less.

Devices are notified to check in on a best-effort basis. The publishing of other resources in your environment can impact how quickly devices in your deployment receive notifications to check in.

Saving Network Bandwidth

By default, Fast Lane deployment is initiated when Internal apps, Public apps, and Profiles impacting 20,000 or fewer devices are published. However, delivering resources rapidly to a large number of devices can strain your network bandwidth, especially in environments with slower connectivity. To help manage bandwidth usage, you can request a lower delivery threshold by contacting the Omnissa Support team.

Use Cases Not Eligible for Fast Lane Deployment

Fast Lane deployment is not initiated in the listed scenarios:

• Device Attribute Changes - Updates to device attributes (such as user group, OS version, or enrollment type) that affect Smart Group membership do not initiate Fast Lane deployment.
• Offline Devices - Resources eligible for Fast Lane deployment cannot be delivered to offline devices because the devices cannot check‑into UEM. When these devices come online, the resources are delivered during the next check‑in.
• Scheduled Application Deployments - Fast Lane deployment is not initiated at the scheduled time for app assignments set for a future date.
• User groups: Users getting added or removed from user groups do not trigger Fast Lane delivery.