> For the complete documentation index, see [llms.txt](https://docs.adaptiva.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adaptiva.com/patch/advanced-settings/deployment-waves.md).

# Deployment Waves

Deployment Waves allow the deployment of patches progressively to devices contained in different Business Units.

Deployment Waves allow you to configure a phased deployment of patches to groups of devices contained in Business Units.

You can define multiple waves of Business Units. A patch strategy will deploy to the first wave, and then, if defined criteria are met, progress to deploying to the next wave sequentially, until all wave deployments are complete or a condition is met that stops the strategy.

Typically, a strategy involving deployment waves will implement one of the following transitions between waves:

* **Delay transition:** the next wave will wait for a set amount of time, before deploying, giving the operator time to stop the strategy if the previous wave ran into issues.
* **Approval transition:** approvals must be granted before the next wave can deploy.
* **Success Gate Transition:** A defined percentage of patches must succeed before the next wave can deploy.

Because Waves execute in top-to-bottom order, less critical Business Units appear higher in the priority. This prioritizes deployment to non-mission critical business units or smaller groups of endpoints first, followed by more critical or larger groupings of endpoints.

When you configure deployment rings in a Simple Strategy, the server automatically creates a corresponding Deployment Wave object called ***\<simple strategy name>*****&#x20;: Deployment Waves**.

## Using Deployment Wave Entries

Entries for Deployment Wave settings exist in the object templates for Advanced Strategies, Deployment Channels, and Customized Products templates. All methods use the same process.

### Create a Wave Entry

1. Select **Advanced Settings > Intent Schema > Deployment Waves**.
2. Select **+ New**.
3. Enter a unique **Name** and **Description**.
4. Select **Add Wave**.

   ![](https://2503798551-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7VJNM00p5XQ4pMWqCu8y%2Fuploads%2Fgit-blob-34f239d83a8295684dfcb1a2c9fbad2a1242ffae%2Fadd-wave.png?alt=media)
5. Select **+ Create Wave Entry**.

   ![](https://2503798551-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7VJNM00p5XQ4pMWqCu8y%2Fuploads%2Fgit-blob-07133eef151f04b321a3787694cc49963bf19860%2Fimage2.png?alt=media)
6. Select **Browse** next to **Add Business Unit**.
   1. Navigate to and select the **Business Unit** to which the Wave Entry applies.
   2. Select **OK** to return to the **Create Wave Entry** dialog.

      ![](https://2503798551-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7VJNM00p5XQ4pMWqCu8y%2Fuploads%2Fgit-blob-de0e6240d3ae9497dbf4dc5433da793bf513a883%2Fimage3.png?alt=media)
7. Expand the **Include Child Business Units** menu to include one or more child Business Units of the selected parent.
8. Select **Create Wave Entry** to return to the Deployment Wave template.
9. Repeat steps 4 through 8 for each additional wave entry you want to create.
10. Select **Save** to save your progress.

### Edit or Remove a Wave Entry

1. Select **Advanced Settings > Intent Schema > Deployment Waves**.
2. Open the **Deployment Wave template** you want to change.
3. Scroll down to the Deployment Waves table that shows the Wave Entry you want to edit or remove.
4. Select the **ellipsis (...)** in the **Actions** column, and then choose one of the following options:
   * Select **Remove Wave Entry** to remove the Wave.
   * Select **Edit the Remote Wave Entry** to make any necessary changes to the Wave.
5. Select **Save** to save your progress.

## Open and Save a Deployment Wave Template

1. In the left navigation menu of the Patch Management Dashboard, select **Deployment Waves**.
2. Select the **Name** of a template to open it, and then save the template with a new title:
3. In the upper-left of the dialog, select **More**, and then select **Save As**.
4. Enter a new name for the template, and then select **Save as**. This returns you to a copy of the template with the new name.
5. Enter a detailed **Description** of the process covered in this template, or leave the prepopulated description.