In modern Workspace ONE UEM environments, resources are delivered to assigned devices within a maximum of 4 hours from the time they are published, regardless of the number of devices targeted. 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 much faster than the default 4-hour check-in interval.
Here's how fast lane deployment works:
- When Workspace ONE UEM initiates Fast Lane Deployment, all devices assigned to the published resource receive proactive notifications to check in with the UEM server.
- Online devices receive notifications immediately, check in, install or remove resources, and reach their desired state.
- Offline devices fail to receive the check-in notification because of their offline status. When these devices come online, the resources are delivered during the next check‑in, which may occur up to four hours after the device reconnects.
Eligible Use Cases for Fast Lane Deployment
Fast Lane Deployment is initiated in the listed scenarios.
-
Resource Publish - When a resource configured for auto-delivery is assigned to 2000 devices or fewer. Types of resources eligible for Fast Lane delivery are Internal apps, Public apps, Profiles, Scripts, Sensors, Workflows, and Windows Mobile Threat Defence (MTD) profiles
-
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 - When an Intelligence automation or Freestyle Workflow is published to 2000 or fewer devices.
-
Compliance Actions - When either resource(s) must be removed, or a compliance profile must be installed on a device based on compliance policy evaluation.
-
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.
Use Cases Not Eligible for Fast Lane Deployment
Fast Lane deployment is not initiated in the listed scenarios:
-
Loss of resource assignment - Fast Lane deployment is not triggered for devices that lose resource assignment.
-
Target assignments exceeding 2,000 devices - Resources assigned to more than 2,000 devices are not eligible for Fast Lane deployment.
-
Smart Group rule updates - Changes to Smart Group rules do not initiate Fast Lane deployment for devices in the group.
-
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. Only changes to Organization Group (OG) or tags are eligible for this delivery type.
-
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, which may occur up to four hours after the device reconnects.
-
Scheduled Application Deployments - Fast Lane deployment is not initiated for app assignments set for a future date.
Was this page helpful?