Manage rollouts

Move from rollout readiness to scheduling and monitoring without missing key checks.

Prepare, schedule, and monitor rollouts from one workflow.

Before you start

Confirm that:

• you know what type of rollout you need to run
• the target devices are already available in Device Management
• the software, parameters, or content are ready for deployment

Review these pages first:

• Prerequisites
• User privileges

1

1. Prepare rollout content

Add the files and configuration needed for the rollout.

Use one of these pages based on what you want to deploy:

• Software management
• Parameter management
• Content management

2

2. Schedule the rollout

Create the rollout for a single device or for a batch of devices.

Start here:

• Schedule rollouts

Then use the task that matches your rollout type:

• Create a batch rollout
• Create rollout for a single device
• Modify existing rollout

3

3. Monitor rollout progress

Track rollout status after submission.

Use these pages to review current rollout progress and results:

• Managing rollouts
• Monitor estate-wide rollouts

Choose the right rollout path

Use these quick rules:

• use Software management when the rollout installs or updates application packages
• use Parameter management when the rollout changes configuration values
• use Content management when the rollout distributes files or media
• use Create rollout for a single device when one device needs a targeted rollout
• use Create a batch rollout when many devices need the same rollout

What to verify before submission

Check these points before you create or schedule a rollout:

• the package, parameter set, or content is the correct one
• the target device or batch is correct
• the schedule matches the intended install window
• the rollout type matches the operational goal

Record the rollout name, payload version, target count, and schedule window before submission. Stop and correct the rollout if its summary differs from this baseline.

Record the rollout name, payload version, target scope, and schedule window. Use this record to verify the submitted rollout and investigate failures.

Verify the result

After you submit and monitor the rollout, confirm that:

• the rollout was created with the expected scope
• the rollout reaches the expected status after submission
• any failures or delays are visible in the monitoring pages
• the next action is clear: monitor, modify, or create another rollout
• the rollout record shows the intended name, scope, and schedule
• the rollout scope and timing match the recorded deployment plan

Result

You can move from rollout readiness to rollout scheduling and monitoring with the right checks in the right order.

Next steps

• Schedule rollouts — choose the exact rollout task
• Managing rollouts — inspect rollout status and details
• Monitor estate-wide rollouts — review broader rollout progress
• Rollouts — return to the rollout hub