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

msapolicy msched msdt

Browse Source
This commit is contained in:
Liz Long 2023-01-06 09:06:45 -05:00
parent 7ff74ddc6c
commit 0ac89d747b
3 changed files with 378 additions and 326 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

133
windows/client-management/mdm/policy-csp-admx-msapolicy.md
View File

@ -1,90 +1,97 @@
--- ---
title: Policy CSP - ADMX_MSAPolicy title: ADMX_MSAPolicy Policy CSP
description: Learn about Policy CSP - ADMX_MSAPolicy. description: Learn more about the ADMX_MSAPolicy Area in Policy CSP
author: vinaypamnani-msft
manager: aaroncz
ms.author: vinpa ms.author: vinpa
ms.date: 01/06/2023
ms.localizationpriority: medium ms.localizationpriority: medium
ms.topic: article
ms.prod: windows-client ms.prod: windows-client
ms.technology: itpro-manage ms.technology: itpro-manage
author: vinaypamnani-msft ms.topic: reference
ms.date: 09/14/2020
ms.reviewer:
manager: aaroncz
--- ---
<!-- Auto-Generated CSP Document -->
<!-- ADMX_MSAPolicy-Begin -->
# Policy CSP - ADMX_MSAPolicy # Policy CSP - ADMX_MSAPolicy
>[!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). > [!TIP]
> 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).
<hr/> <!-- ADMX_MSAPolicy-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- ADMX_MSAPolicy-Editable-End -->
<!--Policies--> <!-- MicrosoftAccount_DisableUserAuth-Begin -->
## ADMX_MSAPolicy policies ## MicrosoftAccount_DisableUserAuth
<dl> <!-- MicrosoftAccount_DisableUserAuth-Applicability-Begin -->
<dd> | Scope | Editions | Applicable OS |
<a href="#admx-msapolicy-microsoftaccount-disableuserauth">ADMX_MSAPolicy/IncludeMicrosoftAccount_DisableUserAuthCmdLine</a> |:--|:--|:--|
</dd> | :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 |
</dl> <!-- MicrosoftAccount_DisableUserAuth-Applicability-End -->
<!-- MicrosoftAccount_DisableUserAuth-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/ADMX_MSAPolicy/MicrosoftAccount_DisableUserAuth
```
<!-- MicrosoftAccount_DisableUserAuth-OmaUri-End -->
<hr/> <!-- MicrosoftAccount_DisableUserAuth-Description-Begin -->
<!-- Description-Source-ADMX -->
This setting controls whether users can provide Microsoft accounts for authentication for applications or services. If this setting is enabled, all applications and services on the device are prevented from using Microsoft accounts for authentication.
This applies both to existing users of a device and new users who may be added. However, any application or service that has already authenticated a user will not be affected by enabling this setting until the authentication cache expires.
It is recommended to enable this setting before any user signs in to a device to prevent cached tokens from being present. If this setting is disabled or not configured, applications and services can use Microsoft accounts for authentication.
By default, this setting is Disabled. This setting does not affect whether users can sign in to devices by using Microsoft accounts, or the ability for users to provide Microsoft accounts via the browser for authentication with web-based applications.
<!-- MicrosoftAccount_DisableUserAuth-Description-End -->
<!--Policy--> <!-- MicrosoftAccount_DisableUserAuth-Editable-Begin -->
<a href="" id="admx-msapolicy-microsoftaccount-disableuserauth"></a>**ADMX_MSAPolicy/MicrosoftAccount_DisableUserAuth** <!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- MicrosoftAccount_DisableUserAuth-Editable-End -->
<!--SupportedSKUs--> <!-- MicrosoftAccount_DisableUserAuth-DFProperties-Begin -->
**Description framework properties**:
|Edition|Windows 10|Windows 11| | Property name | Property value |
|--- |--- |--- | |:--|:--|
|Home|No|No| | Format | chr (string) |
|Pro|Yes|Yes| | Access Type | Add, Delete, Get, Replace |
|Windows SE|No|Yes| <!-- MicrosoftAccount_DisableUserAuth-DFProperties-End -->
|Business|Yes|Yes|
|Enterprise|Yes|Yes|
|Education|Yes|Yes|
<!--/SupportedSKUs--> <!-- MicrosoftAccount_DisableUserAuth-AdmxBacked-Begin -->
<hr/> > [!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).
<!--Scope--> **ADMX mapping**:
[Scope](./policy-configuration-service-provider.md#policy-scope):
> [!div class = "checklist"] | Name | Value |
> * Device |:--|:--|
| Name | MicrosoftAccount_DisableUserAuth |
| Friendly Name | Block all consumer Microsoft account user authentication |
| Location | Computer Configuration |
| Path | Windows Components > Microsoft account |
| Registry Key Name | Software\Policies\Microsoft\MicrosoftAccount |
| Registry Value Name | DisableUserAuth |
| ADMX File Name | MSAPolicy.admx |
<!-- MicrosoftAccount_DisableUserAuth-AdmxBacked-End -->
<hr/> <!-- MicrosoftAccount_DisableUserAuth-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- MicrosoftAccount_DisableUserAuth-Examples-End -->
<!--/Scope--> <!-- MicrosoftAccount_DisableUserAuth-End -->
<!--Description-->
This policy setting controls whether users can provide Microsoft accounts for authentication, applications or services. If this setting is enabled, all applications and services on the device are prevented from using Microsoft accounts for authentication.
This functionality applies both to existing users of a device and new users who may be added. However, any application or service that has already authenticated a user won't be affected by enabling this setting until the authentication cache expires. <!-- ADMX_MSAPolicy-CspMoreInfo-Begin -->
<!-- Add any additional information about this CSP here. Anything outside this section will get overwritten. -->
<!-- ADMX_MSAPolicy-CspMoreInfo-End -->
It's recommended to enable this setting before any user signs in to a device to prevent cached tokens from being present. If this setting is disabled or not configured, applications and services can use Microsoft accounts for authentication. <!-- ADMX_MSAPolicy-End -->
By default, this setting is Disabled. This setting doesn't affect whether users can sign in to devices by using Microsoft accounts, or the ability for users to provide Microsoft accounts via the browser for authentication with web-based applications. ## Related articles
<!--/Description--> [Policy configuration service provider](policy-configuration-service-provider.md)
<!--ADMXBacked-->
ADMX Info:
- GP Friendly name: *Block all consumer Microsoft account user authentication*
- GP name: *MicrosoftAccount_DisableUserAuth*
- GP path: *Windows Components\Microsoft account*
- GP ADMX file name: *MSAPolicy.admx*
<!--/ADMXBacked-->
<!--/Policy-->
<hr/>
<!--/Policies-->
## Related topics
[ADMX-backed policies in Policy CSP](./policies-in-policy-csp-admx-backed.md)

216
windows/client-management/mdm/policy-csp-admx-msched.md
View File

@ -1,143 +1,163 @@
--- ---
title: Policy CSP - ADMX_msched title: ADMX_msched Policy CSP
description: Learn about Policy CSP - ADMX_msched. description: Learn more about the ADMX_msched Area in Policy CSP
author: vinaypamnani-msft
manager: aaroncz
ms.author: vinpa ms.author: vinpa
ms.date: 01/06/2023
ms.localizationpriority: medium ms.localizationpriority: medium
ms.topic: article
ms.prod: windows-client ms.prod: windows-client
ms.technology: itpro-manage ms.technology: itpro-manage
author: vinaypamnani-msft ms.topic: reference
ms.date: 12/08/2020
ms.reviewer:
manager: aaroncz
--- ---
<!-- Auto-Generated CSP Document -->
<!-- ADMX_msched-Begin -->
# Policy CSP - ADMX_msched # Policy CSP - ADMX_msched
>[!TIP] > [!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). > 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_msched-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- ADMX_msched-Editable-End -->
<!--Policies--> <!-- ActivationBoundaryPolicy-Begin -->
## ADMX_msched policies ## ActivationBoundaryPolicy
<dl> <!-- ActivationBoundaryPolicy-Applicability-Begin -->
<dd> | Scope | Editions | Applicable OS |
<a href="#admx-msched-activationboundarypolicy">ADMX_msched/ActivationBoundaryPolicy</a> |:--|:--|:--|
</dd> | :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 |
<dd> <!-- ActivationBoundaryPolicy-Applicability-End -->
<a href="#admx-msched-randomdelaypolicy">ADMX_msched/RandomDelayPolicy</a>
</dd>
</dl>
<!-- ActivationBoundaryPolicy-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/ADMX_msched/ActivationBoundaryPolicy
```
<!-- ActivationBoundaryPolicy-OmaUri-End -->
<hr/> <!-- ActivationBoundaryPolicy-Description-Begin -->
<!-- Description-Source-ADMX -->
This policy setting allows you to configure Automatic Maintenance activation boundary.
<!--Policy--> The maintenance activation boundary is the daily schduled time at which Automatic Maintenance starts
<a href="" id="admx-msched-activationboundarypolicy"></a>**ADMX_msched/ActivationBoundaryPolicy**
<!--SupportedSKUs--> If you enable this policy setting, this will override the default daily scheduled time as specified in Security and Maintenance/Automatic Maintenance Control Panel.
|Edition|Windows 10|Windows 11| If you disable or do not configure this policy setting, the daily scheduled time as specified in Security and Maintenance/Automatic Maintenance Control Panel will apply.
|--- |--- |--- | <!-- ActivationBoundaryPolicy-Description-End -->
|Home|No|No|
|Pro|Yes|Yes|
|Windows SE|No|Yes|
|Business|Yes|Yes|
|Enterprise|Yes|Yes|
|Education|Yes|Yes|
<!--/SupportedSKUs--> <!-- ActivationBoundaryPolicy-Editable-Begin -->
<hr/> <!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- ActivationBoundaryPolicy-Editable-End -->
<!--Scope--> <!-- ActivationBoundaryPolicy-DFProperties-Begin -->
[Scope](./policy-configuration-service-provider.md#policy-scope): **Description framework properties**:
> [!div class = "checklist"] | Property name | Property value |
> * Device |:--|:--|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
<!-- ActivationBoundaryPolicy-DFProperties-End -->
<hr/> <!-- ActivationBoundaryPolicy-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).
<!--/Scope--> **ADMX mapping**:
<!--Description-->
This policy setting allows you to configure Automatic Maintenance activation boundary. The maintenance activation boundary is the daily scheduled time at which Automatic Maintenance starts.
If you enable this policy setting, this scheduled time will override the default daily scheduled time as specified in Security and Maintenance/Automatic Maintenance Control Panel. | Name | Value |
|:--|:--|
| Name | ActivationBoundary |
| Friendly Name | Automatic Maintenance Activation Boundary |
| Location | Computer Configuration |
| Path | Windows Components > Maintenance Scheduler |
| Registry Key Name | Software\Policies\Microsoft\Windows\Task Scheduler\Maintenance |
| ADMX File Name | msched.admx |
<!-- ActivationBoundaryPolicy-AdmxBacked-End -->
If you disable or don't configure this policy setting, the daily scheduled time as specified in Security and Maintenance/Automatic Maintenance Control Panel will apply. <!-- ActivationBoundaryPolicy-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- ActivationBoundaryPolicy-Examples-End -->
<!--/Description--> <!-- ActivationBoundaryPolicy-End -->
<!-- RandomDelayPolicy-Begin -->
## RandomDelayPolicy
<!--ADMXBacked--> <!-- RandomDelayPolicy-Applicability-Begin -->
ADMX Info: | Scope | Editions | Applicable OS |
- GP Friendly name: *Automatic Maintenance Activation Boundary* |:--|:--|:--|
- GP name: *ActivationBoundaryPolicy* | :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 |
- GP path: *Windows Components\Maintenance Scheduler* <!-- RandomDelayPolicy-Applicability-End -->
- GP ADMX file name: *msched.admx*
<!--/ADMXBacked--> <!-- RandomDelayPolicy-OmaUri-Begin -->
<!--/Policy--> ```Device
<hr/> ./Device/Vendor/MSFT/Policy/Config/ADMX_msched/RandomDelayPolicy
```
<!-- RandomDelayPolicy-OmaUri-End -->
<!--Policy--> <!-- RandomDelayPolicy-Description-Begin -->
<a href="" id="admx-msched-randomdelaypolicy"></a>**ADMX_msched/RandomDelayPolicy** <!-- Description-Source-ADMX -->
<!--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-->
This policy setting allows you to configure Automatic Maintenance activation random delay. This policy setting allows you to configure Automatic Maintenance activation random delay.
The maintenance random delay is the amount of time up to which Automatic Maintenance will delay starting from its Activation Boundary. The maintenance random delay is the amount of time up to which Automatic Maintenance will delay starting from its Activation Boundary.
If you enable this policy setting, Automatic Maintenance will delay starting from its Activation Boundary, by up to this time. If you enable this policy setting, Automatic Maintenance will delay starting from its Activation Boundary, by upto this time.
If you don't configure this policy setting, 4 hour random delay will be applied to Automatic Maintenance. If you do not configure this policy setting, 4 hour random delay will be applied to Automatic Maintenance.
If you disable this policy setting, no random delay will be applied to Automatic Maintenance. If you disable this policy setting, no random delay will be applied to Automatic Maintenance.
<!-- RandomDelayPolicy-Description-End -->
<!--/Description--> <!-- RandomDelayPolicy-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- RandomDelayPolicy-Editable-End -->
<!-- RandomDelayPolicy-DFProperties-Begin -->
**Description framework properties**:
<!--ADMXBacked--> | Property name | Property value |
ADMX Info: |:--|:--|
- GP Friendly name: *Automatic Maintenance Random Delay* | Format | chr (string) |
- GP name: *RandomDelayPolicy* | Access Type | Add, Delete, Get, Replace |
- GP path: *Windows Components\Maintenance Scheduler* <!-- RandomDelayPolicy-DFProperties-End -->
- GP ADMX file name: *msched.admx*
<!--/ADMXBacked--> <!-- RandomDelayPolicy-AdmxBacked-Begin -->
<!--/Policy--> > [!TIP]
<hr/> > 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 | RandomDelay |
| Friendly Name | Automatic Maintenance Random Delay |
| Location | Computer Configuration |
| Path | Windows Components > Maintenance Scheduler |
| Registry Key Name | Software\Policies\Microsoft\Windows\Task Scheduler\Maintenance |
| Registry Value Name | Randomized |
| ADMX File Name | msched.admx |
<!-- RandomDelayPolicy-AdmxBacked-End -->
[ADMX-backed policies in Policy CSP](./policies-in-policy-csp-admx-backed.md) <!-- RandomDelayPolicy-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- RandomDelayPolicy-Examples-End -->
<!-- RandomDelayPolicy-End -->
<!-- ADMX_msched-CspMoreInfo-Begin -->
<!-- Add any additional information about this CSP here. Anything outside this section will get overwritten. -->
<!-- ADMX_msched-CspMoreInfo-End -->
<!-- ADMX_msched-End -->
## Related articles
[Policy configuration service provider](policy-configuration-service-provider.md)

