Skip to content

Commit 0510a7c

Browse files
committed
feedback incorporated, updated toc, edited the date and procedure
1 parent 5de195c commit 0510a7c

File tree

6 files changed

+26
-14
lines changed

6 files changed

+26
-14
lines changed

articles/update-center/manage-multiple-machines.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Manage multiple machines in update management center (preview)
33
description: The article details how to use Update management center (preview) in Azure to manage multiple supported machines and view their compliance state in the Azure portal.
44
ms.service: update-management-center
5-
ms.date: 04/11/2023
5+
ms.date: 04/26/2023
66
ms.topic: conceptual
77
author: SnehaSudhirG
88
ms.author: sudhirsneha
@@ -13,8 +13,8 @@ ms.author: sudhirsneha
1313
**Applies to:** :heavy_check_mark: Windows VMs :heavy_check_mark: Linux VMs :heavy_check_mark: On-premises environment :heavy_check_mark: Azure Arc-enabled servers.
1414

1515
> [!IMPORTANT]
16-
> - For a seamless scheduled patching experience, we recommend that for all Azure VMs, you update the patch mode to *Azure orchestrated with user managed schedules (preview)* before April 30, 2023. If you fail to update the patch mode before April 30, 2023, you can experience a disruption in business continuity because the schedules will fail to patch the VMs.[Learn more](prerequsite-for-schedule-patching.md).
17-
> - To update the patch mode, go to **Update management center (Preview)** home page > **Update Settings**. In **Change update settings**, add the machines and under **Patch orchestration**, select *Azure orchestrated with user managed schedules (Preview)*.
16+
> - For a seamless scheduled patching experience, we recommend that for all Azure VMs, you update the patch mode to *Azure orchestrated with user managed schedules (preview)* before **May 19, 2023**. If you fail to update the patch mode before **May 19, 2023**, you can experience a disruption in business continuity because the schedules will fail to patch the VMs.[Learn more](prerequsite-for-schedule-patching.md).
17+
> - To update the patch mode, go to **Update management center (Preview)** home page > **Update Settings**. In **Change update settings**, add the machines and under **Patch orchestration**, select *Azure-orchestrated-safe deployment*.
1818
1919
This article describes the various features that update management center (Preview) offers to manage the system updates on your machines. Using the update management center (preview), you can:
2020

articles/update-center/prerequsite-for-schedule-patching.md

Lines changed: 14 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Configure schedule patching on Azure VMs to ensure business continuity in update management center (preview).
33
description: The article describes the new prerequisites to configure scheduled patching to ensure business continuity in Update management center (preview).
44
ms.service: update-management-center
5-
ms.date: 04/24/2023
5+
ms.date: 04/26/2023
66
ms.topic: conceptual
77
author: snehasudhirG
88
ms.author: sudhirsneha
@@ -16,13 +16,23 @@ This article is an overview on how to configure Schedule patching and Automatic
1616

