Managing rollouts
Review rollout progress, investigate exceptions, and choose the next safe action.
Review rollout status and follow rollout progress after scheduling.
Use this page when you need to monitor active rollouts, confirm completion, or investigate rollout issues.
When to use this page
Use this page when you need to:
confirm a rollout actually started
understand whether download or install work is still moving
decide whether the next action is monitor, extend, or modify
Before you start
Confirm that:
the rollout has already been created or scheduled
you know whether you are tracking one device, one batch, or multiple rollout jobs
the software, parameter, or content package was prepared correctly before scheduling
If you still need to prepare or schedule the rollout, start here:
What managing rollouts includes
Use rollout management to:
review rollout progress after submission
check whether downloads or installs completed
identify rollouts that need follow-up
track rollout activity across one device or many devices
Monitor rollout progress
After a rollout starts, review its status to confirm whether it is progressing as expected.
Track:
rollout state
target devices or batches
current progress
completed or failed rollout activity
Review rollouts in this order
Use this order to avoid missing the root cause:
confirm the rollout exists and targets the intended scope
confirm the rollout state matches the current schedule window
review failed or incomplete work before you resubmit anything
What to check first
Start with these questions:
did the rollout start at the expected time
is the rollout affecting the intended device or batch set
do failures point to one device group or a broader issue
Record the rollout name, batch, expected target count, and schedule window. Use this baseline when comparing progress or investigating exceptions.
When to review a rollout
Review rollout status when you need to:
confirm that a scheduled rollout has started
check whether the deployment completed successfully
decide whether another rollout or update is required
investigate devices that did not receive the expected update
Common rollout outcomes
Use these checks to interpret what you see:
The rollout is active — continue monitoring until devices move to a completed state
The rollout is complete — confirm the intended devices received the expected package or change
The rollout is incomplete or failed — review the affected device set before you extend or reschedule
Choose the next action
Use the rollout state to decide what happens next:
Within its schedule window — keep monitoring.
Complete with the expected scope — record the result.
Unexpected or incomplete — investigate the affected devices first.
Do not submit a duplicate rollout while the original rollout needs review.
Common problems to check
Use these checks to narrow the issue:
The rollout never started — confirm the schedule window and the target scope
Some devices completed and others did not — compare the affected devices by model, status, or connectivity
The rollout is still running longer than expected — confirm devices are checking in and still eligible for the rollout
You need to change the rollout — use the modify flow instead of creating a duplicate rollout
The scope is unexpected — stop follow-up changes and verify the rollout and batch selection
Related rollout tasks
Use these pages based on what you need to do next:
Create a batch rollout — create a rollout for multiple devices
Create rollout for a single device — create a rollout for one device
Create a new batch for rollout — extend an existing rollout
Modify existing rollout — update a saved rollout or cancel a rollout in progress
Monitor estate-wide rollouts — review broader rollout activity and status
Result
You can confirm rollout progress and decide whether more action is needed.
Next steps
Last updated
Was this helpful?