Business unit rollout processes define which clients receive patches first and are the last step before patches reach clients. For example, a Business Unit rollout process can define rolling out to clients in batches of one hundred to allow administrators to view progress and catch any errors that occur before rolling out to additional devices.
After Patching Processes and Deployment Channel processes supply the details for the required activity, they delegate the rollout task to each Business Unit. The Business Unit manages its own rollout based on the customized All Clients Rollout Process workflow.
Before creating a custom Rollout Processes, enter a support ticket and request help from
|
The Rollout process executes a workflow that queries information contained within a Business Unit template, such as Approval Chains, Notification Chains, and Related Business Units. The Business Unit uses this information to control the approval and deployment logic for new patches. The Rollouts also perform the actual client deployment to devices within the Business Unit.
New child Business Unit configurations automatically inherit the Rollout Process from the parent Business Unit. In most cases, this is the All Clients Rollout Process.
The Business Unit template you are editing might use a Rollout Process inherited from a parent Business Unit. Before you can change an inherited Rollout Process, you must turn off inheritance.