Skip to content

Commit ae867eb

Browse files
committed
2205tp-collmaintwindow-3601127
1 parent e5a75a4 commit ae867eb

3 files changed

Lines changed: 13 additions & 12 deletions

File tree

memdocs/configmgr/core/get-started/2022/includes/2205/13351390.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.date: 05/15/2022
88
ms.localizationpriority: medium
99
---
1010

11-
## <a name="bkmk_anchor"></a> Improvements to CMG V2 creation and workflow
11+
## <a name="bkmk_anchor"></a> Improvements to cloud management gateway (CMG) workflow
1212
<!--13351390#-->
1313

14-
Support for CMG Application approval workflow, and PowerShell Cmdlets added in this release.
14+
You can now approve application workflow through email. For the application approvals through email, manually add the CMG URL in the Azure Active Directory app as single page application redirect URI. For more information on how to change the URI, see [Create an app registration in Azure AD for your App Service app](/azure/app-service/configure-authentication-provider-aad).

memdocs/configmgr/core/get-started/2022/includes/2205/3601127.md

Lines changed: 11 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -8,23 +8,24 @@ ms.date: 05/15/2022
88
ms.localizationpriority: medium
99
---
1010

11-
## <a name="bkmk_anchor"></a> Improvements to monthly maintenance window reoccurence schedule with Offset (in days)
11+
## <a name="bkmk_anchor"></a> Offset for monthly maintenance window reoccurrence schedule.
1212
<!--3601127#-->
1313

14-
Based upon your feedback, we can now have an offset to the monthly maintenance window schedule in days to align deployments with monthly security updates. For example, an offset of two days after the second Tuesday of the month sets maintance window on Thursday.
15-
16-
:::image type="content" source="../../media/3601127-collmaintwindow-Collection.png" alt-text="Screenshot of right-click menu displaying options for the Device collection node ." lightbox="../../media/3601127-collmaintwindow-Collection.png":::
14+
Based upon your feedback, we can now have an offset to the monthly maintenance window schedule in days to align deployments with monthly security updates. For example, an offset of two days after the second Tuesday of the month sets maintenance window on Thursday.
1715

1816
:::image type="content" source="../../media/3601127-Collmaintwindow-Schedule.png" alt-text="Screenshot of menu displaying options for the new custom schedule for setting offset days." lightbox="../../media/3601127-Collmaintwindow-Schedule.png":::
1917

20-
:::image type="content" source="../../media/3601127-Collmaintwindow-Client.png" alt-text="Screenshot of menu displaying maintenance window set on client machine." lightbox="../../media/3601127-Collmaintwindow-Client.png":::
2118

2219
### Try it out!
23-
Try to complete the tasks. Then send **Feedback** from the **Home** tab of the ribbon letting us know how it worked. <br/>
20+
Try to complete the tasks. Then send **Feedback** from the **Home** tab of the ribbon letting us know how it worked.
21+
22+
**Create a custom schedule that sets maintenance window offset from a base day**
2423

25-
**Create a custom schedule that sets maintenance window offset from a base day** </br>
2624
1. In the **Device Collection** workspace, create **New Collection**, and select **Properties**.
27-
2. Click on **Maintenance Window** and choose **New Custom Schedule**.
25+
2. Select on **Maintenance Window** and choose **New Custom Schedule**.
2826
3. For the custom schedule, select **Monthly** and put in a base day such as the second Tuesday.
29-
4. Check **Offset (days)** and the number of days for the offset then **OK** when finished.
30-
5. Complete the rest of the **Scenario involves Deploying the Software Updates and other objects aligned with monthly security updates**.
27+
4. Verify the **Offset (days)** and the number of days for the offset then **OK** when finished.
28+
5. Complete the deployment as usual.
29+
30+
> [!NOTE]
31+
> Before using this feature, upgrade the hierarchy to version 2205.
-261 KB
Loading

0 commit comments

Comments
 (0)