Merge pull request #8151 from mestew/2207-timeout-14120481

CM2207CB- timeout -14120481

Author: PRMerger8

memdocs/configmgr/compliance/deploy-use/create-custom-configuration-items-for-windows-desktop-and-server-computers-managed-with-the-client.md

@@ -2,7 +2,7 @@
 title: Create custom configuration items
 titleSuffix: Configuration Manager
 description: Manage settings for Windows computers and servers with a custom configuration item for Windows desktops and servers
-ms.date: 03/10/2022
+ms.date: 08/01/2022
 ms.prod: configuration-manager
 ms.technology: configmgr-compliance
 ms.topic: conceptual
@@ -227,8 +227,8 @@ The value returned by the script is used to assess the compliance of the global
 - **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.  
 
 > [!IMPORTANT]
-> When using a signed PowerShell script, ensure you select **Open**.  You can't use copy and paste for a signed script. <!--8538617-->
-
+> - When using a signed PowerShell script, ensure you select **Open**.  You can't use copy and paste for a signed script. <!--8538617-->
+> - 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-->
 
 ### <a name="bkmk_sql"></a> SQL query
 

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

@@ -171,8 +171,9 @@ Select **Schedule** to create the default schedule for configuration baseline de
 
 Choose **Yes** if you want to deploy [user data and profiles](../../../compliance/deploy-use/create-user-data-and-profiles-configuration-items.md) configuration items.
 
+## Script Execution Timeout (seconds)
 
-
+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-->
 ## Computer agent  
 
 ### User notifications for required deployments

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

@@ -59,7 +59,7 @@ You can now add options via PowerShell to include and prefer cloud management ga
 <!--14120481-->
 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.
 
-<!--For more information, see [xxxxxc](../../servers/blah.md). -->
+For more information, see the [compliance settings group of client settings](../../clients/deploy/about-client-settings.md#compliance-settings).
 
 ## Collections