You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/automation/update-management/deploy-updates.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: How to create update deployments for Azure Automation Update Management
3
3
description: This article describes how to schedule update deployments and review their status.
4
4
services: automation
5
5
ms.subservice: update-management
6
-
ms.date: 10/14/2020
6
+
ms.date: 10/21/2020
7
7
ms.topic: conceptual
8
8
---
9
9
@@ -49,12 +49,12 @@ To schedule a new update deployment, perform the following steps. Depending on t
49
49
> [!NOTE]
50
50
> This option is not available if you selected an Azure VM or Arc enabled server. The operating system is automatically identified.
51
51
52
-
5. In the **Groups to update (preview)** region, define a query that combines subscription, resource groups, locations, and tags to build a dynamic group of Azure VMs to include in your deployment. To learn more, see [Use dynamic groups with Update Management](configure-groups.md).
52
+
5. In the **Groups to update** region, define a query that combines subscription, resource groups, locations, and tags to build a dynamic group of Azure VMs to include in your deployment. To learn more, see [Use dynamic groups with Update Management](configure-groups.md).
53
53
54
54
> [!NOTE]
55
55
> This option is not available if you selected an Azure VM or Arc enabled server. The machine is automatically targeted for the scheduled deployment.
56
56
57
-
6. In the **Machines to update** region, select a saved search, an imported group, or pick **Machines** from the dropdown menu and select individual machines. With this option, you can see the readiness of the Log Analytics agent for each machine. To learn about the different methods of creating computer groups in Azure Monitor logs, see [Computer groups in Azure Monitor logs](../../azure-monitor/platform/computer-groups.md). You can include up to a maximum of 500 machines in a scheduled update deployment.
57
+
6. In the **Machines to update** region, select a saved search, an imported group, or pick **Machines** from the dropdown menu and select individual machines. With this option, you can see the readiness of the Log Analytics agent for each machine. To learn about the different methods of creating computer groups in Azure Monitor logs, see [Computer groups in Azure Monitor logs](../../azure-monitor/platform/computer-groups.md). You can include up to a maximum of 1000 machines in a scheduled update deployment.
58
58
59
59
> [!NOTE]
60
60
> This option is not available if you selected an Azure VM or Arc enabled server. The machine is automatically targeted for the scheduled deployment.
@@ -78,7 +78,7 @@ To schedule a new update deployment, perform the following steps. Depending on t
78
78
79
79
10. Use the **Recurrence** to specify if the deployment occurs once or uses a recurring schedule, then select **OK**.
80
80
81
-
11. In the **Pre-scripts + Post-scripts (Preview)** region, select the scripts to run before and after your deployment. To learn more, see [Manage pre-scripts and post-scripts](pre-post-scripts.md).
81
+
11. In the **Pre-scripts + Post-scripts** region, select the scripts to run before and after your deployment. To learn more, see [Manage pre-scripts and post-scripts](pre-post-scripts.md).
82
82
83
83
12. Use the **Maintenance window (minutes)** field to specify the amount of time allowed for updates to install. Consider the following details when specifying a maintenance window:
84
84
@@ -106,7 +106,7 @@ To schedule a new update deployment, perform the following steps. Depending on t
106
106
> [!NOTE]
107
107
> When you're finished configuring the deployment schedule for a selected Arc enabled server, select **Review + create**.
108
108
109
-
15. You're returned to the status dashboard. Select **Deployment schedules** to show the deployment schedule that you've created.
109
+
15. You're returned to the status dashboard. Select **Deployment schedules** to show the deployment schedule that you've created. A maximum of 500 schedules are listed. If you have more than 500 schedules and you want to review the complete list, see the [Software Update Configurations - List](/rest/api/automation/softwareupdateconfigurations/list) REST API method using version 2019-06-01 or higher.
0 commit comments