For the complete documentation index, see llms.txt. This page is also available as Markdown.

Rollouts

Prepare, schedule, and monitor controlled device deployments.

Use Rollouts to deploy software, parameters, or content to one device or many devices.

Rollouts help you manage changes across the estate without updating devices one by one.

Use this page to choose a deployment path, validate readiness, and monitor the result.

Before you start

Confirm that:

  • your role allows you to create or manage rollouts

  • the target devices are already onboarded and available in Device Management

  • the software, parameter set, or content package is ready to deploy

Review access and rollout readiness:

Do not schedule a rollout until you have confirmed the target scope and package.

Choose a rollout path

What rollouts support

Use rollouts to:

  • deploy software updates remotely

  • apply parameter changes to devices

  • distribute content packages across the estate

  • schedule downloads and installs by time or maintenance window

  • monitor rollout progress and results

Rollout workflow

Most rollout work follows this flow:

  1. Prepare the software, parameters, or content.

  2. Create the rollout for one device or many devices.

  3. Schedule the download and install.

  4. Monitor progress and resolve any issues.

Record the deployment scope and intended schedule before starting. Compare them with the rollout summary before launch.

Choose what to deploy

Software

Use software rollouts when you need to install or update application packages on devices.

Parameters

Use parameter rollouts when you need to update device configuration values.

Content

Use content rollouts when you need to distribute files or media used by the device estate.

Start with Content management.

Common rollout tasks

Prepare rollout content

Before scheduling a rollout, make sure the package or configuration is available in Device Management.

Use:

Schedule a rollout

Use the scheduling pages to target one device, a batch of devices, or an existing rollout.

Use:

Monitor rollout progress

Track rollout status after submission. Confirm progress, completion, or failure before closing the deployment task.

Use:

Result

Rollouts let you prepare, schedule, and track device changes from one workflow. A completed rollout has the expected package, target scope, and outcome.

Next steps

Last updated

Was this helpful?