Skip to content

Commit c421a7f

Browse files
committed
2207-timeout-14120481
1 parent 4cfef7d commit c421a7f

2 files changed

Lines changed: 3 additions & 2 deletions

File tree

memdocs/configmgr/core/clients/deploy/about-client-settings.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -171,8 +171,9 @@ Select **Schedule** to create the default schedule for configuration baseline de
171171

172172
Choose **Yes** if you want to deploy [user data and profiles](../../../compliance/deploy-use/create-user-data-and-profiles-configuration-items.md) configuration items.
173173

174+
## Script Execution Timeout (seconds)
174175

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.
176177
## Computer agent
177178

178179
### User notifications for required deployments

memdocs/configmgr/core/plan-design/changes/whats-new-in-version-2207.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,7 @@ You can now add options via PowerShell to include and prefer cloud management ga
5959
<!--14120481-->
6060
You can now define a **Script Execution Timeout (seconds)** when configuring client 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 run scripts that may exceed the default of 60 seconds.
6161

62-
<!--For more information, see [xxxxxc](../../servers/blah.md). -->
62+
For more information, see the [compliance settings group of client settings](../../clients/deploy/about-client-settings.md#compliance-settings).
6363

6464
## Collections
6565

0 commit comments

Comments
 (0)