Prerequisites

Confirm access, device, payload, and schedule readiness before starting a rollout.

Complete these checks before you schedule a rollout.

Access and permissions

Confirm that you can create or manage rollouts for the target estate.

See User privileges.

Device readiness

Before you continue, confirm that:

• the target device is already boarded in Device Management
• the device status is Pending Hierarchy or Active
• the device is visible in the customer, estate, or hierarchy you manage

Rollout payload readiness

Confirm that the item you want to deploy is ready:

• software packages are already uploaded before software rollouts
• content packages are already uploaded before content rollouts
• parameter changes are already defined before parameter rollouts

See:

• Software management
• Content management
• Parameter management

Scheduling checks

Before you start the rollout, confirm that:

• the selected device does not already have a conflicting rollout
• you know whether the rollout targets one device or a batch
• you are ready to choose the download and install schedule

Record the rollout name, payload version, target count, and schedule window. Use this baseline to verify the rollout summary before launch.

Final go or no-go check

Before submission, record the payload version, target count, and schedule. Stop if the payload, device scope, or schedule differs from the deployment plan.

Next step

When these checks are complete, continue to Schedule rollouts.