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/core/get-started/2022/includes/2205/14120481.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
@@ -8,6 +8,6 @@ ms.date: 05/20/2022
8
8
ms.localizationpriority: medium
9
9
---
10
10
11
-
## <aname="bkmk_anchor"></a> Feature Name
12
-
<!--CMADO#-->
13
-
11
+
## <aname="bkmk_timeout"></a> Script execution timeout for compliance settings
12
+
<!--14120481-->
13
+
You can now define a **Script Execution Timeout (seconds)** when configuring [client settings](../../../../clients/deploy/about-client-settings.md#compliance-settings) for compliance settings. 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 to run scripts that may exceed the default of 60 seconds.
0 commit comments