Skip to content

Commit 38f3cfb

Browse files
Merge pull request #134869 from MGoedtel/task1783455b
updated UM Deploy updates and SvcLimits articles
2 parents 6e658cd + 77866e9 commit 38f3cfb

File tree

3 files changed

+7
-7
lines changed

3 files changed

+7
-7
lines changed

articles/automation/update-management/deploy-updates.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: How to create update deployments for Azure Automation Update Management
33
description: This article describes how to schedule update deployments and review their status.
44
services: automation
55
ms.subservice: update-management
6-
ms.date: 10/14/2020
6+
ms.date: 10/21/2020
77
ms.topic: conceptual
88
---
99

@@ -49,12 +49,12 @@ To schedule a new update deployment, perform the following steps. Depending on t
4949
> [!NOTE]
5050
> This option is not available if you selected an Azure VM or Arc enabled server. The operating system is automatically identified.
5151
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).
5353

5454
> [!NOTE]
5555
> This option is not available if you selected an Azure VM or Arc enabled server. The machine is automatically targeted for the scheduled deployment.
5656
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.
5858

5959
> [!NOTE]
6060
> 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
7878
7979
10. Use the **Recurrence** to specify if the deployment occurs once or uses a recurring schedule, then select **OK**.
8080

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).
8282

8383
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:
8484

@@ -106,7 +106,7 @@ To schedule a new update deployment, perform the following steps. Depending on t
106106
> [!NOTE]
107107
> When you're finished configuring the deployment schedule for a selected Arc enabled server, select **Review + create**.
108108
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.
110110

111111
## Schedule an update deployment programmatically
112112

4.38 KB
Loading

includes/azure-automation-service-limits.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: automation
55
author: mgoedtel
66
ms.service: automation
77
ms.topic: "include"
8-
ms.date: 10/14/2020
8+
ms.date: 10/21/2020
99
ms.author: magoedte
1010
ms.custom: "include file"
1111
---
@@ -55,4 +55,4 @@ The following table shows the limits for Update Management.
5555

5656
| **Resource** | **Limit**| **Notes** |
5757
|---|---|---|
58-
|Number of machines per update deployment|500||
58+
|Number of machines per update deployment|1000||

0 commit comments

Comments
 (0)