deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-12 13:27:23 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

peertopeercaching pentraining performancediagnostics

Browse Source
This commit is contained in:
Liz Long 2023-01-05 11:12:41 -05:00
parent acd6597a34
commit a875c629fd
3 changed files with 864 additions and 691 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

879
windows/client-management/mdm/policy-csp-admx-peertopeercaching.md
View File

File diff suppressed because it is too large Load Diff

210
windows/client-management/mdm/policy-csp-admx-pentraining.md
View File

@ -1,138 +1,158 @@
---
title: Policy CSP - ADMX_PenTraining
description: Learn about Policy CSP - ADMX_PenTraining.
title: ADMX_PenTraining Policy CSP
description: Learn more about the ADMX_PenTraining Area in Policy CSP
author: vinaypamnani-msft
manager: aaroncz
ms.author: vinpa
ms.date: 01/05/2023
ms.localizationpriority: medium
ms.topic: article
ms.prod: windows-client
ms.technology: itpro-manage
author: vinaypamnani-msft
ms.date: 12/22/2020
ms.reviewer:
manager: aaroncz
ms.topic: reference
---
<!-- Auto-Generated CSP Document -->
<!-- ADMX_PenTraining-Begin -->
# Policy CSP - ADMX_PenTraining
> [!TIP]
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](../understanding-admx-backed-policies.md).
> Some of these are ADMX-backed policies and require a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
>
> You must specify the data type in the SyncML as &lt;Format&gt;chr&lt;/Format&gt;. For an example SyncML, refer to [Enabling a policy](../understanding-admx-backed-policies.md#enabling-a-policy).
> You must specify the data type in the SyncML as &lt;Format&gt;chr&lt;/Format&gt;. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
>
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
<hr/>
<!-- ADMX_PenTraining-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- ADMX_PenTraining-Editable-End -->
<!--Policies-->
## ADMX_PenTraining policies
<!-- PenTrainingOff_2-Begin -->
## PenTrainingOff_2
<dl>
<dd>
<a href="#admx-pentraining-pentrainingoff_1">ADMX_PenTraining/PenTrainingOff_1</a>
</dd>
<dd>
<a href="#admx-pentraining-pentrainingoff_2">ADMX_PenTraining/PenTrainingOff_2</a>
</dd>
</dl>
<!-- PenTrainingOff_2-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 2004 [10.0.19041.1202] and later <br> :heavy_check_mark: Windows 10, version 2009 [10.0.19042.1202] and later <br> :heavy_check_mark: Windows 10, version 21H1 [10.0.19043.1202] and later <br> :heavy_check_mark: Windows 11, version 21H2 [10.0.22000] and later |
<!-- PenTrainingOff_2-Applicability-End -->
<hr/>
<!-- PenTrainingOff_2-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/ADMX_PenTraining/PenTrainingOff_2
```
<!-- PenTrainingOff_2-OmaUri-End -->
<!--Policy-->
<a href="" id="admx-pentraining-pentrainingoff_1"></a>**ADMX_PenTraining/PenTrainingOff_1**
<!--SupportedSKUs-->
|Edition|Windows 10|Windows 11|
|--- |--- |--- |
|Home|No|No|
|Pro|Yes|Yes|
|Windows SE|No|Yes|
|Business|Yes|Yes|
|Enterprise|Yes|Yes|
|Education|Yes|Yes|
<!--/SupportedSKUs-->
<hr/>
<!--Scope-->
[Scope](./policy-configuration-service-provider.md#policy-scope):
> [!div class = "checklist"]
> * User
<hr/>
<!--/Scope-->
<!--Description-->
<!-- PenTrainingOff_2-Description-Begin -->
<!-- Description-Source-ADMX -->
Turns off Tablet PC Pen Training.
- If you enable this policy setting, users can't open Tablet PC Pen Training.
If you enable this policy setting, users cannot open Tablet PC Pen Training.
- If you disable or don't configure this policy setting, users can open Tablet PC Pen Training.
If you disable or do not configure this policy setting, users can open Tablet PC Pen Training.
<!-- PenTrainingOff_2-Description-End -->
<!--/Description-->
<!-- PenTrainingOff_2-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- PenTrainingOff_2-Editable-End -->
<!-- PenTrainingOff_2-DFProperties-Begin -->
**Description framework properties**:
<!--ADMXBacked-->
ADMX Info:
- GP Friendly name: *Turn off Tablet PC Pen Training*
- GP name: *PenTrainingOff_1*
- GP path: *Windows Components\Tablet PC\Tablet PC Pen Training*
- GP ADMX file name: *PenTraining.admx*
| Property name | Property value |
|:--|:--|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
<!-- PenTrainingOff_2-DFProperties-End -->
<!--/ADMXBacked-->
<!--/Policy-->
<hr/>
<!-- PenTrainingOff_2-AdmxBacked-Begin -->
> [!TIP]
> This is an ADMX-backed policy and requires SyncML format for configuration. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
<!--Policy-->
<a href="" id="admx-pentraining-pentrainingoff_2"></a>**ADMX_PenTraining/PenTrainingOff_2**
**ADMX mapping**:
<!--SupportedSKUs-->
| Name | Value |
|:--|:--|
| Name | PenTrainingOff |
| Friendly Name | Turn off Tablet PC Pen Training |
| Location | Computer Configuration |
| Path | WindowsComponents > Tablet PC > Tablet PC Pen Training |
| Registry Key Name | SOFTWARE\Policies\Microsoft\PenTraining |
| Registry Value Name | DisablePenTraining |
| ADMX File Name | PenTraining.admx |
<!-- PenTrainingOff_2-AdmxBacked-End -->
|Edition|Windows 10|Windows 11|
|--- |--- |--- |
|Home|No|No|
|Pro|Yes|Yes|
|Windows SE|No|Yes|
|Business|Yes|Yes|
|Enterprise|Yes|Yes|
|Education|Yes|Yes|
<!-- PenTrainingOff_2-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- PenTrainingOff_2-Examples-End -->
<!--/SupportedSKUs-->
<hr/>
<!-- PenTrainingOff_2-End -->
<!--Scope-->
[Scope](./policy-configuration-service-provider.md#policy-scope):
<!-- PenTrainingOff_1-Begin -->
## PenTrainingOff_1
> [!div class = "checklist"]
> * User
<!-- PenTrainingOff_1-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| :x: Device <br> :heavy_check_mark: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 2004 [10.0.19041.1202] and later <br> :heavy_check_mark: Windows 10, version 2009 [10.0.19042.1202] and later <br> :heavy_check_mark: Windows 10, version 21H1 [10.0.19043.1202] and later <br> :heavy_check_mark: Windows 11, version 21H2 [10.0.22000] and later |
<!-- PenTrainingOff_1-Applicability-End -->
<hr/>
<!-- PenTrainingOff_1-OmaUri-Begin -->
```User
./User/Vendor/MSFT/Policy/Config/ADMX_PenTraining/PenTrainingOff_1
```
<!-- PenTrainingOff_1-OmaUri-End -->
<!--/Scope-->
<!--Description-->
<!-- PenTrainingOff_1-Description-Begin -->
<!-- Description-Source-ADMX -->
Turns off Tablet PC Pen Training.
- If you enable this policy setting, users can't open Tablet PC Pen Training.
If you enable this policy setting, users cannot open Tablet PC Pen Training.
- If you disable or don't configure this policy setting, users can open Tablet PC Pen Training.
If you disable or do not configure this policy setting, users can open Tablet PC Pen Training.
<!-- PenTrainingOff_1-Description-End -->
<!--/Description-->
<!-- PenTrainingOff_1-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- PenTrainingOff_1-Editable-End -->
<!-- PenTrainingOff_1-DFProperties-Begin -->
**Description framework properties**:
<!--ADMXBacked-->
ADMX Info:
- GP Friendly name: *Turn off Tablet PC Pen Training*
- GP name: *PenTrainingOff_2*
- GP path: *Windows Components\Tablet PC\Tablet PC Pen Training*
- GP ADMX file name: *PenTraining.admx*
| Property name | Property value |
|:--|:--|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
<!-- PenTrainingOff_1-DFProperties-End -->
<!--/ADMXBacked-->
<!--/Policy-->
<hr/>
<!-- PenTrainingOff_1-AdmxBacked-Begin -->
> [!TIP]
> This is an ADMX-backed policy and requires SyncML format for configuration. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
<!--/Policies-->
**ADMX mapping**:
## Related topics
| Name | Value |
|:--|:--|
| Name | PenTrainingOff |
| Friendly Name | Turn off Tablet PC Pen Training |
| Location | User Configuration |
| Path | WindowsComponents > Tablet PC > Tablet PC Pen Training |
| Registry Key Name | SOFTWARE\Policies\Microsoft\PenTraining |
| Registry Value Name | DisablePenTraining |
| ADMX File Name | PenTraining.admx |
<!-- PenTrainingOff_1-AdmxBacked-End -->
[ADMX-backed policies in Policy CSP](./policies-in-policy-csp-admx-backed.md)
<!-- PenTrainingOff_1-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- PenTrainingOff_1-Examples-End -->
<!-- PenTrainingOff_1-End -->
<!-- ADMX_PenTraining-CspMoreInfo-Begin -->
<!-- Add any additional information about this CSP here. Anything outside this section will get overwritten. -->
<!-- ADMX_PenTraining-CspMoreInfo-End -->
<!-- ADMX_PenTraining-End -->
## Related articles
[Policy configuration service provider](policy-configuration-service-provider.md)

456
windows/client-management/mdm/policy-csp-admx-performancediagnostics.md
View File

@ -1,274 +1,310 @@
---
title: Policy CSP - ADMX_PerformanceDiagnostics
description: Learn about Policy CSP - ADMX_PerformanceDiagnostics.
title: ADMX_PerformanceDiagnostics Policy CSP
description: Learn more about the ADMX_PerformanceDiagnostics Area in Policy CSP
author: vinaypamnani-msft
manager: aaroncz
ms.author: vinpa
ms.date: 01/05/2023
ms.localizationpriority: medium
ms.topic: article
ms.prod: windows-client
ms.technology: itpro-manage
author: vinaypamnani-msft
ms.date: 09/16/2020
ms.reviewer:
manager: aaroncz
ms.topic: reference
---
<!-- Auto-Generated CSP Document -->
<!-- ADMX_PerformanceDiagnostics-Begin -->
# Policy CSP - ADMX_PerformanceDiagnostics
> [!TIP]
> These are ADMX-backed policies and require a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](../understanding-admx-backed-policies.md).
> Some of these are ADMX-backed policies and require a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
>
> You must specify the data type in the SyncML as &lt;Format&gt;chr&lt;/Format&gt;. For an example SyncML, refer to [Enabling a policy](../understanding-admx-backed-policies.md#enabling-a-policy).
> You must specify the data type in the SyncML as &lt;Format&gt;chr&lt;/Format&gt;. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
>
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
<hr/>
<!-- ADMX_PerformanceDiagnostics-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- ADMX_PerformanceDiagnostics-Editable-End -->
<!--Policies-->
## ADMX_PerformanceDiagnostics policies
<!-- WdiScenarioExecutionPolicy_1-Begin -->
## WdiScenarioExecutionPolicy_1
<dl>
<dd>
<a href="#admx-performancediagnostics-wdiscenarioexecutionpolicy-1">ADMX_PerformanceDiagnostics/WdiScenarioExecutionPolicy_1</a>
</dd>
<dd>
<a href="#admx-performancediagnostics-wdiscenarioexecutionpolicy-2">ADMX_PerformanceDiagnostics/WdiScenarioExecutionPolicy_2</a>
</dd>
<dd>
<a href="#admx-performancediagnostics-wdiscenarioexecutionpolicy-3">ADMX_PerformanceDiagnostics/WdiScenarioExecutionPolicy_3</a>
</dd>
<dd>
<a href="#admx-performancediagnostics-wdiscenarioexecutionpolicy-4">ADMX_PerformanceDiagnostics/WdiScenarioExecutionPolicy_4</a>
</dd>
</dl>
<!-- WdiScenarioExecutionPolicy_1-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 2004 [10.0.19041.1202] and later <br> :heavy_check_mark: Windows 10, version 2009 [10.0.19042.1202] and later <br> :heavy_check_mark: Windows 10, version 21H1 [10.0.19043.1202] and later <br> :heavy_check_mark: Windows 11, version 21H2 [10.0.22000] and later |
<!-- WdiScenarioExecutionPolicy_1-Applicability-End -->
<!-- WdiScenarioExecutionPolicy_1-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/ADMX_PerformanceDiagnostics/WdiScenarioExecutionPolicy_1
```
<!-- WdiScenarioExecutionPolicy_1-OmaUri-End -->
<hr/>
<!-- WdiScenarioExecutionPolicy_1-Description-Begin -->
<!-- Description-Source-ADMX -->
Determines the execution level for Windows Boot Performance Diagnostics.
<!--Policy-->
<a href="" id="admx-performancediagnostics-wdiscenarioexecutionpolicy-1"></a>**ADMX_PerformanceDiagnostics/WdiScenarioExecutionPolicy_1**
If you enable this policy setting, you must select an execution level from the dropdown menu. If you select problem detection and troubleshooting only, the Diagnostic Policy Service (DPS) will detect Windows Boot Performance problems and attempt to determine their root causes. These root causes will be logged to the event log when detected, but no corrective action will be taken. If you select detection, troubleshooting and resolution, the DPS will detect Windows Boot Performance problems and indicate to the user that assisted resolution is available.
<!--SupportedSKUs-->
If you disable this policy setting, Windows will not be able to detect, troubleshoot or resolve any Windows Boot Performance problems that are handled by the DPS.
|Edition|Windows 10|Windows 11|
|--- |--- |--- |
|Home|No|No|
|Pro|Yes|Yes|
|Windows SE|No|Yes|
|Business|Yes|Yes|
|Enterprise|Yes|Yes|
|Education|Yes|Yes|
If you do not configure this policy setting, the DPS will enable Windows Boot Performance for resolution by default.
<!--/SupportedSKUs-->
<hr/>
This policy setting takes effect only if the diagnostics-wide scenario execution policy is not configured.
<!--Scope-->
[Scope](./policy-configuration-service-provider.md#policy-scope):
No system restart or service restart is required for this policy to take effect: changes take effect immediately.
> [!div class = "checklist"]
> * Device
This policy setting will only take effect when the Diagnostic Policy Service is in the running state. When the service is stopped or disabled, diagnostic scenarios will not be executed. The DPS can be configured with the Services snap-in to the Microsoft Management Console.
<!-- WdiScenarioExecutionPolicy_1-Description-End -->
<hr/>
<!-- WdiScenarioExecutionPolicy_1-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- WdiScenarioExecutionPolicy_1-Editable-End -->
<!--/Scope-->
<!--Description-->
This policy setting determines the execution level for Windows Boot Performance Diagnostics.
<!-- WdiScenarioExecutionPolicy_1-DFProperties-Begin -->
**Description framework properties**:
If you enable this policy setting, you must select an execution level from the dropdown menu. If you select problem detection and troubleshooting only, the Diagnostic Policy Service (DPS) will detect Windows Boot Performance problems and attempt to determine their root causes. These root causes will be logged to the event log when detected, but no corrective action will be taken. If you select detection, troubleshooting, and resolution, the DPS will detect Windows Boot Performance problems and indicate to the user that assisted resolution is available.
| Property name | Property value |
|:--|:--|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
<!-- WdiScenarioExecutionPolicy_1-DFProperties-End -->
If you disable this policy setting, Windows won't be able to detect, troubleshoot or resolve any Windows Boot Performance problems that are handled by the DPS.
<!-- WdiScenarioExecutionPolicy_1-AdmxBacked-Begin -->
> [!TIP]
> This is an ADMX-backed policy and requires SyncML format for configuration. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
If you don't configure this policy setting, the DPS will enable Windows Boot Performance for resolution by default.
**ADMX mapping**:
This policy setting takes effect only if the diagnostics-wide scenario execution policy isn't configured.
| Name | Value |
|:--|:--|
| Name | WdiScenarioExecutionPolicy |
| Friendly Name | Configure Scenario Execution Level |
| Location | Computer Configuration |
| Path | System > Troubleshooting and Diagnostics > Windows Boot Performance Diagnostics |
| Registry Key Name | SOFTWARE\Policies\Microsoft\Windows\WDI\{67144949-5132-4859-8036-a737b43825d8} |
| Registry Value Name | ScenarioExecutionEnabled |
| ADMX File Name | PerformanceDiagnostics.admx |
<!-- WdiScenarioExecutionPolicy_1-AdmxBacked-End -->
>[!Note]
>No system restart or service restart is required for this policy to take effect; changes take effect immediately.
<!-- WdiScenarioExecutionPolicy_1-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- WdiScenarioExecutionPolicy_1-Examples-End -->
This policy setting will only take effect when the Diagnostic Policy Service is in the running state. When the service is stopped or disabled, diagnostic scenarios won't be executed. The DPS can be configured with the Services snap-in to the Microsoft Management Console.
<!-- WdiScenarioExecutionPolicy_1-End -->
<!--/Description-->
<!-- WdiScenarioExecutionPolicy_2-Begin -->
## WdiScenarioExecutionPolicy_2
<!-- WdiScenarioExecutionPolicy_2-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 2004 [10.0.19041.1202] and later <br> :heavy_check_mark: Windows 10, version 2009 [10.0.19042.1202] and later <br> :heavy_check_mark: Windows 10, version 21H1 [10.0.19043.1202] and later <br> :heavy_check_mark: Windows 11, version 21H2 [10.0.22000] and later |
<!-- WdiScenarioExecutionPolicy_2-Applicability-End -->
<!--ADMXBacked-->
ADMX Info:
- GP Friendly name: *Configure Scenario Execution Level*
- GP name: *WdiScenarioExecutionPolicy_1*
- GP path: *System\Troubleshooting and Diagnostics\Windows Boot Performance Diagnostics*
- GP ADMX file name: *PerformanceDiagnostics.admx*
<!-- WdiScenarioExecutionPolicy_2-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/ADMX_PerformanceDiagnostics/WdiScenarioExecutionPolicy_2
```
<!-- WdiScenarioExecutionPolicy_2-OmaUri-End -->
<!--/ADMXBacked-->
<!--/Policy-->
<hr/>
<!-- WdiScenarioExecutionPolicy_2-Description-Begin -->
<!-- Description-Source-ADMX -->
Determines the execution level for Windows System Responsiveness Diagnostics.
<!--Policy-->
<a href="" id="admx-performancediagnostics-wdiscenarioexecutionpolicy-2"></a>**ADMX_PerformanceDiagnostics/WdiScenarioExecutionPolicy_2**
If you enable this policy setting, you must select an execution level from the dropdown menu. If you select problem detection and troubleshooting only, the Diagnostic Policy Service (DPS) will detect Windows System Responsiveness problems and attempt to determine their root causes. These root causes will be logged to the event log when detected, but no corrective action will be taken. If you select detection, troubleshooting and resolution, the DPS will detect Windows System Responsiveness problems and indicate to the user that assisted resolution is available.
<!--SupportedSKUs-->
If you disable this policy setting, Windows will not be able to detect, troubleshoot or resolve any Windows System Responsiveness problems that are handled by the DPS.
|Edition|Windows 10|Windows 11|
|--- |--- |--- |
|Home|No|No|
|Pro|Yes|Yes|
|Windows SE|No|Yes|
|Business|Yes|Yes|
|Enterprise|Yes|Yes|
|Education|Yes|Yes|
If you do not configure this policy setting, the DPS will enable Windows System Responsiveness for resolution by default.
<!--/SupportedSKUs-->
<hr/>
This policy setting takes effect only if the diagnostics-wide scenario execution policy is not configured.
<!--Scope-->
[Scope](./policy-configuration-service-provider.md#policy-scope):
No system restart or service restart is required for this policy to take effect: changes take effect immediately.
> [!div class = "checklist"]
> * Device
This policy setting will only take effect when the Diagnostic Policy Service is in the running state. When the service is stopped or disabled, diagnostic scenarios will not be executed. The DPS can be configured with the Services snap-in to the Microsoft Management Console.
<!-- WdiScenarioExecutionPolicy_2-Description-End -->
<hr/>
<!-- WdiScenarioExecutionPolicy_2-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- WdiScenarioExecutionPolicy_2-Editable-End -->
<!--/Scope-->
<!--Description-->
<!-- WdiScenarioExecutionPolicy_2-DFProperties-Begin -->
**Description framework properties**:
| Property name | Property value |
|:--|:--|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
<!-- WdiScenarioExecutionPolicy_2-DFProperties-End -->
<!-- WdiScenarioExecutionPolicy_2-AdmxBacked-Begin -->
> [!TIP]
> This is an ADMX-backed policy and requires SyncML format for configuration. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
**ADMX mapping**:
| Name | Value |
|:--|:--|
| Name | WdiScenarioExecutionPolicy |
| Friendly Name | Configure Scenario Execution Level |
| Location | Computer Configuration |
| Path | System > Troubleshooting and Diagnostics > Windows System Responsiveness Performance Diagnostics |
| Registry Key Name | SOFTWARE\Policies\Microsoft\Windows\WDI\{a7a5847a-7511-4e4e-90b1-45ad2a002f51} |
| Registry Value Name | ScenarioExecutionEnabled |
| ADMX File Name | PerformanceDiagnostics.admx |
<!-- WdiScenarioExecutionPolicy_2-AdmxBacked-End -->
<!-- WdiScenarioExecutionPolicy_2-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- WdiScenarioExecutionPolicy_2-Examples-End -->
<!-- WdiScenarioExecutionPolicy_2-End -->
<!-- WdiScenarioExecutionPolicy_3-Begin -->
## WdiScenarioExecutionPolicy_3
<!-- WdiScenarioExecutionPolicy_3-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 2004 [10.0.19041.1202] and later <br> :heavy_check_mark: Windows 10, version 2009 [10.0.19042.1202] and later <br> :heavy_check_mark: Windows 10, version 21H1 [10.0.19043.1202] and later <br> :heavy_check_mark: Windows 11, version 21H2 [10.0.22000] and later |
<!-- WdiScenarioExecutionPolicy_3-Applicability-End -->
<!-- WdiScenarioExecutionPolicy_3-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/ADMX_PerformanceDiagnostics/WdiScenarioExecutionPolicy_3
```
<!-- WdiScenarioExecutionPolicy_3-OmaUri-End -->
<!-- WdiScenarioExecutionPolicy_3-Description-Begin -->
<!-- Description-Source-ADMX -->
Determines the execution level for Windows Shutdown Performance Diagnostics.
If you enable this policy setting, you must select an execution level from the dropdown menu. If you select problem detection and troubleshooting only, the Diagnostic Policy Service (DPS) will detect Windows Shutdown Performance problems and attempt to determine their root causes. These root causes will be logged to the event log when detected, but no corrective action will be taken. If you select detection, troubleshooting and resolution, the DPS will detect Windows Shutdown Performance problems and indicate to the user that assisted resolution is available.
If you disable this policy setting, Windows will not be able to detect, troubleshoot or resolve any Windows Shutdown Performance problems that are handled by the DPS.
If you do not configure this policy setting, the DPS will enable Windows Shutdown Performance for resolution by default.
This policy setting takes effect only if the diagnostics-wide scenario execution policy is not configured.
No system restart or service restart is required for this policy to take effect: changes take effect immediately.
This policy setting will only take effect when the Diagnostic Policy Service is in the running state. When the service is stopped or disabled, diagnostic scenarios will not be executed. The DPS can be configured with the Services snap-in to the Microsoft Management Console.
<!-- WdiScenarioExecutionPolicy_3-Description-End -->
<!-- WdiScenarioExecutionPolicy_3-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- WdiScenarioExecutionPolicy_3-Editable-End -->
<!-- WdiScenarioExecutionPolicy_3-DFProperties-Begin -->
**Description framework properties**:
| Property name | Property value |
|:--|:--|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
<!-- WdiScenarioExecutionPolicy_3-DFProperties-End -->
<!-- WdiScenarioExecutionPolicy_3-AdmxBacked-Begin -->
> [!TIP]
> This is an ADMX-backed policy and requires SyncML format for configuration. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
**ADMX mapping**:
| Name | Value |
|:--|:--|
| Name | WdiScenarioExecutionPolicy |
| Friendly Name | Configure Scenario Execution Level |
| Location | Computer Configuration |
| Path | System > Troubleshooting and Diagnostics > Windows Shutdown Performance Diagnostics |
| Registry Key Name | SOFTWARE\Policies\Microsoft\Windows\WDI\{2698178D-FDAD-40AE-9D3C-1371703ADC5B} |
| Registry Value Name | ScenarioExecutionEnabled |
| ADMX File Name | PerformanceDiagnostics.admx |
<!-- WdiScenarioExecutionPolicy_3-AdmxBacked-End -->
<!-- WdiScenarioExecutionPolicy_3-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- WdiScenarioExecutionPolicy_3-Examples-End -->
<!-- WdiScenarioExecutionPolicy_3-End -->
<!-- WdiScenarioExecutionPolicy_4-Begin -->
## WdiScenarioExecutionPolicy_4
<!-- WdiScenarioExecutionPolicy_4-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 2004 [10.0.19041.1202] and later <br> :heavy_check_mark: Windows 10, version 2009 [10.0.19042.1202] and later <br> :heavy_check_mark: Windows 10, version 21H1 [10.0.19043.1202] and later <br> :heavy_check_mark: Windows 11, version 21H2 [10.0.22000] and later |
<!-- WdiScenarioExecutionPolicy_4-Applicability-End -->
<!-- WdiScenarioExecutionPolicy_4-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/ADMX_PerformanceDiagnostics/WdiScenarioExecutionPolicy_4
```
<!-- WdiScenarioExecutionPolicy_4-OmaUri-End -->
<!-- WdiScenarioExecutionPolicy_4-Description-Begin -->
<!-- Description-Source-ADMX -->
Determines the execution level for Windows Standby/Resume Performance Diagnostics.
If you enable this policy setting, you must select an execution level from the dropdown menu. If you select problem detection and troubleshooting only, the Diagnostic Policy Service (DPS) will detect Windows Standby/Resume Performance problems and attempt to determine their root causes. These root causes will be logged to the event log when detected, but no corrective action will be taken. If you select detection, troubleshooting, and resolution, the DPS will detect Windows Standby/Resume Performance problems and indicate to the user that assisted resolution is available.
If you enable this policy setting, you must select an execution level from the dropdown menu. If you select problem detection and troubleshooting only, the Diagnostic Policy Service (DPS) will detect Windows Standby/Resume Performance problems and attempt to determine their root causes. These root causes will be logged to the event log when detected, but no corrective action will be taken. If you select detection, troubleshooting and resolution, the DPS will detect Windows Standby/Resume Performance problems and indicate to the user that assisted resolution is available.
If you disable this policy setting, Windows won't be able to detect, troubleshoot or resolve any Windows Standby/Resume Performance problems that are handled by the DPS.
If you disable this policy setting, Windows will not be able to detect, troubleshoot or resolve any Windows Standby/Resume Performance problems that are handled by the DPS.
If you don't configure this policy setting, the DPS will enable Windows Standby/Resume Performance for resolution by default.
If you do not configure this policy setting, the DPS will enable Windows Standby/Resume Performance for resolution by default.
This policy setting takes effect only if the diagnostics-wide scenario execution policy isn't configured.
This policy setting takes effect only if the diagnostics-wide scenario execution policy is not configured.
No system restart or service restart is required for this policy to take effect: changes take effect immediately.
This policy setting will only take effect when the Diagnostic Policy Service is in the running state. When the service is stopped or disabled, diagnostic scenarios won't be executed. The DPS can be configured with the Services snap-in to the Microsoft Management Console.
This policy setting will only take effect when the Diagnostic Policy Service is in the running state. When the service is stopped or disabled, diagnostic scenarios will not be executed. The DPS can be configured with the Services snap-in to the Microsoft Management Console.
<!-- WdiScenarioExecutionPolicy_4-Description-End -->
<!--/Description-->
<!-- WdiScenarioExecutionPolicy_4-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- WdiScenarioExecutionPolicy_4-Editable-End -->
<!-- WdiScenarioExecutionPolicy_4-DFProperties-Begin -->
**Description framework properties**:
<!--ADMXBacked-->
ADMX Info:
- GP Friendly name: *Configure Scenario Execution Level*
- GP name: *WdiScenarioExecutionPolicy_2*
- GP path: *System\Troubleshooting and Diagnostics\Windows System Responsiveness Performance Diagnostics*
- GP ADMX file name: *PerformanceDiagnostics.admx*
| Property name | Property value |
|:--|:--|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
<!-- WdiScenarioExecutionPolicy_4-DFProperties-End -->
<!--/ADMXBacked-->
<!--/Policy-->
<hr/>
<!-- WdiScenarioExecutionPolicy_4-AdmxBacked-Begin -->
> [!TIP]
> This is an ADMX-backed policy and requires SyncML format for configuration. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
<!--Policy-->
<a href="" id="admx-performancediagnostics-wdiscenarioexecutionpolicy-3"></a>**ADMX_PerformanceDiagnostics/WdiScenarioExecutionPolicy_3**
**ADMX mapping**:
<!--SupportedSKUs-->
| Name | Value |
|:--|:--|
| Name | WdiScenarioExecutionPolicy |
| Friendly Name | Configure Scenario Execution Level |
| Location | Computer Configuration |
| Path | System > Troubleshooting and Diagnostics > Windows Standby/Resume Performance Diagnostics |
| Registry Key Name | SOFTWARE\Policies\Microsoft\Windows\WDI\{ffc42108-4920-4acf-a4fc-8abdcc68ada4} |
| Registry Value Name | ScenarioExecutionEnabled |
| ADMX File Name | PerformanceDiagnostics.admx |
<!-- WdiScenarioExecutionPolicy_4-AdmxBacked-End -->
|Edition|Windows 10|Windows 11|
|--- |--- |--- |
|Home|No|No|
|Pro|Yes|Yes|
|Windows SE|No|Yes|
|Business|Yes|Yes|
|Enterprise|Yes|Yes|
|Education|Yes|Yes|
<!-- WdiScenarioExecutionPolicy_4-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- WdiScenarioExecutionPolicy_4-Examples-End -->
<!--/SupportedSKUs-->
<hr/>
<!-- WdiScenarioExecutionPolicy_4-End -->
<!--Scope-->
[Scope](./policy-configuration-service-provider.md#policy-scope):
<!-- ADMX_PerformanceDiagnostics-CspMoreInfo-Begin -->
<!-- Add any additional information about this CSP here. Anything outside this section will get overwritten. -->
<!-- ADMX_PerformanceDiagnostics-CspMoreInfo-End -->
> [!div class = "checklist"]
> * Device
<!-- ADMX_PerformanceDiagnostics-End -->
<hr/>
## Related articles
<!--/Scope-->
<!--Description-->
This policy setting determines the execution level for Windows Shutdown Performance Diagnostics.
If you enable this policy setting, you must select an execution level from the dropdown menu. If you select problem detection and troubleshooting only, the Diagnostic Policy Service (DPS) will detect Windows Shutdown Performance problems and attempt to determine their root causes. These root causes will be logged to the event log when detected, but no corrective action will be taken. If you select detection, troubleshooting, and resolution, the DPS will detect Windows Shutdown Performance problems and indicate to the user that assisted resolution is available.
If you disable this policy setting, Windows won't be able to detect, troubleshoot or resolve any Windows Shutdown Performance problems that are handled by the DPS.
If you don't configure this policy setting, the DPS will enable Windows Shutdown Performance for resolution by default.
This policy setting takes effect only if the diagnostics-wide scenario execution policy isn't configured.
No system restart or service restart is required for this policy to take effect: changes take effect immediately.
This policy setting will only take effect when the Diagnostic Policy Service is in the running state. When the service is stopped or disabled, diagnostic scenarios won't be executed. The DPS can be configured with the Services snap-in to the Microsoft Management Console.
<!--/Description-->
<!--ADMXBacked-->
ADMX Info:
- GP Friendly name: *Configure Scenario Execution Level*
- GP name: *WdiScenarioExecutionPolicy_3*
- GP path: *System\Troubleshooting and Diagnostics\Windows Shutdown Performance Diagnostics*
- GP ADMX file name: *PerformanceDiagnostics.admx*
<!--/ADMXBacked-->
<!--/Policy-->
<hr/>
<!--Policy-->
<a href="" id="admx-performancediagnostics-wdiscenarioexecutionpolicy-4"></a>**ADMX_PerformanceDiagnostics/WdiScenarioExecutionPolicy_4**
<!--SupportedSKUs-->
|Edition|Windows 10|Windows 11|
|--- |--- |--- |
|Home|No|No|
|Pro|Yes|Yes|
|Windows SE|No|Yes|
|Business|Yes|Yes|
|Enterprise|Yes|Yes|
|Education|Yes|Yes|
<!--/SupportedSKUs-->
<hr/>
<!--Scope-->
[Scope](./policy-configuration-service-provider.md#policy-scope):
> [!div class = "checklist"]
> * Device
<hr/>
<!--/Scope-->
<!--Description-->
Determines the execution level for Windows Standby/Resume Performance Diagnostics.
If you enable this policy setting, you must select an execution level from the dropdown menu. If you select problem detection and troubleshooting only, the Diagnostic Policy Service (DPS) will detect Windows Standby/Resume Performance problems and attempt to determine their root causes. These root causes will be logged to the event log when detected, but no corrective action will be taken. If you select detection, troubleshooting, and resolution, the DPS will detect Windows Standby/Resume Performance problems and indicate to the user that assisted resolution is available.
If you disable this policy setting, Windows won't be able to detect, troubleshoot or resolve any Windows Standby/Resume Performance problems that are handled by the DPS.
If you don't configure this policy setting, the DPS will enable Windows Standby/Resume Performance for resolution by default.
This policy setting takes effect only if the diagnostics-wide scenario execution policy isn't configured.
No system restart or service restart is required for this policy to take effect: changes take effect immediately.
This policy setting will only take effect when the Diagnostic Policy Service is in the running state. When the service is stopped or disabled, diagnostic scenarios won't be executed. The DPS can be configured with the Services snap-in to the Microsoft Management Console.
<!--/Description-->
<!--ADMXBacked-->
ADMX Info:
- GP Friendly name: *Configure Scenario Execution Level*
- GP name: *WdiScenarioExecutionPolicy_4*
- GP path: *System\Troubleshooting and Diagnostics\Windows Standby/Resume Performance Diagnostics*
- GP ADMX file name: *PerformanceDiagnostics.admx*
<!--/ADMXBacked-->
<!--/Policy-->
<hr/>
<!--/Policies-->
## Related topics
[ADMX-backed policies in Policy CSP](./policies-in-policy-csp-admx-backed.md)
[Policy configuration service provider](policy-configuration-service-provider.md)