This topic answers common questions about Phased Deployment and helps you better understand how it works. Review this topic to learn why certain deployment behaviors occur, what limitations to expect, and how to manage phased deployments more effectively.
Q 1. Why can't I assign an assignment group to a Phased Deployment?
An assignment group that is already part of another Phased Deployment assignment cannot be added to a new one. This ensures existing deployments are not disrupted. To resolve this, you can either wait for the existing Phased Deployment to complete and transition to a direct assignment or delete the existing Phased Deployment assignment that includes the group.
Q 2. Why can't I assign a Progressive Rollout phase based on the total number of devices?
Progressive Rollout phases are percentage-based to ensure configured percentages are respected even as devices are added or removed from Smart Groups during deployment.
Consider a phased deployment targeting 1000 devices across three phases. Phase 1 targets the Test Devices Smart Group (100 devices). Phase 2 targets 30% of total devices (300 devices), and the Final Phase targets the remaining 60% (600 devices). If an additional 1000 devices are added to the Test Devices group, the total device count doubles to 2000. Due to this increase in devices, Phase 2 and the Final Phase are no longer reaching their set percentages. Phase 2 was set to reach 30%, but it only reaches 15% of the new total. This creates a confusing and inconsistent deployment experience for admins.
By restricting Progressive Rollout phases to include remaining device groups instead of the total number of devices, UEM ensures rollout targets remain accurate and predictable regardless of how Smart Group membership changes over time.
Q 3. How can I ensure deployment progresses to the next phase only at a specific time of the day?
This can be achieved by configuring a deployment time against the setting ‘Deployment Begins’ and selecting the option ‘Apply start time to all phases'. This ensures deployment progresses only at the configured time, even if automatic progression rules are met earlier.
Q 4. How can I configure deployment to occur only during specific days of the week or within specific time windows of a day?
There is currently no provision to configure such a deployment today.
Q 5. Does the percentage configured against Progressive Rollout phases account for excluded smart groups?
No. The system attempts to deploy the resource to devices as per the configured percentage. For example, if 100 devices remain for Progressive Rollout phases and a phase is configured to target 40%, the UEM targets 40 devices. If 20 devices are excluded, UEM targets 40 devices out of the remaining 80 — still honoring the configured 40%. If exclusions reduce the available device count to the point where the configured percentage cannot be met, UEM targets all available devices.
In short, UEM always attempts to honor the configured percentage against available devices, with the least impact from exclusions.
Q 6. On what basis are devices distributed across Progressive Rollout phases?
Devices are randomly distributed based on their unique identifier. The system attempts to first map online devices to phases, followed by offline devices.
Q 7. Why is the device count of the Final Phase zero?
If you have assigned all devices of the targeted Assignment Groups in previous phases, the Final phase does not have any devices to target.
Q 8. Why am I not able to edit target Assignment Groups or change phase configurations after my Phased Deployment assignment is published?
You cannot edit phased deployment configurations or date and time post-publish. However, you can change the deployment method and rules for upcoming phases post-publish.
Q 9. Why do I not see devices assigned to phases soon after I publish the Phased Deployment assignment?
Devices won’t be visible on the Phase level Deployment Tracking view just after the assignment is published. It may take up to 6 hours from the time a Phased Deployment assignment is published for all targeted devices to be visible on the Phased Deployment Tracking view. This happens because a device gets assigned to a phase only when it either checks in or undergoes a scheduled offline check-in.
Q 10. Why does the deployment not progress from phase 1 to phase 2 even though the configured Automatic progression rules have been met?
The first phase remains active for 6 hrs from the time a Phased Deployment assignment is published. This allows devices enough time to check in and get mapped to phases, ensuring deployment does not progress prematurely to the next phase. However, an admin may choose to manually advance to the next phase, overriding this default behaviour at their own discretion.
Q 11. Even though all the configured Automatic progression rules are met, why hasn't the deployment progressed to the next phase?
It may take half an hour for a deployment to progress to the next phase even after all automatic progression rules are met. This is because the job that evaluates the progression rules runs once every half hour.
Q 12. Why do I not see some devices of the ongoing phase as ‘Currently Assigned’ on the application’s Deployment Tracking view?
When deployment progresses to the next phase, some devices in the newly activated phase might not immediately appear as Currently Assigned in the app’s Deployment Tracking view. This occurs because a device must check in after the phase begins for its assignment state to be updated. Until that check‑in happens, the device is considered scheduled for app delivery and is therefore not shown as Currently Assigned.
Q 13. Why is my device not visible on Phase Deployment Tracking even after it has checked in?
There can be many reasons for it, as follows:
- Device is targeted to a yet-to-start phase and is assigned to the same app through another assignment, a closer organization group, or assigned to a different version of the app.
- Device has checked in before it was labeled to a Progressive Rollout phase. A device targeted through such a phase needs to be labeled to a phase before it becomes visible in the Phased Deployment tracking view. This discrepancy gets resolved once the device checks in post-labeling. In the most likely scenario, all devices are expected to remain visible against their phases on the Phase Deployment tracking view for up to 6 hours from the time of assignment publication.
Q 14. Why am I not able to export a list of devices mapped to a phase or export all devices of the phased deployment?
The ability to export devices deployed through a phased assignment is not currently available.
Q 15. Why do I see the following error?
In rare cases, the system may fail to assign some devices to their intended phases. When this occurs, the app cannot be delivered to the affected devices even when they check in during the targeted phase. This may prevent the deployment from completing as intended. If you encounter this, delete the assignment and create a new one.
Q 16. Do devices assigned through phased deployment but offline for over 30 days become visible on the Phase Deployment tracking page?
Yes. All devices, irrespective of their check-in status, will be mapped to phases within 6 hours of publishing a phased assignment. Offline devices undergo a scheduled offline evaluation once every 6 hours.
Q 17. Can I deploy VPP apps through phased deployment?
No. Phased Deployment is currently supported only for internal apps.
이 페이지가 도움이 되었나요?