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: memdocs/configmgr/compliance/deploy-use/create-custom-configuration-items-for-windows-desktop-and-server-computers-managed-with-the-client.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Create custom configuration items
3
3
titleSuffix: Configuration Manager
4
4
description: Manage settings for Windows computers and servers with a custom configuration item for Windows desktops and servers
5
-
ms.date: 03/10/2022
5
+
ms.date: 08/12/2022
6
6
ms.prod: configuration-manager
7
7
ms.technology: configmgr-compliance
8
8
ms.topic: conceptual
@@ -227,8 +227,8 @@ The value returned by the script is used to assess the compliance of the global
227
227
-**Run scripts by using the logged on user credentials**: If you enable this option, the script runs on client computers that use the credentials of the signed-in user.
228
228
229
229
> [!IMPORTANT]
230
-
> When using a signed PowerShell script, ensure you select **Open**. You can't use copy and paste for a signed script. <!--8538617-->
231
-
230
+
> -When using a signed PowerShell script, ensure you select **Open**. You can't use copy and paste for a signed script. <!--8538617-->
231
+
> - Starting in 2207, you can define a **Script Execution Timeout (seconds)** when configuring [client settings](../../core/clients/deploy/about-client-settings.md#compliance-settings) for compliance settings. <!--14120481-->
Copy file name to clipboardExpand all lines: memdocs/configmgr/core/clients/deploy/about-client-settings.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -171,8 +171,9 @@ Select **Schedule** to create the default schedule for configuration baseline de
171
171
172
172
Choose **Yes** if you want to deploy [user data and profiles](../../../compliance/deploy-use/create-user-data-and-profiles-configuration-items.md) configuration items.
173
173
174
+
## Script Execution Timeout (seconds)
174
175
175
-
176
+
Starting in version 2207, you can define a **Script Execution Timeout (seconds)**. The timeout value can be set from a minimum of 60 seconds to a maximum of 600 seconds. This new setting allows you more flexibility for configuration items when you need to run scripts that may exceed the default of 60 seconds. <!--14120481-->
Copy file name to clipboardExpand all lines: memdocs/configmgr/core/clients/manage/collections/use-maintenance-windows.md
+7-4Lines changed: 7 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,13 +2,13 @@
2
2
title: Use maintenance windows
3
3
titleSuffix: Configuration Manager
4
4
description: Use collections and maintenance windows to effectively manage clients in Configuration Manager.
5
-
ms.date: 04/05/2021
5
+
ms.date: 08/01/2021
6
6
ms.prod: configuration-manager
7
7
ms.technology: configmgr-client
8
8
ms.topic: how-to
9
-
author: aczechowski
10
-
ms.author: aaroncz
11
-
manager: dougeby
9
+
author: baladelli
10
+
ms.author: baladell
11
+
manager: apoorvseth
12
12
ms.localizationpriority: medium
13
13
---
14
14
@@ -80,6 +80,8 @@ By default, with multiple maintenance windows, the client only installs software
80
80
-**Coordinated Universal Time (UTC)**: Enable this option for the client to interpret the start and end times in the UTC time zone. For regionally or globally distributed devices in the same collection, this option sets the maintenance window to occur simultaneously on all devices in the collection. Disable this option for the client to use the device's local time zone. This option is disabled by default.
81
81
82
82
1. Configure the recurrence pattern. The default is once per week on the current day of the week.
83
+
> [!NOTE]
84
+
> Starting in version 2207, you can offset monthly maintenance window schedules to better align deployments with the release of monthly security updates. For example, using an offset of two days after the second Tuesday of the month, sets the maintenance window for Thursday. <!--3601127-->
83
85
84
86
1.**Apply this schedule to**: By default the window applies to **All deployments**. You can select either **Software updates** or **Task sequences** to further control what deployments run during this window.
85
87
@@ -88,6 +90,7 @@ By default, with multiple maintenance windows, the client only installs software
88
90
89
91
1. Select **OK** to save and close the window.
90
92
93
+
91
94
The **Maintenance Windows** tab of the collection properties displays all configured windows.
Copy file name to clipboardExpand all lines: memdocs/configmgr/core/plan-design/changes/whats-new-in-version-1906.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -516,12 +516,12 @@ For more information on the dashboard, prerequisites, and using this data, see [
516
516
## <aname="bkmk_protect"></a> Protection
517
517
518
518
### Windows Defender Application Guard file trust criteria
519
-
519
+
_Applies to version 2203 or earlier_
520
520
<!--3555858-->
521
521
522
522
There's a new policy setting that enables users to trust files that normally open in Windows Defender Application Guard (WDAG). Upon successful completion, the files will open on the host device instead of in WDAG.
523
523
524
-
For more information, see [Create and deploy Windows Defender Application Guard policy](../../../protect/deploy-use/create-deploy-application-guard-policy.md#bkmk_FM).
524
+
For more information, see [Create and deploy Windows Defender Application Guard policy](../../../protect/deploy-use/create-deploy-application-guard-policy.md#bkmk_ABS).
0 commit comments