355
windows/client-management/mdm/policy-csp-admx-msdt.md
View File

@ -1,220 +1,245 @@
--- ---
title: Policy CSP - ADMX_MSDT title: ADMX_MSDT Policy CSP
description: Learn about Policy CSP - ADMX_MSDT. description: Learn more about the ADMX_MSDT Area in Policy CSP
author: vinaypamnani-msft
manager: aaroncz
ms.author: vinpa ms.author: vinpa
ms.date: 01/06/2023
ms.localizationpriority: medium ms.localizationpriority: medium
ms.topic: article
ms.prod: windows-client ms.prod: windows-client
ms.technology: itpro-manage ms.technology: itpro-manage
author: vinaypamnani-msft ms.topic: reference
ms.date: 12/09/2020
ms.reviewer:
manager: aaroncz
--- ---
<!-- Auto-Generated CSP Document -->
<!-- ADMX_MSDT-Begin -->
# Policy CSP - ADMX_MSDT # Policy CSP - ADMX_MSDT
>[!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). > [!TIP]
> 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).
<hr/> <!-- ADMX_MSDT-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- ADMX_MSDT-Editable-End -->
<!--Policies--> <!-- MsdtSupportProvider-Begin -->
## ADMX_MSDT policies ## MsdtSupportProvider
<dl> <!-- MsdtSupportProvider-Applicability-Begin -->
<dd> | Scope | Editions | Applicable OS |
<a href="#admx-msdt-msdtsupportprovider">ADMX_MSDT/MsdtSupportProvider</a> |:--|:--|:--|
</dd> | :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 |
<dd> <!-- MsdtSupportProvider-Applicability-End -->
<a href="#admx-msdt-msdttooldownloadpolicy">ADMX_MSDT/MsdtToolDownloadPolicy</a>
</dd>
<dd>
<a href="#admx-msdt-wdiscenarioexecutionpolicy">ADMX_MSDT/WdiScenarioExecutionPolicy</a>
</dd>
</dl>
<!-- MsdtSupportProvider-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/ADMX_MSDT/MsdtSupportProvider
```
<!-- MsdtSupportProvider-OmaUri-End -->
<hr/> <!-- MsdtSupportProvider-Description-Begin -->
<!-- Description-Source-ADMX -->
<!--Policy-->
<a href="" id="admx-msdt-msdtsupportprovider"></a>**ADMX_MSDT/MsdtSupportProvider**
<!--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-->
This policy setting configures Microsoft Support Diagnostic Tool (MSDT) interactive communication with the support provider. MSDT gathers diagnostic data for analysis by support professionals. This policy setting configures Microsoft Support Diagnostic Tool (MSDT) interactive communication with the support provider. MSDT gathers diagnostic data for analysis by support professionals.
If you enable this policy setting, users can use MSDT to collect and send diagnostic data to a support professional to resolve a problem. If you enable this policy setting, users can use MSDT to collect and send diagnostic data to a support professional to resolve a problem.
By default, the support provider is set to Microsoft Corporation. By default, the support provider is set to Microsoft Corporation.
If you disable this policy setting, MSDT can't run in support mode, and no data can be collected or sent to the support provider. If you disable this policy setting, MSDT cannot run in support mode, and no data can be collected or sent to the support provider.
If you don't configure this policy setting, MSDT support mode is enabled by default. If you do not configure this policy setting, MSDT support mode is enabled by default.
No reboots or service restarts are required for this policy setting to take effect. Changes take effect immediately. No reboots or service restarts are required for this policy setting to take effect. Changes take effect immediately.
<!-- MsdtSupportProvider-Description-End -->
<!--/Description--> <!-- MsdtSupportProvider-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- MsdtSupportProvider-Editable-End -->
<!-- MsdtSupportProvider-DFProperties-Begin -->
**Description framework properties**:
<!--ADMXBacked--> | Property name | Property value |
ADMX Info: |:--|:--|
- GP Friendly name: *Microsoft Support Diagnostic Tool: Turn on MSDT interactive communication with support provider* | Format | chr (string) |
- GP name: *MsdtSupportProvider* | Access Type | Add, Delete, Get, Replace |
- GP path: *System\Troubleshooting and Diagnostics\Microsoft Support Diagnostic Tool* <!-- MsdtSupportProvider-DFProperties-End -->
- GP ADMX file name: *MSDT.admx*
<!--/ADMXBacked--> <!-- MsdtSupportProvider-AdmxBacked-Begin -->
<!--/Policy--> > [!TIP]
<hr/> > 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--> **ADMX mapping**:
<a href="" id="admx-msdt-msdttooldownloadpolicy"></a>**ADMX_MSDT/MsdtToolDownloadPolicy**
<!--SupportedSKUs--> | Name | Value |
|:--|:--|
| Name | MsdtSupportProvider |
| Friendly Name | Microsoft Support Diagnostic Tool: Turn on MSDT interactive communication with support provider |
| Location | Computer Configuration |
| Path | System > Troubleshooting and Diagnostics > Microsoft Support Diagnostic Tool |
| Registry Key Name | SOFTWARE\Policies\Microsoft\Windows\ScriptedDiagnosticsProvider\Policy |
| Registry Value Name | DisableQueryRemoteServer |
| ADMX File Name | MSDT.admx |
<!-- MsdtSupportProvider-AdmxBacked-End -->
|Edition|Windows 10|Windows 11| <!-- MsdtSupportProvider-Examples-Begin -->
|--- |--- |--- | <!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
|Home|No|No| <!-- MsdtSupportProvider-Examples-End -->
|Pro|Yes|Yes|
|Windows SE|No|Yes|
|Business|Yes|Yes|
|Enterprise|Yes|Yes|
|Education|Yes|Yes|
<!--/SupportedSKUs--> <!-- MsdtSupportProvider-End -->
<hr/>
<!--Scope--> <!-- MsdtToolDownloadPolicy-Begin -->
[Scope](./policy-configuration-service-provider.md#policy-scope): ## MsdtToolDownloadPolicy
> [!div class = "checklist"] <!-- MsdtToolDownloadPolicy-Applicability-Begin -->
> * Device | 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 |
<!-- MsdtToolDownloadPolicy-Applicability-End -->
<hr/> <!-- MsdtToolDownloadPolicy-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/ADMX_MSDT/MsdtToolDownloadPolicy
```
<!-- MsdtToolDownloadPolicy-OmaUri-End -->
<!--/Scope--> <!-- MsdtToolDownloadPolicy-Description-Begin -->
<!--Description--> <!-- Description-Source-ADMX -->
This policy setting restricts the tool download policy for Microsoft Support Diagnostic Tool. This policy setting restricts the tool download policy for Microsoft Support Diagnostic Tool.
Microsoft Support Diagnostic Tool (MSDT) gathers diagnostic data for analysis by support professionals. Microsoft Support Diagnostic Tool (MSDT) gathers diagnostic data for analysis by support professionals. For some problems, MSDT may prompt the user to download additional tools for troubleshooting.
For some problems, MSDT may prompt the user to download more tools for troubleshooting. These tools are required to completely troubleshoot the problem. These tools are required to completely troubleshoot the problem. If tool download is restricted, it may not be possible to find the root cause of the problem.
If tool download is restricted, it may not be possible to find the root cause of the problem. If you enable this policy setting for remote troubleshooting, MSDT prompts the user to download additional tools to diagnose problems on remote computers only. If you enable this policy setting for local and remote troubleshooting, MSDT always prompts for additional tool downloading.
If you enable this policy setting for remote troubleshooting, MSDT prompts the user to download more tools to diagnose problems on remote computers only.
If you enable this policy setting for local and remote troubleshooting, MSDT always prompts for more tool downloading.
If you disable this policy setting, MSDT never downloads tools, and is unable to diagnose problems on remote computers. If you disable this policy setting, MSDT never downloads tools, and is unable to diagnose problems on remote computers.
If you don't configure this policy setting, MSDT prompts the user before downloading any extra tools. No reboots or service restarts are required for this policy setting to take effect. Changes take effect immediately. If you do not configure this policy setting, MSDT prompts the user before downloading any additional tools.
This policy setting will take effect only when MSDT is enabled.
This policy setting will only take effect when the Diagnostic Policy Service (DPS) is in the running state.
When the service is stopped or disabled, diagnostic scenarios aren't executed.
The DPS can be configured with the Services snap-in to the Microsoft Management Console.
<!--/Description-->
<!--ADMXBacked-->
ADMX Info:
- GP Friendly name: *Microsoft Support Diagnostic Tool: Restrict tool download*
- GP name: *MsdtToolDownloadPolicy*
- GP path: *System\Troubleshooting and Diagnostics\Microsoft Support Diagnostic Tool*
- GP ADMX file name: *MSDT.admx*
<!--/ADMXBacked-->
<!--/Policy-->
<hr/>
<!--Policy-->
<a href="" id="admx-msdt-wdiscenarioexecutionpolicy"></a>**ADMX_MSDT/WdiScenarioExecutionPolicy**
<!--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-->
This policy setting determines the execution level for Microsoft Support Diagnostic Tool.
Microsoft Support Diagnostic Tool (MSDT) gathers diagnostic data for analysis by support professionals. If you enable this policy setting, administrators can use MSDT to collect and send diagnostic data to a support professional to resolve a problem.
If you disable this policy setting, MSDT can't gather diagnostic data. If you don't configure this policy setting, MSDT is turned on by default.
This policy setting takes effect only if the diagnostics-wide scenario execution policy isn't configured.
No reboots or service restarts are required for this policy setting to take effect. Changes take effect immediately. No reboots or service restarts are required for this policy setting to take effect. Changes take effect immediately.
This policy setting will only take effect when the Diagnostic Policy Service (DPS) 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 take effect only when MSDT is enabled.
<!--/Description--> This policy setting will only take effect when the Diagnostic Policy Service (DPS) is in the running state. When the service is stopped or disabled, diagnostic scenarios are not executed. The DPS can be configured with the Services snap-in to the Microsoft Management Console.
<!-- MsdtToolDownloadPolicy-Description-End -->
<!-- MsdtToolDownloadPolicy-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- MsdtToolDownloadPolicy-Editable-End -->
<!--ADMXBacked--> <!-- MsdtToolDownloadPolicy-DFProperties-Begin -->
ADMX Info: **Description framework properties**:
- GP Friendly name: *Microsoft Support Diagnostic Tool: Configure execution level*
- GP name: *WdiScenarioExecutionPolicy*
- GP path: *System\Troubleshooting and Diagnostics\Microsoft Support Diagnostic Tool*
- GP ADMX file name: *MSDT.admx*
<!--/ADMXBacked--> | Property name | Property value |
<!--/Policy--> |:--|:--|
<hr/> | Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
<!-- MsdtToolDownloadPolicy-DFProperties-End -->
<!-- MsdtToolDownloadPolicy-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**:
<!--/Policies--> | Name | Value |
|:--|:--|
| Name | MsdtToolDownloadPolicy |
| Friendly Name | Microsoft Support Diagnostic Tool: Restrict tool download |
| Location | Computer Configuration |
| Path | System > Troubleshooting and Diagnostics > Microsoft Support Diagnostic Tool |
| Registry Key Name | SOFTWARE\Policies\Microsoft\Windows\WDI\{C295FBBA-FD47-46ac-8BEE-B1715EC634E5} |
| Registry Value Name | DownloadToolsEnabled |
| ADMX File Name | MSDT.admx |
<!-- MsdtToolDownloadPolicy-AdmxBacked-End -->
## Related topics <!-- MsdtToolDownloadPolicy-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- MsdtToolDownloadPolicy-Examples-End -->
[ADMX-backed policies in Policy CSP](./policies-in-policy-csp-admx-backed.md) <!-- MsdtToolDownloadPolicy-End -->
<!-- WdiScenarioExecutionPolicy-Begin -->
## WdiScenarioExecutionPolicy
<!-- WdiScenarioExecutionPolicy-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-Applicability-End -->
<!-- WdiScenarioExecutionPolicy-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/ADMX_MSDT/WdiScenarioExecutionPolicy
```
<!-- WdiScenarioExecutionPolicy-OmaUri-End -->
<!-- WdiScenarioExecutionPolicy-Description-Begin -->
<!-- Description-Source-ADMX -->
This policy setting determines the execution level for Microsoft Support Diagnostic Tool.
Microsoft Support Diagnostic Tool (MSDT) gathers diagnostic data for analysis by support professionals.
If you enable this policy setting, administrators can use MSDT to collect and send diagnostic data to a support professional to resolve a problem.
If you disable this policy setting, MSDT cannot gather diagnostic data.
If you do not configure this policy setting, MSDT is turned on by default.
This policy setting takes effect only if the diagnostics-wide scenario execution policy is not configured.
No reboots or service restarts are required for this policy setting to take effect. Changes take effect immediately.
This policy setting will only take effect when the Diagnostic Policy Service (DPS) 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-Description-End -->
<!-- WdiScenarioExecutionPolicy-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- WdiScenarioExecutionPolicy-Editable-End -->
<!-- WdiScenarioExecutionPolicy-DFProperties-Begin -->
**Description framework properties**:
| Property name | Property value |
|:--|:--|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
<!-- WdiScenarioExecutionPolicy-DFProperties-End -->
<!-- WdiScenarioExecutionPolicy-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 | Microsoft Support Diagnostic Tool: Configure execution level |
| Location | Computer Configuration |
| Path | System > Troubleshooting and Diagnostics > Microsoft Support Diagnostic Tool |
| Registry Key Name | SOFTWARE\Policies\Microsoft\Windows\WDI\{C295FBBA-FD47-46ac-8BEE-B1715EC634E5} |
| ADMX File Name | MSDT.admx |
<!-- WdiScenarioExecutionPolicy-AdmxBacked-End -->
<!-- WdiScenarioExecutionPolicy-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- WdiScenarioExecutionPolicy-Examples-End -->
<!-- WdiScenarioExecutionPolicy-End -->
<!-- ADMX_MSDT-CspMoreInfo-Begin -->
<!-- Add any additional information about this CSP here. Anything outside this section will get overwritten. -->
<!-- ADMX_MSDT-CspMoreInfo-End -->
<!-- ADMX_MSDT-End -->
## Related articles
[Policy configuration service provider](policy-configuration-service-provider.md)