1717
Currently, you can enable [Automatic guest VM patching](../virtual-machines/automatic-vm-guest-patching.md) (Autopatch) by setting the patch mode to **Azure-orchestrated**/**AutomaticByPlatform** on Azure portal/REST API respectively, where patches are automatically applied during off-peak hours.
1818

19-
For customizing control over your patch installation, you can use [schedule patching](updates-maintenance-schedules.md#scheduled-patching) to define your maintenance window. You can enable [schedule patching](scheduled-patching.md#schedule-recurring-updates-on-single-vm) by setting the patch mode to **Azure orchestrated**/**AutomaticByPlatform** and attaching a schedule to the Azure VM. To patch your machines, the VM ARM properties to differentiate between **schedule patching** or **Automatic guest VM patching** were the same as the patch mode in both cases is set to *Azure-Orchestrated*.
19+
For customizing control over your patch installation, you can use [schedule patching](updates-maintenance-schedules.md#scheduled-patching) to define your maintenance window. You can [enable schedule patching](scheduled-patching.md#schedule-recurring-updates-on-single-vm) by setting the patch mode to **Azure orchestrated**/**AutomaticByPlatform** and attaching a schedule to the Azure VM. So, the VM properties couldn't be differentiated between **schedule patching** or **Automatic guest VM patching** as both had the patch mode set to *Azure-Orchestrated*.
2020

21-
So, in some instances, when you remove the schedule from a VM, there is a possibility that the VM may be auto patched for critical or security patches and subsequently rebooted. To avoid such accidental or unintentional patching, a new prerequisite has been introduced - **ByPassPlatformSafetyChecksOnUserSchedule**, when set to *true* accurately determines the VMs for scheduled patching and ensures that the VMs with this property set to *true* will no longer be patched as a path of the Automatic VM Guest Patching schedule when the VMs do not have an associated maintenance configuration.
21+
Additionally, in some instances, when you remove the schedule from a VM, there is a possibility that the VM may be auto patched and rebooted. To overcome the limitations, we have introduced a new prerequisite - **ByPassPlatformSafetyChecksOnUserSchedule**, which can now be set to *true* to identify a VM using schedule patching. It means that VMs with this property set to *true* will no longer be auto patched when the VMs don't have an associated maintenance configuration.
2222

2323
> [!IMPORTANT]
2424
> For a continued scheduled patching experience, you must ensure that the new VM property, *BypassPlatformSafetyChecksOnUserSchedule*, is enabled on all your Azure VMs (existing or new) that have schedules attached to them **before May 19, 2023**. This setting will ensure machines are patched using your configured schedules and not autopatched. Failing to enable the pre-requisite will give an error that the prerequisites aren't met.
2525
26+
## Find VMs with associated schedules
27+
28+
To identify the list of VMs with the associated schedules for which you have to enable new VM property, follow these steps:
29+
30+
1. Go to **Update management center (Preview)** home page and select **Machines** tab.
31+
1. In **Patch orchestration** filter, select **Azure-orchestrated safe deployment**.
32+
1. Use the **Select all** option to select the machines and then select **Export to CSV**.
33+
1. Open the CSV file and in the column **Associated schedules**, select the rows that have an entry.
34+
In the corresponding **Name** column, you can view the list the VMs to which you would need to enable the **ByPassPlatformSafetyChecksOnUserSchedule** flag.
35+
2636

2737
## Enable schedule patching on Azure VMs
2838

@@ -69,7 +79,7 @@ To update the patch mode, follow these steps:
6979
1. In **Select resources**, select your VMs and then select **Add**.
7080
1. In **Change update settings**, under **Patch orchestration**, select *Customer managed schedules* and then select **Save**.
7181

72-
Attach a schedule after you complete the above steps and to check if the **BypassPlatformSafetyChecksOnUserSchedule** is enabled, go to **JSON View** in the Virtual machine home page.
82+
Attach a schedule after you complete the above steps.To check if the **BypassPlatformSafetyChecksOnUserSchedule** is enabled, go to **Virtual machine** home page > **Overview** tab > **JSON View**.
7383

7484
# [REST API](#tab/new-prereq-rest-api)
7585

articles/update-center/scheduled-patching.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Scheduling recurring updates in Update management center (preview)
33
description: The article details how to use update management center (preview) in Azure to set update schedules that install recurring updates on your machines.
44
ms.service: update-management-center
5-
ms.date: 04/11/2023
5+
ms.date: 04/26/2023
66
ms.topic: conceptual
77
author: SnehaSudhirG
88
ms.author: sudhirsneha
@@ -13,8 +13,8 @@ ms.author: sudhirsneha
1313
**Applies to:** :heavy_check_mark: Windows VMs :heavy_check_mark: Linux VMs :heavy_check_mark: On-premises environment :heavy_check_mark: Azure Arc-enabled servers.
1414

1515
> [!IMPORTANT]
16-
> - For a seamless scheduled patching experience, we recommend that for all Azure VMs, you update the patch mode to *Azure orchestrated with user managed schedules (preview)* before April 30, 2023. If you fail to update the patch mode before April 30, 2023, you can experience a disruption in business continuity because the schedules will fail to patch the VMs. [Learn more](prerequsite-for-schedule-patching.md).
17-
> - To update the patch mode, go to **Update management center (Preview)** home page > **Update Settings**. In **Change update settings**, add the machines and under **Patch orchestration**, select *Azure orchestrated with user managed schedules (Preview)*.
16+
> - For a seamless scheduled patching experience, we recommend that for all Azure VMs, you update the patch mode to *Azure orchestrated with user managed schedules (preview)* before **May 19, 2023**. If you fail to update the patch mode before **May 19, 2023**, you can experience a disruption in business continuity because the schedules will fail to patch the VMs.[Learn more](prerequsite-for-schedule-patching.md).
17+
> - To update the patch mode, go to **Update management center (Preview)** home page > **Update Settings**. In **Change update settings**, add the machines and under **Patch orchestration**, select *Azure-orchestrated-safe deployment*.
1818
1919
You can use update management center (preview) in Azure to create and save recurring deployment schedules. You can create a schedule on a daily, weekly or hourly cadence, specify the machines that must be updated as part of the schedule, and the updates to be installed. This schedule will then automatically install the updates as per the created schedule for single VM and at scale.
2020

articles/update-center/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,8 @@
1616
items:
1717
- name: Update and maintenance options
1818
href: updates-maintenance-schedules.md
19+
- name: Schedule patching configuration on Azure VMs for business continuity
20+
href: prerequsite-for-schedule-patching
1921
- name: Assessment options
2022
href: assessment-options.md
2123
- name: Query resources with Azure Resource Graph

articles/update-center/updates-maintenance-schedules.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Updates and maintenance in update management center (preview).
33
description: The article describes the updates and maintenance options available in Update management center (preview).
44
ms.service: update-management-center
5-
ms.date: 03/15/2023
5+
ms.date: 04/26/2023
66
ms.topic: conceptual
77
author: snehasudhirG
88
ms.author: sudhirsneha
@@ -13,8 +13,8 @@ ms.author: sudhirsneha
1313
**Applies to:** :heavy_check_mark: Windows VMs :heavy_check_mark: Linux VMs :heavy_check_mark: On-premises environment :heavy_check_mark: Azure Arc-enabled servers.
1414

1515
> [!IMPORTANT]
16-
> - For a seamless scheduled patching experience, we recommend that for all Azure VMs, you update the patch mode to *Azure orchestrated with user managed schedules (preview)* before April 30, 2023. If you fail to update the patch mode before April 30, 2023, you can experience a disruption in business continuity because the schedules will fail to patch the VMs. [Learn more](prerequsite-for-schedule-patching.md).
17-
> - To update the patch mode, go to **Update management center (Preview)** home page > **Update Settings**. In **Change update settings**, add the machines and under **Patch orchestration**, select *Azure orchestrated with user managed schedules (Preview)*.
16+
> - For a seamless scheduled patching experience, we recommend that for all Azure VMs, you update the patch mode to *Azure orchestrated with user managed schedules (preview)* before **May 19, 2023**. If you fail to update the patch mode before **May 19, 2023**, you can experience a disruption in business continuity because the schedules will fail to patch the VMs.[Learn more](prerequsite-for-schedule-patching.md).
17+
> - To update the patch mode, go to **Update management center (Preview)** home page > **Update Settings**. In **Change update settings**, add the machines and under **Patch orchestration**, select *Azure-orchestrated-safe deployment*.
1818
1919

2020
This article provides an overview of the various update and maintenance options available by update management center (preview).

articles/update-center/whats-new.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ ms.date: 03/03/2023
1919
A new patch mode - **Azure orchestrated with user managed schedules (Preview)** is introduced as a prerequisite to enable scheduled patching on Azure VMs. The new patch enables the *Azure-orchestrated using Automatic guest patching* and *BypassPlatformSafteyChecksOnUserSchedule* VM properties on your behalf after receiving the consent. [Learn more](prerequsite-for-schedule-patching.md).
2020

2121
> [!IMPORTANT]
22-
> For a seamless scheduled patching experience, we recommend that for all Azure VMs, you update the patch mode to *Azure orchestrated with user managed schedules (preview)* before **April 30, 2023**. If you fail to update the patch mode before **April 30, 2023**, you can experience a disruption in business continuity because the schedules will fail to patch the VMs.
22+
> For a seamless scheduled patching experience, we recommend that for all Azure VMs, you update the patch mode to *Azure orchestrated with user managed schedules (preview)* before **May 19, 2023**. If you fail to update the patch mode before **May 19, 2023**, you can experience a disruption in business continuity because the schedules will fail to patch the VMs.
2323
2424

2525
## November 2022

0 commit comments

Comments
 (0)