deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-15 18:33:43 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

add admx_wdi csp

Browse Source
This commit is contained in:
Aaron Czechowski
2022-12-22 11:31:28 -08:00
parent 29d933aecf
commit 42b2d58b6e
1 changed files with 124 additions and 103 deletions
Download Patch File Download Diff File Expand all files Collapse all files

227
windows/client-management/mdm/policy-csp-admx-wdi.md
View File

@ -1,147 +1,168 @@
---
title: Policy CSP - ADMX_WDI
description: Learn about Policy CSP - ADMX_WDI.
title: ADMX_WDI Policy CSP
description: Learn more about the ADMX_WDI Area in Policy CSP
author: vinaypamnani-msft
manager: aaroncz
ms.author: vinpa
ms.date: 12/22/2022
ms.localizationpriority: medium
ms.topic: article
ms.prod: windows-client
ms.technology: itpro-manage
author: vinaypamnani-msft
ms.date: 11/09/2020
ms.reviewer:
manager: aaroncz
ms.topic: reference
---
<!-- Auto-Generated CSP Document -->
<!-- ADMX_WDI-Begin -->
# Policy CSP - ADMX_WDI
<hr/>
<!--Policies-->
## ADMX_WDI policies
> [!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).
> 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).
<dl>
<dd>
<a href="#admx-wdi-wdidpsscenarioexecutionpolicy">ADMX_WDI/WdiDpsScenarioExecutionPolicy</a>
</dd>
<dd>
<a href="#admx-wdi-wdidpsscenariodatasizelimitpolicy">ADMX_WDI/WdiDpsScenarioDataSizeLimitPolicy</a>
</dd>
</dl>
<!-- ADMX_WDI-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- ADMX_WDI-Editable-End -->
<!-- WdiDpsScenarioDataSizeLimitPolicy-Begin -->
## WdiDpsScenarioDataSizeLimitPolicy
<hr/>
<!-- WdiDpsScenarioDataSizeLimitPolicy-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 |
<!-- WdiDpsScenarioDataSizeLimitPolicy-Applicability-End -->
<!--Policy-->
<a href="" id="admx-wdi-wdidpsscenarioexecutionpolicy"></a>**ADMX_WDI/WdiDpsScenarioExecutionPolicy**
<!-- WdiDpsScenarioDataSizeLimitPolicy-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/ADMX_WDI/WdiDpsScenarioDataSizeLimitPolicy
```
<!-- WdiDpsScenarioDataSizeLimitPolicy-OmaUri-End -->
<!--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-->
<!-- WdiDpsScenarioDataSizeLimitPolicy-Description-Begin -->
<!-- Description-Source-ADMX -->
This policy setting determines the data retention limit for Diagnostic Policy Service (DPS) scenario data.
If you enable this policy setting, you must enter the maximum size of scenario data that should be retained in megabytes. Detailed troubleshooting data related to scenarios will be retained until this limit is reached.
If you disable or don't configure this policy setting, the DPS deletes scenario data once it exceeds 128 megabytes in size. No reboots or service restarts are required for this policy setting to take effect: changes take effect immediately.
If you disable or do not configure this policy setting, the DPS deletes scenario data once it exceeds 128 megabytes in size.
>[!NOTE]
> 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 scenario data won't be deleted.
>
> The DPS can be configured with the Services snap-in to the Microsoft Management Console.
No reboots or service restarts are required for this policy setting to take effect: changes take effect immediately.
<!--/Description-->
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 scenario data will not be deleted. The DPS can be configured with the Services snap-in to the Microsoft Management Console.
<!-- WdiDpsScenarioDataSizeLimitPolicy-Description-End -->
<!--ADMXBacked-->
ADMX Info:
- GP Friendly name: *Diagnostics: Configure scenario retention*
- GP name: *WdiDpsScenarioExecutionPolicy*
- GP path: *System\Troubleshooting and Diagnostics*
- GP ADMX file name: *WDI.admx*
<!-- WdiDpsScenarioDataSizeLimitPolicy-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- WdiDpsScenarioDataSizeLimitPolicy-Editable-End -->
<!--/ADMXBacked-->
<!--/Policy-->
<hr/>
<!-- WdiDpsScenarioDataSizeLimitPolicy-DFProperties-Begin -->
**Description framework properties**:
<!--Policy-->
<a href="" id="admx-wdi-wdidpsscenariodatasizelimitpolicy"></a>**ADMX_WDI/WdiDpsScenarioDataSizeLimitPolicy**
| Property name | Property value |
|:--|:--|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
<!-- WdiDpsScenarioDataSizeLimitPolicy-DFProperties-End -->
<!--SupportedSKUs-->
<!-- WdiDpsScenarioDataSizeLimitPolicy-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).
|Edition|Windows 10|Windows 11|
|--- |--- |--- |
|Home|No|No|
|Pro|Yes|Yes|
|Windows SE|No|Yes|
|Business|Yes|Yes|
|Enterprise|Yes|Yes|
|Education|Yes|Yes|
**ADMX mapping**:
<!--/SupportedSKUs-->
<hr/>
| Name | Value |
|:--|:--|
| Name | WdiDpsScenarioDataSizeLimitPolicy |
| Friendly Name | Diagnostics: Configure scenario retention |
| Location | Computer Configuration |
| Path | System > Troubleshooting and Diagnostics |
| Registry Key Name | SOFTWARE\Policies\Microsoft\Windows\WDI |
| Registry Value Name | DataRetentionBySizeEnabled |
| ADMX File Name | WDI.admx |
<!-- WdiDpsScenarioDataSizeLimitPolicy-AdmxBacked-End -->
<!--Scope-->
[Scope](./policy-configuration-service-provider.md#policy-scope):
<!-- WdiDpsScenarioDataSizeLimitPolicy-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- WdiDpsScenarioDataSizeLimitPolicy-Examples-End -->
> [!div class = "checklist"]
> * Device
<!-- WdiDpsScenarioDataSizeLimitPolicy-End -->
<hr/>
<!-- WdiDpsScenarioExecutionPolicy-Begin -->
## WdiDpsScenarioExecutionPolicy
<!--/Scope-->
<!--Description-->
<!-- WdiDpsScenarioExecutionPolicy-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 |
<!-- WdiDpsScenarioExecutionPolicy-Applicability-End -->
<!-- WdiDpsScenarioExecutionPolicy-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/ADMX_WDI/WdiDpsScenarioExecutionPolicy
```
<!-- WdiDpsScenarioExecutionPolicy-OmaUri-End -->
<!-- WdiDpsScenarioExecutionPolicy-Description-Begin -->
<!-- Description-Source-ADMX -->
This policy setting determines the execution level for Diagnostic Policy Service (DPS) scenarios.
If you enable this policy setting, you must select an execution level from the drop-down menu.
If you enable this policy setting, you must select an execution level from the drop-down menu. If you select problem detection and troubleshooting only, the DPS will detect 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 attempt to automatically fix problems it detects or indicate to the user that assisted resolution is available.
- If you select problem detection and troubleshooting only, the DPS will detect 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 attempt to automatically fix problems it detects or indicate to the user that assisted resolution is available.
If you disable this policy setting, Windows cannot detect, troubleshoot, or resolve any problems that are handled by the DPS.
If you disable this policy setting, Windows can't detect, troubleshoot, or resolve any problems that are handled by the DPS.
If you do not configure this policy setting, the DPS enables all scenarios for resolution by default, unless you configure separate scenario-specific policy settings.
If you don't configure this policy setting, the DPS enables all scenarios for resolution by default, unless you configure separate scenario-specific policy settings. This policy setting takes precedence over any scenario-specific policy settings when it's enabled or disabled. Scenario-specific policy settings only take effect if this policy setting isn't configured. No reboots or service restarts are required for this policy setting to take effect: changes take effect immediately.
This policy setting takes precedence over any scenario-specific policy settings when it is enabled or disabled. Scenario-specific policy settings only take effect if this policy setting is not configured.
<!--/Description-->
No reboots or service restarts are required for this policy setting to take effect: changes take effect immediately.
<!-- WdiDpsScenarioExecutionPolicy-Description-End -->
<!--ADMXBacked-->
ADMX Info:
- GP Friendly name: *Diagnostics: Configure scenario execution level*
- GP name: *WdiDpsScenarioDataSizeLimitPolicy*
- GP path: *System\Troubleshooting and Diagnostics*
- GP ADMX file name: *WDI.admx*
<!-- WdiDpsScenarioExecutionPolicy-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- WdiDpsScenarioExecutionPolicy-Editable-End -->
<!--/ADMXBacked-->
<!--/Policy-->
<hr/>
<!-- WdiDpsScenarioExecutionPolicy-DFProperties-Begin -->
**Description framework properties**:
<!--/Policies-->
| Property name | Property value |
|:--|:--|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
<!-- WdiDpsScenarioExecutionPolicy-DFProperties-End -->
## Related topics
<!-- WdiDpsScenarioExecutionPolicy-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-backed policies in Policy CSP](./policies-in-policy-csp-admx-backed.md)
**ADMX mapping**:
| Name | Value |
|:--|:--|
| Name | WdiDpsScenarioExecutionPolicy |
| Friendly Name | Diagnostics: Configure scenario execution level |
| Location | Computer Configuration |
| Path | System > Troubleshooting and Diagnostics |
| Registry Key Name | SOFTWARE\Policies\Microsoft\Windows\WDI |
| Registry Value Name | ScenarioExecutionEnabled |
| ADMX File Name | WDI.admx |
<!-- WdiDpsScenarioExecutionPolicy-AdmxBacked-End -->
<!-- WdiDpsScenarioExecutionPolicy-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- WdiDpsScenarioExecutionPolicy-Examples-End -->
<!-- WdiDpsScenarioExecutionPolicy-End -->
<!-- ADMX_WDI-CspMoreInfo-Begin -->
<!-- Add any additional information about this CSP here. Anything outside this section will get overwritten. -->
<!-- ADMX_WDI-CspMoreInfo-End -->
<!-- ADMX_WDI-End -->
## Related articles
[Policy configuration service provider](policy-configuration-service-provider.md)