mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-14 14:27:22 +00:00
Merge branch 'master' into prereq-urls
This commit is contained in:
Joey Caparas
commit
ba7ed42224
@ -14565,41 +14565,86 @@
|
||||
"redirect_url": "https://docs.microsoft.com/windows/client-management/mdm/policy-csps-supported-by-surface-hub",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/client-management/mdm/policy-csps-supported-by-surface-hub.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/client-management/mdm/policies-in-policy-csp-supported-by-surface-hub",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/client-management/mdm/policies-supported-by-iot-enterprise.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/client-management/mdm/policy-csps-supported-by-iot-enterprise",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/client-management/mdm/policy-csps-supported-by-iot-enterprise.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/client-management/mdm/policies-in-policy-csp-supported-by-iot-enterprise",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/client-management/mdm/policies-supported-by-iot-core.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/client-management/mdm/policy-csps-supported-by-iot-core",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/client-management/mdm/policy-csps-supported-by-iot-core.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/client-management/mdm/policies-in-policy-csp-supported-by-iot-core",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/client-management/mdm/policies-supported-by-hololens2.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/client-management/mdm/policy-csps-supported-by-hololens2",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/client-management/mdm/policy-csps-supported-by-hololens2.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens2",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/client-management/mdm/policies-supported-by-hololens-1st-gen-development-edition.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/client-management/mdm/policy-csps-supported-by-hololens-1st-gen-development-edition",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/client-management/mdm/policy-csps-supported-by-hololens-1st-gen-development-edition.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens-1st-gen-development-edition",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/client-management/mdm/policies-supported-by-hololens-1st-gen-commercial-suite.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/client-management/mdm/policy-csps-supported-by-hololens-1st-gen-commercial-suite",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/client-management/mdm/policy-csps-supported-by-hololens-1st-gen-commercial-suite.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens-1st-gen-commercial-suite",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/client-management/mdm/policies-admx-backed.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/client-management/mdm/policy-csps-admx-backed",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/client-management/mdm/policy-csps-admx-backed.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/client-management/mdm/policies-in-policy-csp-admx-backed",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/client-management/mdm/policies-supported-by-group-policy.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/client-management/mdm/policy-csps-supported-by-group-policy",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/client-management/mdm/policy-csps-supported-by-group-policy.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/client-management/mdm/policies-in-policy-csp-supported-by-group-policy",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/client-management/mdm/policy-csps-that-can-be-set-using-eas.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/client-management/mdm/policies-in-policy-csp-that-can-be-set-using-eas",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/keep-secure/collect-wip-audit-event-logs.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/threat-protection/windows-information-protection/collect-wip-audit-event-logs",
|
||||
|
||||
@ -159,14 +159,14 @@
|
||||
#### [Personalization DDF file](personalization-ddf.md)
|
||||
### [Policy CSP](policy-configuration-service-provider.md)
|
||||
#### [Policy DDF file](policy-ddf-file.md)
|
||||
#### [Policy CSPs supported by Group Policy](policy-csps-supported-by-group-policy.md)
|
||||
#### [ADMX-backed policy CSPs](policy-csps-admx-backed.md)
|
||||
#### [Policy CSPs supported by HoloLens 2](policy-csps-supported-by-hololens2.md)
|
||||
#### [Policy CSPs supported by HoloLens (1st gen) Commercial Suite](policy-csps-supported-by-hololens-1st-gen-commercial-suite.md)
|
||||
#### [Policy CSPs supported by HoloLens (1st gen) Development Edition](policy-csps-supported-by-hololens-1st-gen-development-edition.md)
|
||||
#### [Policy CSPs supported by Windows 10 IoT Enterprise](policy-csps-supported-by-iot-enterprise.md)
|
||||
#### [Policy CSPs supported by Windows 10 IoT Core](policy-csps-supported-by-iot-core.md)
|
||||
#### [Policy CSPs supported by Microsoft Surface Hub](policy-csps-supported-by-surface-hub.md)
|
||||
#### [Policies in Policy CSP supported by Group Policy](policy-csps-supported-by-group-policy.md)
|
||||
#### [ADMX-backed policies in Policy CSP](policy-csps-admx-backed.md)
|
||||
#### [Policies in Policy CSP supported by HoloLens 2](policy-csps-supported-by-hololens2.md)
|
||||
#### [Policies in Policy CSP supported by HoloLens (1st gen) Commercial Suite](policy-csps-supported-by-hololens-1st-gen-commercial-suite.md)
|
||||
#### [Policies in Policy CSP supported by HoloLens (1st gen) Development Edition](policy-csps-supported-by-hololens-1st-gen-development-edition.md)
|
||||
#### [Policies in Policy CSP supported by Windows 10 IoT Enterprise](policy-csps-supported-by-iot-enterprise.md)
|
||||
#### [Policies in Policy CSP supported by Windows 10 IoT Core](policy-csps-supported-by-iot-core.md)
|
||||
#### [Policies in Policy CSP supported by Microsoft Surface Hub](policy-csps-supported-by-surface-hub.md)
|
||||
#### [Policy CSPs that can be set using Exchange Active Sync (EAS)](policy-csps-that-can-be-set-using-eas.md)
|
||||
#### [AboveLock](policy-csp-abovelock.md)
|
||||
#### [Accounts](policy-csp-accounts.md)
|
||||
|
||||
@ -36,9 +36,8 @@ Supported operation is Get.
|
||||
<a href="" id="devicestatus-cellularidentities"></a>**DeviceStatus/CellularIdentities**
|
||||
Required. Node for queries on the SIM cards.
|
||||
|
||||
> **Note** Multiple SIMs are supported.
|
||||
|
||||
|
||||
>[!NOTE]
|
||||
>Multiple SIMs are supported.
|
||||
|
||||
<a href="" id="devicestatus-cellularidentities-imei"></a>**DeviceStatus/CellularIdentities/**<strong>*IMEI*</strong>
|
||||
The unique International Mobile Station Equipment Identity (IMEI) number of the mobile device. An IMEI is present for each SIM card on the device.
|
||||
@ -107,7 +106,7 @@ Supported operation is Get.
|
||||
Node for the compliance query.
|
||||
|
||||
<a href="" id="devicestatus-compliance-encryptioncompliance"></a>**DeviceStatus/Compliance/EncryptionCompliance**
|
||||
Boolean value that indicates compliance with the enterprise encryption policy. The value is one of the following:
|
||||
Boolean value that indicates compliance with the enterprise encryption policy for OS (system) drives. The value is one of the following:
|
||||
|
||||
- 0 - not encrypted
|
||||
- 1 - encrypted
|
||||
|
||||
@ -33,7 +33,7 @@ See [Support Tip: Ingesting Office ADMX-backed policies using Microsoft Intune](
|
||||
## Enable a policy
|
||||
|
||||
> [!NOTE]
|
||||
> See [Understanding ADMX-backed policy CSPs](https://docs.microsoft.com/windows/client-management/mdm/understanding-admx-backed-policies).
|
||||
> See [Understanding ADMX-backed policies in Policy CSP](https://docs.microsoft.com/windows/client-management/mdm/understanding-admx-backed-policies).
|
||||
|
||||
1. Find the policy from the list [ADMX-backed policies](policy-csps-admx-backed.md). You need the following information listed in the policy description.
|
||||
- GP English name
|
||||
|
||||
@ -2515,7 +2515,7 @@ How do I turn if off? | The service can be stopped from the "Services" console o
|
||||
</ul>
|
||||
<p>Added a new section:</p>
|
||||
<ul>
|
||||
<li><a href="policy-csps-supported-by-group-policy.md" data-raw-source="[[Policy CSPs supported by Group Policy](policy-csps-supported-by-group-policy.md)">[Policy CSPs supported by Group Policy</a> - list of policies in Policy CSP that has corresponding Group Policy. The policy description contains the GP information, such as GP policy name and variable name.</li>
|
||||
<li><a href="policy-csps-supported-by-group-policy.md" data-raw-source="[[Policies in Policy CSP supported by Group Policy](policy-csps-supported-by-group-policy.md)">[Policies in Policy CSP supported by Group Policy</a> - list of policies in Policy CSP that has corresponding Group Policy. The policy description contains the GP information, such as GP policy name and variable name.</li>
|
||||
</ul>
|
||||
</td></tr>
|
||||
<tr>
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: ADMX-backed policy CSPs
|
||||
description: ADMX-backed policy CSPs
|
||||
title: ADMX-backed policies in Policy CSP
|
||||
description: ADMX-backed policies in Policy CSP
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: dansimp
|
||||
@ -9,15 +9,15 @@ ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 08/18/2020
|
||||
ms.date: 10/08/2020
|
||||
---
|
||||
|
||||
# ADMX-backed policy CSPs
|
||||
# ADMX-backed policies in Policy CSP
|
||||
|
||||
> [!div class="op_single_selector"]
|
||||
>
|
||||
> - [Policy CSPs supported by Group Policy](policy-csps-supported-by-group-policy.md)
|
||||
> - [ADMX-backed policy-CSPs](policy-csps-admx-backed.md)
|
||||
> - [Policies in Policy CSP supported by Group Policy](policy-csps-supported-by-group-policy.md)
|
||||
> - [ADMX-backed policies in Policy CSP](policy-csps-admx-backed.md)
|
||||
>
|
||||
|
||||
- [ActiveXControls/ApprovedInstallationSites](./policy-csp-activexcontrols.md#activexcontrols-approvedinstallationsites)
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Policy CSPs supported by Group Policy
|
||||
description: Policy CSPs supported by Group Policy
|
||||
title: Policies in Policy CSP supported by Group Policy
|
||||
description: Policies in Policy CSP supported by Group Policy
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: dansimp
|
||||
@ -12,12 +12,12 @@ ms.localizationpriority: medium
|
||||
ms.date: 07/18/2019
|
||||
---
|
||||
|
||||
# Policy CSPs supported by Group Policy
|
||||
# Policies in Policy CSP supported by Group Policy
|
||||
|
||||
> [!div class="op_single_selector"]
|
||||
>
|
||||
> - [Policy CSPs supported by Group Policy](policy-csps-supported-by-group-policy.md)
|
||||
> - [ADMX-backed policy CSPs](policy-csps-admx-backed.md)
|
||||
> - [Policies in Policy CSP supported by Group Policy](policy-csps-supported-by-group-policy.md)
|
||||
> - [ADMX-backed policies in Policy CSP](policy-csps-admx-backed.md)
|
||||
>
|
||||
|
||||
- [AboveLock/AllowCortanaAboveLock](./policy-csp-abovelock.md#abovelock-allowcortanaabovelock)
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Policy CSPs supported by HoloLens (1st gen) Commercial Suite
|
||||
description: Policy CSPs supported by HoloLens (1st gen) Commercial Suite
|
||||
title: Policies in Policy CSP supported by HoloLens (1st gen) Commercial Suite
|
||||
description: Policies in Policy CSP supported by HoloLens (1st gen) Commercial Suite
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: dansimp
|
||||
@ -12,7 +12,7 @@ ms.localizationpriority: medium
|
||||
ms.date: 09/17/2019
|
||||
---
|
||||
|
||||
# Policy CSPs supported by HoloLens (1st gen) Commercial Suite
|
||||
# Policies in Policy CSP supported by HoloLens (1st gen) Commercial Suite
|
||||
|
||||
> [!div class="op_single_selector"]
|
||||
>
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Policy CSPs supported by HoloLens (1st gen) Development Edition
|
||||
description: Policy CSPs supported by HoloLens (1st gen) Development Edition
|
||||
title: Policies in Policy CSP supported by HoloLens (1st gen) Development Edition
|
||||
description: Policies in Policy CSP supported by HoloLens (1st gen) Development Edition
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: dansimp
|
||||
@ -12,7 +12,7 @@ ms.localizationpriority: medium
|
||||
ms.date: 07/18/2019
|
||||
---
|
||||
|
||||
# Policy CSPs supported by HoloLens (1st gen) Development Edition
|
||||
# Policies in Policy CSP supported by HoloLens (1st gen) Development Edition
|
||||
|
||||
> [!div class="op_single_selector"]
|
||||
>
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Policy CSPs supported by HoloLens 2
|
||||
description: Policy CSPs supported by HoloLens 2
|
||||
title: Policies in Policy CSP supported by HoloLens 2
|
||||
description: Policies in Policy CSP supported by HoloLens 2
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: dansimp
|
||||
@ -12,7 +12,7 @@ ms.localizationpriority: medium
|
||||
ms.date: 05/11/2020
|
||||
---
|
||||
|
||||
# Policy CSPs supported by HoloLens 2
|
||||
# Policies in Policy CSP supported by HoloLens 2
|
||||
|
||||
> [!div class="op_single_selector"]
|
||||
>
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Policy CSPs supported by Windows 10 IoT Core
|
||||
description: Policy CSPs supported by Windows 10 IoT Core
|
||||
title: Policies in Policy CSP supported by Windows 10 IoT Core
|
||||
description: Policies in Policy CSP supported by Windows 10 IoT Core
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: dansimp
|
||||
@ -12,7 +12,7 @@ ms.localizationpriority: medium
|
||||
ms.date: 09/16/2019
|
||||
---
|
||||
|
||||
# Policy CSPs supported by Windows 10 IoT Core
|
||||
# Policies in Policy CSP supported by Windows 10 IoT Core
|
||||
|
||||
> [!div class="op_single_selector"]
|
||||
>
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Policy CSPs supported by Windows 10 IoT Enterprise
|
||||
description: Policy CSPs supported by Windows 10 IoT Enterprise
|
||||
title: Policies in Policy CSP supported by Windows 10 IoT Enterprise
|
||||
description: Policies in Policy CSP supported by Windows 10 IoT Enterprise
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: dansimp
|
||||
@ -12,7 +12,7 @@ ms.localizationpriority: medium
|
||||
ms.date: 07/18/2019
|
||||
---
|
||||
|
||||
# Policy CSPs supported by Windows 10 IoT Enterprise
|
||||
# Policies in Policy CSP supported by Windows 10 IoT Enterprise
|
||||
|
||||
> [!div class="op_single_selector"]
|
||||
>
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Policy CSPs supported by Microsoft Surface Hub
|
||||
description: Policy CSPs supported by Microsoft Surface Hub
|
||||
title: Policies in Policy CSP supported by Microsoft Surface Hub
|
||||
description: Policies in Policy CSP supported by Microsoft Surface Hub
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: dansimp
|
||||
@ -12,7 +12,7 @@ ms.localizationpriority: medium
|
||||
ms.date: 07/22/2020
|
||||
---
|
||||
|
||||
# Policy CSPs supported by Microsoft Surface Hub
|
||||
# Policies in Policy CSP supported by Microsoft Surface Hub
|
||||
|
||||
|
||||
- [ApplicationManagement/AllowAppStoreAutoUpdate](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-applicationmanagement#applicationmanagement-allowappstoreautoupdate)
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Policy CSPs that can be set using Exchange Active Sync (EAS)
|
||||
description: Policy CSPs that can be set using Exchange Active Sync (EAS)
|
||||
title: Policies in Policy CSP that can be set using Exchange Active Sync (EAS)
|
||||
description: Policies in Policy CSP that can be set using Exchange Active Sync (EAS)
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: dansimp
|
||||
@ -12,7 +12,7 @@ ms.localizationpriority: medium
|
||||
ms.date: 07/18/2019
|
||||
---
|
||||
|
||||
# Policy CSPs that can be set using Exchange Active Sync (EAS)
|
||||
# Policies in Policy CSP that can be set using Exchange Active Sync (EAS)
|
||||
|
||||
- [Camera/AllowCamera](policy-csp-camera.md#camera-allowcamera)
|
||||
- [Cellular/ShowAppCellularAccessUI](policy-csp-cellular.md#cellular-showappcellularaccessui)
|
||||
@ -4901,27 +4901,27 @@ The following diagram shows the Policy configuration service provider in tree fo
|
||||
</dd>
|
||||
</dl>
|
||||
|
||||
## Policy CSPs supported by Group Policy and ADMX-backed policy CSPs
|
||||
- [Policy CSPs supported by Group Policy](policy-csps-supported-by-group-policy.md)
|
||||
- [ADMX-backed policy CSPs](policy-csps-admx-backed.md)
|
||||
## Policies in Policy CSP supported by Group Policy and ADMX-backed policies in Policy CSP
|
||||
- [Policies in Policy CSP supported by Group Policy](policy-csps-supported-by-group-policy.md)
|
||||
- [ADMX-backed policies in Policy CSP](policy-csps-admx-backed.md)
|
||||
|
||||
> [!NOTE]
|
||||
> Not all Policy CSPs supported by Group Policy are ADMX-backed. For more details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
||||
> Not all Policies in Policy CSP supported by Group Policy are ADMX-backed. For more details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
||||
|
||||
## Policy CSPs supported by HoloLens devices
|
||||
- [Policy CSPs supported by HoloLens 2](policy-csps-supported-by-hololens2.md)
|
||||
- [Policy CSPs supported by HoloLens (1st gen) Commercial Suite](policy-csps-supported-by-hololens-1st-gen-commercial-suite.md)
|
||||
- [Policy CSPs supported by HoloLens (1st gen) Development Edition](policy-csps-supported-by-hololens-1st-gen-development-edition.md)
|
||||
## Policies in Policy CSP supported by HoloLens devices
|
||||
- [Policies in Policy CSP supported by HoloLens 2](policy-csps-supported-by-hololens2.md)
|
||||
- [Policies in Policy CSP supported by HoloLens (1st gen) Commercial Suite](policy-csps-supported-by-hololens-1st-gen-commercial-suite.md)
|
||||
- [Policies in Policy CSP supported by HoloLens (1st gen) Development Edition](policy-csps-supported-by-hololens-1st-gen-development-edition.md)
|
||||
|
||||
## Policy CSPs supported by Windows 10 IoT
|
||||
- [Policy CSPs supported by Windows 10 IoT Enterprise](policy-csps-supported-by-iot-enterprise.md)
|
||||
- [Policy CSPs supported by Windows 10 IoT Core](policy-csps-supported-by-iot-core.md)
|
||||
## Policies in Policy CSP supported by Windows 10 IoT
|
||||
- [Policies in Policy CSP supported by Windows 10 IoT Enterprise](policy-csps-supported-by-iot-enterprise.md)
|
||||
- [Policies in Policy CSP supported by Windows 10 IoT Core](policy-csps-supported-by-iot-core.md)
|
||||
|
||||
## Policy CSPs supported by Microsoft Surface Hub
|
||||
- [Policy CSPs supported by Microsoft Surface Hub](policy-csps-supported-by-surface-hub.md)
|
||||
## Policies in Policy CSP supported by Microsoft Surface Hub
|
||||
- [Policies in Policy CSP supported by Microsoft Surface Hub](policy-csps-supported-by-surface-hub.md)
|
||||
|
||||
## Policy CSPs that can be set using Exchange ActiveSync (EAS)
|
||||
- [Policy CSPs that can be set using Exchange ActiveSync (EAS)](policy-csps-that-can-be-set-using-eas.md)
|
||||
## Policies in Policy CSP that can be set using Exchange ActiveSync (EAS)
|
||||
- [Policies in Policy CSP that can be set using Exchange ActiveSync (EAS)](policy-csps-that-can-be-set-using-eas.md)
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
@ -97,7 +97,7 @@ For information about supported cipher suites, see [Cipher Suites in TLS/SSL (Sc
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *SSL Cipher Suite Order*
|
||||
- GP name: *Functions*
|
||||
- GP name: *SSLCipherSuiteOrder*
|
||||
- GP path: *Network/SSL Configuration Settings*
|
||||
- GP ADMX file name: *CipherSuiteOrder.admx*
|
||||
|
||||
@ -180,7 +180,7 @@ CertUtil.exe -DisplayEccCurve
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *ECC Curve Order*
|
||||
- GP name: *EccCurves*
|
||||
- GP name: *SSLCurveOrder*
|
||||
- GP path: *Network/SSL Configuration Settings*
|
||||
- GP ADMX file name: *CipherSuiteOrder.admx*
|
||||
|
||||
|
||||
@ -99,7 +99,7 @@ This setting appears in the Computer Configuration and User Configuration folder
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Download missing COM components*
|
||||
- GP name: *COMClassStore*
|
||||
- GP name: *AppMgmt_COM_SearchForCLSID_1*
|
||||
- GP path: *System*
|
||||
- GP ADMX file name: *COM.admx*
|
||||
|
||||
@ -174,7 +174,7 @@ This setting appears in the Computer Configuration and User Configuration folder
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Download missing COM components*
|
||||
- GP name: *COMClassStore*
|
||||
- GP name: *AppMgmt_COM_SearchForCLSID_2*
|
||||
- GP path: *System*
|
||||
- GP ADMX file name: *COM.admx*
|
||||
|
||||
|
||||
@ -96,7 +96,7 @@ If you disable or do not configure this setting, Digital Locker can be run.
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Do not allow Digital Locker to run*
|
||||
- GP name: *DoNotRunDigitalLocker*
|
||||
- GP name: *Digitalx_DiableApplication_TitleText_1*
|
||||
- GP path: *Windows Components/Digital Locker*
|
||||
- GP ADMX file name: *DigitalLocker.admx*
|
||||
|
||||
@ -167,7 +167,7 @@ If you disable or do not configure this setting, Digital Locker can be run.
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Do not allow Digital Locker to run*
|
||||
- GP name: *DoNotRunDigitalLocker*
|
||||
- GP name: *Digitalx_DiableApplication_TitleText_2*
|
||||
- GP path: *Windows Components/Digital Locker*
|
||||
- GP ADMX file name: *DigitalLocker.admx*
|
||||
|
||||
|
||||
@ -109,7 +109,7 @@ If you disable or do not configure this policy setting, the default internal col
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Specify a default color*
|
||||
- GP name: *DefaultColorizationColorState*
|
||||
- GP name: *DwmDefaultColorizationColor_1*
|
||||
- GP path: *Windows Components/Desktop Window Manager/Window Frame Coloring*
|
||||
- GP ADMX file name: *DWM.admx*
|
||||
|
||||
@ -182,7 +182,7 @@ If you disable or do not configure this policy setting, the default internal col
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Specify a default color*
|
||||
- GP name: *DefaultColorizationColorState*
|
||||
- GP name: *DwmDefaultColorizationColor_2*
|
||||
- GP path: *Windows Components/Desktop Window Manager/Window Frame Coloring*
|
||||
- GP ADMX file name: *DWM.admx*
|
||||
|
||||
@ -253,7 +253,7 @@ Changing this policy setting requires a logoff for it to be applied.
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Do not allow window animations*
|
||||
- GP name: *DisallowAnimations*
|
||||
- GP name: *DwmDisallowAnimations_1*
|
||||
- GP path: *Windows Components/Desktop Window Manager*
|
||||
- GP ADMX file name: *DWM.admx*
|
||||
|
||||
@ -324,7 +324,7 @@ Changing this policy setting requires a logoff for it to be applied.
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Do not allow window animations*
|
||||
- GP name: *DisallowAnimations*
|
||||
- GP name: *DwmDisallowAnimations_2*
|
||||
- GP path: *Windows Components/Desktop Window Manager*
|
||||
- GP ADMX file name: *DWM.admx*
|
||||
|
||||
@ -396,7 +396,7 @@ If you disable or do not configure this policy setting, you allow users to chang
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Do not allow color changes*
|
||||
- GP name: *DisallowColorizationColorChanges*
|
||||
- GP name: *DwmDisallowColorizationColorChanges_1*
|
||||
- GP path: *Windows Components/Desktop Window Manager/Window Frame Coloring*
|
||||
- GP ADMX file name: *DWM.admx*
|
||||
|
||||
@ -468,7 +468,7 @@ If you disable or do not configure this policy setting, you allow users to chang
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Do not allow color changes*
|
||||
- GP name: *DisallowColorizationColorChanges*
|
||||
- GP name: *DwmDisallowColorizationColorChanges_2*
|
||||
- GP path: *Windows Components/Desktop Window Manager/Window Frame Coloring*
|
||||
- GP ADMX file name: *DWM.admx*
|
||||
|
||||
|
||||
@ -97,7 +97,7 @@ This setting applies across all subscriptions for the forwarder (source computer
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Configure forwarder resource usage*
|
||||
- GP name: *MaxForwardingRate*
|
||||
- GP name: *ForwarderResourceUsage*
|
||||
- GP path: *Windows Components/Event Forwarding*
|
||||
- GP ADMX file name: *EventForwarding.admx*
|
||||
|
||||
|
||||
@ -94,7 +94,7 @@ By default, the RPC protocol message between File Server VSS provider and File S
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Allow or Disallow use of encryption to protect the RPC protocol messages between File Share Shadow Copy Provider running on application server and File Share Shadow Copy Agent running on the file servers.*
|
||||
- GP name: *EncryptProtocol*
|
||||
- GP name: *Pol_EncryptProtocol*
|
||||
- GP path: *System/File Share Shadow Copy Provider*
|
||||
- GP ADMX file name: *FileServerVSSProvider.admx*
|
||||
|
||||
|
||||
@ -106,7 +106,7 @@ Available in Windows 10 Insider Preview Build 20185. Compression can add to the
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Do not allow compression on all NTFS volumes*
|
||||
- GP name: *NtfsDisableCompression*
|
||||
- GP name: *DisableCompression*
|
||||
- GP path: *System/Filesystem/NTFS*
|
||||
- GP ADMX file name: *FileSys.admx*
|
||||
|
||||
@ -237,7 +237,7 @@ Available in Windows 10 Insider Preview Build 20185. Encryption can add to the p
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Do not allow encryption on all NTFS volumes*
|
||||
- GP name: *NtfsDisableEncryption*
|
||||
- GP name: *DisableEncryption*
|
||||
- GP path: *System/Filesystem/NTFS*
|
||||
- GP ADMX file name: *FileSys.admx*
|
||||
|
||||
@ -300,7 +300,7 @@ Available in Windows 10 Insider Preview Build 20185. Encrypting the page file pr
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Enable NTFS pagefile encryption*
|
||||
- GP name: *NtfsEncryptPagingFile*
|
||||
- GP name: *EnablePagefileEncryption*
|
||||
- GP path: *System/Filesystem/NTFS*
|
||||
- GP ADMX file name: *FileSys.admx*
|
||||
|
||||
@ -428,7 +428,7 @@ If you enable short names on all volumes then short names will always be generat
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Short name creation options*
|
||||
- GP name: *NtfsDisable8dot3NameCreation*
|
||||
- GP name: *ShortNameCreationSettings*
|
||||
- GP path: *System/Filesystem/NTFS*
|
||||
- GP ADMX file name: *FileSys.admx*
|
||||
|
||||
@ -502,7 +502,7 @@ For more information, refer to the Windows Help section.
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Selectively allow the evaluation of a symbolic link*
|
||||
- GP name: *SymlinkLocalToLocalEvaluation*
|
||||
- GP name: *SymlinkEvaluation*
|
||||
- GP path: *System/Filesystem*
|
||||
- GP ADMX file name: *FileSys.admx*
|
||||
|
||||
@ -565,7 +565,7 @@ Available in Windows 10 Insider Preview Build 20185. TXF deprecated features inc
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Enable / disable TXF deprecated features*
|
||||
- GP name: *NtfsEnableTxfDeprecatedFunctionality*
|
||||
- GP name: *TxfDeprecatedFunctionality*
|
||||
- GP path: *System/Filesystem/NTFS*
|
||||
- GP ADMX file name: *FileSys.admx*
|
||||
|
||||
|
||||
@ -329,7 +329,7 @@ If you disable or not configure this policy setting, Windows Vista, Windows 7, W
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Use localized subfolder names when redirecting Start Menu and My Documents*
|
||||
- GP name: *LocalizeXPRelativePaths*
|
||||
- GP name: *LocalizeXPRelativePaths_1*
|
||||
- GP path: *System/Folder Redirection*
|
||||
- GP ADMX file name: *FolderRedirection.admx*
|
||||
|
||||
@ -401,7 +401,7 @@ If you disable or not configure this policy setting, Windows Vista, Windows 7, W
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Use localized subfolder names when redirecting Start Menu and My Documents*
|
||||
- GP name: *LocalizeXPRelativePaths*
|
||||
- GP name: *LocalizeXPRelativePaths_2*
|
||||
- GP path: *System/Folder Redirection*
|
||||
- GP ADMX file name: *FolderRedirection.admx*
|
||||
|
||||
@ -474,7 +474,7 @@ If you disable or do not configure this policy setting and the user has redirect
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Redirect folders on primary computers only*
|
||||
- GP name: *PrimaryComputerEnabledFR*
|
||||
- GP name: *PrimaryComputer_FR_1*
|
||||
- GP path: *System/Folder Redirection*
|
||||
- GP ADMX file name: *FolderRedirection.admx*
|
||||
|
||||
@ -547,7 +547,7 @@ If you disable or do not configure this policy setting and the user has redirect
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Redirect folders on primary computers only*
|
||||
- GP name: *PrimaryComputerEnabledFR*
|
||||
- GP name: *PrimaryComputer_FR_2*
|
||||
- GP path: *System/Folder Redirection*
|
||||
- GP ADMX file name: *FolderRedirection.admx*
|
||||
|
||||
|
||||
@ -185,7 +185,7 @@ For additional options, see the "Restrict these programs from being launched fro
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Restrict potentially unsafe HTML Help functions to specified folders*
|
||||
- GP name: *HelpQualifiedRootDir*
|
||||
- GP name: *HelpQualifiedRootDir_Comp*
|
||||
- GP path: *System*
|
||||
- GP ADMX file name: *Help.admx*
|
||||
|
||||
@ -259,7 +259,7 @@ If you disable or do not configure this policy setting, users can run all applic
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Restrict these programs from being launched from Help*
|
||||
- GP name: *DisableInHelp*
|
||||
- GP name: *RestrictRunFromHelp*
|
||||
- GP path: *System*
|
||||
- GP ADMX file name: *Help.admx*
|
||||
|
||||
@ -332,7 +332,7 @@ If you disable or do not configure this policy setting, users can run all applic
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Restrict these programs from being launched from Help*
|
||||
- GP name: *DisableInHelp*
|
||||
- GP name: *RestrictRunFromHelp_Comp*
|
||||
- GP path: *System*
|
||||
- GP ADMX file name: *Help.admx*
|
||||
|
||||
|
||||
@ -100,7 +100,7 @@ If you disable or do not configure this policy setting, the default behavior app
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Turn off Active Help*
|
||||
- GP name: *NoActiveHelp*
|
||||
- GP name: *ActiveHelp*
|
||||
- GP path: *Windows Components/Online Assistance*
|
||||
- GP ADMX file name: *HelpAndSupport.admx*
|
||||
|
||||
@ -171,7 +171,7 @@ Users can use the control to provide feedback on the quality and usefulness of t
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Turn off Help Ratings*
|
||||
- GP name: *NoExplicitFeedback*
|
||||
- GP name: *HPExplicitFeedback*
|
||||
- GP path: *System/Internet Communication Management/Internet Communication settings*
|
||||
- GP ADMX file name: *HelpAndSupport.admx*
|
||||
|
||||
@ -239,7 +239,7 @@ If you disable or do not configure this policy setting, users can turn on the He
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Turn off Help Experience Improvement Program*
|
||||
- GP name: *NoImplicitFeedback*
|
||||
- GP name: *HPImplicitFeedback*
|
||||
- GP path: *System/Internet Communication Management/Internet Communication settings*
|
||||
- GP ADMX file name: *HelpAndSupport.admx*
|
||||
|
||||
@ -308,7 +308,7 @@ If you disable or do not configure this policy setting, users can access online
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Turn off Windows Online*
|
||||
- GP name: *NoOnlineAssist*
|
||||
- GP name: *HPOnlineAssistance*
|
||||
- GP path: *System/Internet Communication Management/Internet Communication settings*
|
||||
- GP ADMX file name: *HelpAndSupport.admx*
|
||||
|
||||
|
||||
@ -133,7 +133,7 @@ Impact on domain controller performance when this policy setting is enabled:
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *KDC support for claims, compound authentication and Kerberos armoring*
|
||||
- GP name: *EnableCbacAndArmor*
|
||||
- GP name: *CbacAndArmor*
|
||||
- GP path: *System/KDC*
|
||||
- GP ADMX file name: *kdc.admx*
|
||||
|
||||
@ -204,7 +204,7 @@ To ensure consistent behavior, this policy setting must be supported and set ide
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Use forest search order*
|
||||
- GP name: *UseForestSearch*
|
||||
- GP name: *ForestSearch*
|
||||
- GP path: *System/KDC*
|
||||
- GP ADMX file name: *kdc.admx*
|
||||
|
||||
@ -420,7 +420,7 @@ If you disable or do not configure this policy setting, the threshold value defa
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Warning for large Kerberos tickets*
|
||||
- GP name: *EnableTicketSizeThreshold*
|
||||
- GP name: *TicketSizeThreshold*
|
||||
- GP path: *System/KDC*
|
||||
- GP ADMX file name: *kdc.admx*
|
||||
|
||||
@ -494,7 +494,7 @@ If you disable or do not configure this policy setting, the domain controller do
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Provide information about previous logons to client computers*
|
||||
- GP name: *EmitLILI*
|
||||
- GP name: *emitlili*
|
||||
- GP path: *System/KDC*
|
||||
- GP ADMX file name: *kdc.admx*
|
||||
|
||||
|
||||
@ -116,7 +116,7 @@ Arrange the desired cipher suites in the edit box, one cipher suite per line, in
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Cipher suite order*
|
||||
- GP name: *CipherSuiteOrder*
|
||||
- GP name: *Pol_CipherSuiteOrder*
|
||||
- GP path: *Network/Lanman Server*
|
||||
- GP ADMX file name: *LanmanServer.admx*
|
||||
|
||||
@ -199,7 +199,7 @@ In circumstances where this policy setting is enabled, you can also select the f
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Hash Publication for BranchCache*
|
||||
- GP name: *HashPublicationForPeerCaching*
|
||||
- GP name: *Pol_HashPublication*
|
||||
- GP path: *Network/Lanman Server*
|
||||
- GP ADMX file name: *LanmanServer.admx*
|
||||
|
||||
@ -286,7 +286,7 @@ Hash version supported:
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Hash Version support for BranchCache*
|
||||
- GP name: *HashSupportVersion*
|
||||
- GP name: *Pol_HashSupportVersion*
|
||||
- GP path: *Network/Lanman Server*
|
||||
- GP ADMX file name: *LanmanServer.admx*
|
||||
|
||||
@ -358,7 +358,7 @@ If you disable or do not configure this policy setting, the SMB server will sele
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Honor cipher suite order*
|
||||
- GP name: *HonorCipherSuiteOrder*
|
||||
- GP name: *Pol_HonorCipherSuiteOrder*
|
||||
- GP path: *Network/Lanman Server*
|
||||
- GP ADMX file name: *LanmanServer.admx*
|
||||
|
||||
|
||||
@ -96,7 +96,7 @@ If you disable or do not configure this policy setting, the default behavior of
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Turn on Mapper I/O (LLTDIO) driver*
|
||||
- GP name: *EnableLLTDIO*
|
||||
- GP name: *LLTD_EnableLLTDIO*
|
||||
- GP path: *Network/Link-Layer Topology Discovery*
|
||||
- GP ADMX file name: *LinkLayerTopologyDiscovery.admx*
|
||||
|
||||
@ -167,7 +167,7 @@ If you disable or do not configure this policy setting, the default behavior for
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Turn on Responder (RSPNDR) driver*
|
||||
- GP name: *EnableRspndr*
|
||||
- GP name: *LLTD_EnableRspndr*
|
||||
- GP path: *Network/Link-Layer Topology Discovery*
|
||||
- GP ADMX file name: *LinkLayerTopologyDiscovery.admx*
|
||||
|
||||
|
||||
@ -113,7 +113,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *ActiveX Control*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_ActiveXControl*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMC.admx*
|
||||
|
||||
@ -192,7 +192,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Extended View (Web View)*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_ExtendView*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins*
|
||||
- GP ADMX file name: *MMC.admx*
|
||||
|
||||
@ -271,7 +271,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Link to Web Address*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_LinkToWeb*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMC.admx*
|
||||
|
||||
@ -344,7 +344,7 @@ If you disable this setting or do not configure it, users can enter author mode
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Restrict the user from entering author mode*
|
||||
- GP name: *RestrictAuthorMode*
|
||||
- GP name: *MMC_Restrict_Author*
|
||||
- GP path: *Windows Components\Microsoft Management Console*
|
||||
- GP ADMX file name: *MMC.admx*
|
||||
|
||||
@ -422,7 +422,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Restrict users to the explicitly permitted list of snap-ins*
|
||||
- GP name: *RestrictToPermittedSnapins*
|
||||
- GP name: *MMC_Restrict_To_Permitted_Snapins*
|
||||
- GP path: *Windows Components\Microsoft Management Console*
|
||||
- GP ADMX file name: *MMC.admx*
|
||||
|
||||
|
||||
@ -408,7 +408,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Administrative Templates (Computers)*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_ADMComputers_1*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Group Policy snap-in extensions*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -485,7 +485,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Administrative Templates (Computers)*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_ADMComputers_2*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Resultant Set of Policy snap-in extensions*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -563,7 +563,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Administrative Templates (Users)*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_ADMUsers_1*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Group Policy snap-in extensions*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -641,7 +641,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Administrative Templates (Users)*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_ADMUsers_2*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Resultant Set of Policy snap-in extensions*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -719,7 +719,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *ADSI Edit*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_ADSI*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -797,7 +797,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Active Directory Domains and Trusts*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_ActiveDirDomTrusts*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -875,7 +875,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Active Directory Sites and Services*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_ActiveDirSitesServices*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -953,7 +953,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Active Directory Users and Computers*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_ActiveDirUsersComp*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -1031,7 +1031,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *AppleTalk Routing*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_AppleTalkRouting*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -1109,7 +1109,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Authorization Manager*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_AuthMan*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -1187,7 +1187,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Certification Authority*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_CertAuth*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -1264,7 +1264,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Certification Authority Policy Settings*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_CertAuthPolSet*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -1341,7 +1341,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Certificates*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_Certs*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -1418,7 +1418,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Certificate Templates*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_CertsTemplate*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -1495,7 +1495,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Component Services*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_ComponentServices*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -1572,7 +1572,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Computer Management*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_ComputerManagement*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -1649,7 +1649,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Connection Sharing (NAT)*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_ConnectionSharingNAT*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -1726,7 +1726,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *DCOM Configuration Extension*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_DCOMCFG*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -1803,7 +1803,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Distributed File System*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_DFS*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -1880,7 +1880,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *DHCP Relay Management*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_DHCPRelayMgmt*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -1957,7 +1957,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Device Manager*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_DeviceManager_1*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -2034,7 +2034,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Device Manager*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_DeviceManager_2*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -2111,7 +2111,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Disk Defragmenter*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_DiskDefrag*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -2188,7 +2188,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Disk Management*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_DiskMgmt*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -2265,7 +2265,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Enterprise PKI*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_EnterprisePKI*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -2342,7 +2342,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Event Viewer*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_EventViewer_1*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -2419,7 +2419,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Event Viewer (Windows Vista)*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_EventViewer_2*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -2496,7 +2496,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Event Viewer*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_EventViewer_3*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -2573,7 +2573,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Event Viewer (Windows Vista)*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_EventViewer_4*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -2651,7 +2651,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Event Viewer (Windows Vista)*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_EventViewer_2*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -2728,7 +2728,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *FAX Service*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_FAXService*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -2805,7 +2805,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Failover Clusters Manager*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_FailoverClusters*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -2882,7 +2882,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Folder Redirection*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_FolderRedirection_1*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Group Policy snap-in extensions*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -2959,7 +2959,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Folder Redirection*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_FolderRedirection_2*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Resultant Set of Policy snap-in extensions*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -3036,7 +3036,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *FrontPage Server Extensions*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_FrontPageExt*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -3113,7 +3113,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Group Policy Management*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_GroupPolicyManagementSnapIn*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -3190,7 +3190,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Group Policy Object Editor*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_GroupPolicySnapIn*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -3269,7 +3269,7 @@ When the Group Policy tab is inaccessible, it does not appear in the site, domai
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Group Policy tab for Active Directory Tools*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_GroupPolicyTab*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -3346,7 +3346,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Health Registration Authority (HRA)*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_HRA*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -3423,7 +3423,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Internet Authentication Service (IAS)*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_IAS*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -3500,7 +3500,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *IAS Logging*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_IASLogging*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -3577,7 +3577,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Internet Explorer Maintenance*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_IEMaintenance_1*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Group Policy snap-in extensions*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -3654,7 +3654,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Internet Explorer Maintenance*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_IEMaintenance_2*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Resultant Set of Policy snap-in extensions*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -3731,7 +3731,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *IGMP Routing*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_IGMPRouting*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -3808,7 +3808,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Internet Information Services*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_IIS*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -3885,7 +3885,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *IP Routing*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_IPRouting*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -3962,7 +3962,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *IP Security Policy Management*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_IPSecManage_GP*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Group Policy snap-in extensions*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -4039,7 +4039,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *IPX RIP Routing*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_IPXRIPRouting*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -4116,7 +4116,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *IPX Routing*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_IPXRouting*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -4193,7 +4193,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *IPX SAP Routing*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_IPXSAPRouting*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -4270,7 +4270,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Indexing Service*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_IndexingService*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -4347,7 +4347,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *IP Security Policy Management*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_IpSecManage*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -4424,7 +4424,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *IP Security Monitor*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_IpSecMonitor*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -4501,7 +4501,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Local Users and Groups*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_LocalUsersGroups*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -4578,7 +4578,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Logical and Mapped Drives*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_LogicalMappedDrives*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -4655,7 +4655,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Network Policy Server (NPS)*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_NPSUI*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -4732,7 +4732,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *NAP Client Configuration*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_NapSnap*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -4809,7 +4809,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *NAP Client Configuration*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_NapSnap_GP*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Group Policy snap-in extensions*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -4886,7 +4886,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *.Net Framework Configuration*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_Net_Framework*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -4963,7 +4963,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Online Responder*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_OCSP*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -5040,7 +5040,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *OSPF Routing*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_OSPFRouting*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -5117,7 +5117,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Performance Logs and Alerts*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_PerfLogsAlerts*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -5194,7 +5194,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Public Key Policies*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_PublicKey*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -5271,7 +5271,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *QoS Admission Control*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_QoSAdmission*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -5348,7 +5348,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *RAS Dialin - User Node*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_RAS_DialinUser*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -5425,7 +5425,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *RIP Routing*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_RIPRouting*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -5502,7 +5502,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Remote Installation Services*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_RIS*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Group Policy snap-in extensions*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -5579,7 +5579,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Routing and Remote Access*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_RRA*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -5656,7 +5656,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Removable Storage Management*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_RSM*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -5733,7 +5733,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Removable Storage*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_RemStore*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -5810,7 +5810,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Remote Access*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_RemoteAccess*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -5887,7 +5887,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Remote Desktops*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_RemoteDesktop*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -5964,7 +5964,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Resultant Set of Policy snap-in*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_ResultantSetOfPolicySnapIn*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -6041,7 +6041,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Routing*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_Routing*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -6118,7 +6118,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Security Configuration and Analysis*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_SCA*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -6195,7 +6195,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *SMTP Protocol*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_SMTPProtocol*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -6272,7 +6272,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *SNMP*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_SNMP*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -6349,7 +6349,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Scripts (Startup/Shutdown)*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_ScriptsMachine_1*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Group Policy snap-in extensions*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -6426,7 +6426,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Scripts (Startup/Shutdown)*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_ScriptsMachine_2*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Resultant Set of Policy snap-in extensions*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -6503,7 +6503,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Scripts (Logon/Logoff)*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_ScriptsUser_1*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Group Policy snap-in extensions*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -6580,7 +6580,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Scripts (Logon/Logoff)*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_ScriptsUser_2*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Resultant Set of Policy snap-in extensions*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -6657,7 +6657,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Security Settings*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_SecuritySettings_1*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Group Policy snap-in extensions*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -6734,7 +6734,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Security Settings*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_SecuritySettings_2*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Resultant Set of Policy snap-in extensions*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -6811,7 +6811,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Security Templates*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_SecurityTemplates*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -6888,7 +6888,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Send Console Message*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_SendConsoleMessage*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -6965,7 +6965,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Server Manager*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_ServerManager*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -7042,7 +7042,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Service Dependencies*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_ServiceDependencies*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -7119,7 +7119,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Services*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_Services*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -7196,7 +7196,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Shared Folders*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_SharedFolders*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -7273,7 +7273,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Shared Folders Ext*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_SharedFolders_Ext*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -7350,7 +7350,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Software Installation (Computers)*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_SoftwareInstalationComputers_1*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Group Policy snap-in extensions*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -7427,7 +7427,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Software Installation (Computers)*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_SoftwareInstalationComputers_2*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Resultant Set of Policy snap-in extensions*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -7504,7 +7504,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Software Installation (Users)*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_SoftwareInstallationUsers_1*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Group Policy snap-in extensions*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -7581,7 +7581,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Software Installation (Users)*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_SoftwareInstallationUsers_2*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Resultant Set of Policy snap-in extensions*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -7658,7 +7658,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *System Information*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_SysInfo*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -7735,7 +7735,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *System Properties*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_SysProp*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -7812,7 +7812,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *TPM Management*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_TPMManagement*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -7889,7 +7889,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Telephony*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_Telephony*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -7966,7 +7966,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Remote Desktop Services Configuration*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_TerminalServices*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -8043,7 +8043,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *WMI Control*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_WMI*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -8120,7 +8120,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Windows Firewall with Advanced Security*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_WindowsFirewall*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -8197,7 +8197,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Windows Firewall with Advanced Security*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_WindowsFirewall_GP*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Group Policy snap-in extensions*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -8274,7 +8274,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Wired Network (IEEE 802.3) Policies*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_WiredNetworkPolicy*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Group Policy snap-in extensions*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -8351,7 +8351,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Wireless Monitor*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_WirelessMon*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
@ -8428,7 +8428,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Wireless Network (IEEE 802.11) Policies*
|
||||
- GP name: *Restrict_Run*
|
||||
- GP name: *MMC_WirelessNetworkPolicy*
|
||||
- GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Group Policy snap-in extensions*
|
||||
- GP ADMX file name: *MMCSnapins.admx*
|
||||
|
||||
|
||||
@ -93,7 +93,7 @@ By default, this setting is Disabled. This setting does not affect whether users
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Block all consumer Microsoft account user authentication*
|
||||
- GP name: *DisableUserAuth*
|
||||
- GP name: *MicrosoftAccount_DisableUserAuth*
|
||||
- GP path: *Windows Components\Microsoft account*
|
||||
- GP ADMX file name: *MSAPolicy.admx*
|
||||
|
||||
|
||||
@ -122,7 +122,7 @@ You must configure this setting to have complete NCA functionality.
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Corporate Resources*
|
||||
- GP name: *Probe*
|
||||
- GP name: *CorporateResources*
|
||||
- GP path: *Network\DirectAccess Client Experience Settings*
|
||||
- GP ADMX file name: *nca.admx*
|
||||
|
||||
@ -187,7 +187,7 @@ Available in Windows 10 Insider Preview Build 20185. This policy setting specifi
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Custom Commands*
|
||||
- GP name: *CustomCommand*
|
||||
- GP name: *CustomCommands*
|
||||
- GP path: *Network\DirectAccess Client Experience Settings*
|
||||
- GP ADMX file name: *nca.admx*
|
||||
|
||||
@ -258,7 +258,7 @@ You must configure this setting to have complete NCA functionality.
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *IPsec Tunnel Endpoints*
|
||||
- GP name: *DTE*
|
||||
- GP name: *DTEs*
|
||||
- GP path: *Network\DirectAccess Client Experience Settings*
|
||||
- GP ADMX file name: *nca.admx*
|
||||
|
||||
@ -401,7 +401,7 @@ If this setting is not configured, users do not have Connect or Disconnect optio
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Prefer Local Names Allowed*
|
||||
- GP name: *NamePreferenceAllowed*
|
||||
- GP name: *LocalNamesOn*
|
||||
- GP path: *Network\DirectAccess Client Experience Settings*
|
||||
- GP ADMX file name: *nca.admx*
|
||||
|
||||
|
||||
@ -105,7 +105,7 @@ Available in Windows 10 Insider Preview Build 20185. This policy setting enable
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Specify corporate DNS probe host address*
|
||||
- GP name: *DnsProbeContent*
|
||||
- GP name: *NCSI_CorpDnsProbeContent*
|
||||
- GP path: *Network\Network Connectivity Status Indicator*
|
||||
- GP ADMX file name: *NCSI.admx*
|
||||
|
||||
@ -170,7 +170,7 @@ Available in Windows 10 Insider Preview Build 20185. This policy setting enables
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Specify corporate DNS probe host name*
|
||||
- GP name: *DnsProbeHost*
|
||||
- GP name: *NCSI_CorpDnsProbeHost*
|
||||
- GP path: *Network\Network Connectivity Status Indicator*
|
||||
- GP ADMX file name: *NCSI.admx*
|
||||
|
||||
@ -235,7 +235,7 @@ Available in Windows 10 Insider Preview Build 20185. This policy setting enables
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Specify corporate site prefix list*
|
||||
- GP name: *SitePrefixes*
|
||||
- GP name: *NCSI_CorpSitePrefixes*
|
||||
- GP path: *Network\Network Connectivity Status Indicator*
|
||||
- GP ADMX file name: *NCSI.admx*
|
||||
|
||||
@ -300,7 +300,7 @@ Available in Windows 10 Insider Preview Build 20185. This policy setting enables
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Specify corporate Website probe URL*
|
||||
- GP name: *WebProbeUrl*
|
||||
- GP name: *NCSI_CorpWebProbeUrl*
|
||||
- GP path: *Network\Network Connectivity Status Indicator*
|
||||
- GP ADMX file name: *NCSI.admx*
|
||||
|
||||
@ -368,7 +368,7 @@ Available in Windows 10 Insider Preview Build 20185. This policy setting enables
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Specify domain location determination URL*
|
||||
- GP name: *DomainLocationDeterminationUrl*
|
||||
- GP name: *NCSI_DomainLocationDeterminationUrl*
|
||||
- GP path: *Network\Network Connectivity Status Indicator*
|
||||
- GP ADMX file name: *NCSI.admx*
|
||||
|
||||
@ -433,7 +433,7 @@ Available in Windows 10 Insider Preview Build 20185. This policy setting enables
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Specify global DNS*
|
||||
- GP name: *UseGlobalDns*
|
||||
- GP name: *NCSI_GlobalDns*
|
||||
- GP path: *Network\Network Connectivity Status Indicator*
|
||||
- GP ADMX file name: *NCSI.admx*
|
||||
|
||||
@ -498,7 +498,7 @@ Available in Windows 10 Insider Preview Build 20185. This Policy setting enables
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Specify passive polling*
|
||||
- GP name: *DisablePassivePolling*
|
||||
- GP name: *NCSI_PassivePolling*
|
||||
- GP path: *Network\Network Connectivity Status Indicator*
|
||||
- GP ADMX file name: *NCSI.admx*
|
||||
|
||||
|
||||
@ -201,7 +201,7 @@ If you do not configure this policy setting, it is not applied to any DCs, and D
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Specify address lookup behavior for DC locator ping*
|
||||
- GP name: *AddressLookupOnPingBehavior*
|
||||
- GP name: *Netlogon_AddressLookupOnPingBehavior*
|
||||
- GP path: *System\Net Logon\DC Locator DNS Records*
|
||||
- GP ADMX file name: *Netlogon.admx*
|
||||
|
||||
@ -274,7 +274,7 @@ If you do not configure this policy setting, DC Locator APIs can return IPv4/IPv
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Return domain controller address type*
|
||||
- GP name: *AddressTypeReturned*
|
||||
- GP name: *Netlogon_AddressTypeReturned*
|
||||
- GP path: *System\Net Logon\DC Locator DNS Records*
|
||||
- GP ADMX file name: *Netlogon.admx*
|
||||
|
||||
@ -347,7 +347,7 @@ If you disable this policy setting, when the AllowSingleLabelDnsDomain policy is
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Use DNS name resolution when a single-label domain name is used, by appending different registered DNS suffixes, if the AllowSingleLabelDnsDomain setting is not enabled.*
|
||||
- GP name: *AllowDnsSuffixSearch*
|
||||
- GP name: *Netlogon_AllowDnsSuffixSearch*
|
||||
- GP path: *System\Net Logon\DC Locator DNS Records*
|
||||
- GP ADMX file name: *Netlogon.admx*
|
||||
|
||||
@ -422,7 +422,7 @@ If you do not configure this policy setting, Net Logon will not allow the negoti
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Allow cryptography algorithms compatible with Windows NT 4.0*
|
||||
- GP name: *AllowNT4Crypto*
|
||||
- GP name: *Netlogon_AllowNT4Crypto*
|
||||
- GP path: *System\Net Logon*
|
||||
- GP ADMX file name: *Netlogon.admx*
|
||||
|
||||
@ -497,7 +497,7 @@ If you do not configure this policy setting, it is not applied to any computers,
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Use DNS name resolution with a single-label domain name instead of NetBIOS name resolution to locate the DC*
|
||||
- GP name: *AllowSingleLabelDnsDomain*
|
||||
- GP name: *Netlogon_AllowSingleLabelDnsDomain*
|
||||
- GP path: *System\Net Logon\DC Locator DNS Records*
|
||||
- GP ADMX file name: *Netlogon.admx*
|
||||
|
||||
@ -570,7 +570,7 @@ If you do not configure this policy setting, it is not applied to any DCs, and D
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Use automated site coverage by the DC Locator DNS SRV Records*
|
||||
- GP name: *AutoSiteCoverage*
|
||||
- GP name: *Netlogon_AutoSiteCoverage*
|
||||
- GP path: *System\Net Logon\DC Locator DNS Records*
|
||||
- GP ADMX file name: *Netlogon.admx*
|
||||
|
||||
@ -646,7 +646,7 @@ If you disable this policy setting, the DC location algorithm can use NetBIOS-ba
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Do not use NetBIOS-based discovery for domain controller location when DNS-based discovery fails*
|
||||
- GP name: *AvoidFallbackNetbiosDiscovery*
|
||||
- GP name: *Netlogon_AvoidFallbackNetbiosDiscovery*
|
||||
- GP path: *System\Net Logon\DC Locator DNS Records*
|
||||
- GP ADMX file name: *Netlogon.admx*
|
||||
|
||||
@ -721,7 +721,7 @@ If you do not configure this policy setting, it is not applied to any DCs.
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Contact PDC on logon failure*
|
||||
- GP name: *AvoidPdcOnWan*
|
||||
- GP name: *Netlogon_AvoidPdcOnWan*
|
||||
- GP path: *System\Net Logon*
|
||||
- GP ADMX file name: *Netlogon.admx*
|
||||
|
||||
@ -799,7 +799,7 @@ If the value of this setting is less than the value specified in the NegativeCac
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Use initial DC discovery retry setting for background callers*
|
||||
- GP name: *BackgroundRetryInitialPeriod*
|
||||
- GP name: *Netlogon_BackgroundRetryInitialPeriod*
|
||||
- GP path: *System\Net Logon*
|
||||
- GP ADMX file name: *Netlogon.admx*
|
||||
|
||||
@ -879,7 +879,7 @@ If the value for this setting is too small and the DC is not available, the freq
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Use maximum DC discovery retry interval setting for background callers*
|
||||
- GP name: *BackgroundRetryMaximumPeriod*
|
||||
- GP name: *Netlogon_BackgroundRetryMaximumPeriod*
|
||||
- GP path: *System\Net Logon*
|
||||
- GP ADMX file name: *Netlogon.admx*
|
||||
|
||||
@ -951,7 +951,7 @@ The default value for this setting is to not quit retrying (0). The maximum valu
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Use final DC discovery retry setting for background callers*
|
||||
- GP name: *BackgroundRetryQuitTime*
|
||||
- GP name: *Netlogon_BackgroundRetryQuitTime*
|
||||
- GP path: *System\Net Logon*
|
||||
- GP ADMX file name: *Netlogon.admx*
|
||||
|
||||
@ -1018,7 +1018,7 @@ Available in Windows 10 Insider Preview Build 20185. This policy setting determi
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Use positive periodic DC cache refresh for background callers*
|
||||
- GP name: *BackgroundSuccessfulRefreshPeriod*
|
||||
- GP name: *Netlogon_BackgroundSuccessfulRefreshPeriod*
|
||||
- GP path: *System\Net Logon*
|
||||
- GP ADMX file name: *Netlogon.admx*
|
||||
|
||||
@ -1093,7 +1093,7 @@ If you disable this policy setting or do not configure it, the default behavior
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Specify log file debug output level*
|
||||
- GP name: *dbFlag*
|
||||
- GP name: *Netlogon_DebugFlag*
|
||||
- GP path: *System\Net Logon*
|
||||
- GP ADMX file name: *Netlogon.admx*
|
||||
|
||||
@ -1192,7 +1192,7 @@ If you do not configure this policy setting, DCs use their local configuration.
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Specify DC Locator DNS records not registered by the DCs*
|
||||
- GP name: *DnsAvoidRegisterRecords*
|
||||
- GP name: *Netlogon_DnsAvoidRegisterRecords*
|
||||
- GP path: *System\Net Logon\DC Locator DNS Records*
|
||||
- GP ADMX file name: *Netlogon.admx*
|
||||
|
||||
@ -1268,7 +1268,7 @@ If you do not configure this policy setting, it is not applied to any DCs, and D
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Specify Refresh Interval of the DC Locator DNS records*
|
||||
- GP name: *DnsRefreshInterval*
|
||||
- GP name: *Netlogon_DnsRefreshInterval*
|
||||
- GP path: *System\Net Logon\DC Locator DNS Records*
|
||||
- GP ADMX file name: *Netlogon.admx*
|
||||
|
||||
@ -1344,7 +1344,7 @@ A reboot is not required for changes to this setting to take effect.
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Use lowercase DNS host names when registering domain controller SRV records*
|
||||
- GP name: *DnsSrvRecordUseLowerCaseHostNames*
|
||||
- GP name: *Netlogon_DnsSrvRecordUseLowerCaseHostNames*
|
||||
- GP path: *System\Net Logon\DC Locator DNS Records*
|
||||
- GP ADMX file name: *Netlogon.admx*
|
||||
|
||||
@ -1414,7 +1414,7 @@ If you do not configure this policy setting, it is not applied to any DCs, and D
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Set TTL in the DC Locator DNS Records*
|
||||
- GP name: *DnsTtl*
|
||||
- GP name: *Netlogon_DnsTtl*
|
||||
- GP path: *System\Net Logon\DC Locator DNS Records*
|
||||
- GP ADMX file name: *Netlogon.admx*
|
||||
|
||||
@ -1485,7 +1485,7 @@ If you do not configure this policy setting, it is not applied to any computers,
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Specify expected dial-up delay on logon*
|
||||
- GP name: *ExpectedDialupDelay*
|
||||
- GP name: *Netlogon_ExpectedDialupDelay*
|
||||
- GP path: *System\Net Logon*
|
||||
- GP ADMX file name: *Netlogon.admx*
|
||||
|
||||
@ -1560,7 +1560,7 @@ If you do not configure this policy setting, Force Rediscovery will be used by d
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Force Rediscovery Interval*
|
||||
- GP name: *ForceRediscoveryInterval*
|
||||
- GP name: *Netlogon_ForceRediscoveryInterval*
|
||||
- GP path: *System\Net Logon\DC Locator DNS Records*
|
||||
- GP ADMX file name: *Netlogon.admx*
|
||||
|
||||
@ -1633,7 +1633,7 @@ If you do not configure this policy setting, it is not applied to any GCs, and G
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Specify sites covered by the GC Locator DNS SRV Records*
|
||||
- GP name: *GcSiteCoverage*
|
||||
- GP name: *Netlogon_GcSiteCoverage*
|
||||
- GP path: *System\Net Logon\DC Locator DNS Records*
|
||||
- GP ADMX file name: *Netlogon.admx*
|
||||
|
||||
@ -1709,7 +1709,7 @@ If you disable or do not configure this policy setting, this DC processes incomi
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Do not process incoming mailslot messages used for domain controller location based on NetBIOS domain names*
|
||||
- GP name: *IgnoreIncomingMailslotMessages*
|
||||
- GP name: *Netlogon_IgnoreIncomingMailslotMessages*
|
||||
- GP path: *System\Net Logon\DC Locator DNS Records*
|
||||
- GP ADMX file name: *Netlogon.admx*
|
||||
|
||||
@ -1782,7 +1782,7 @@ If you do not configure this policy setting, it is not applied to any DCs, and D
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Set Priority in the DC Locator DNS SRV records*
|
||||
- GP name: *LdapSrvPriority*
|
||||
- GP name: *Netlogon_LdapSrvPriority*
|
||||
- GP path: *System\Net Logon\DC Locator DNS Records*
|
||||
- GP ADMX file name: *Netlogon.admx*
|
||||
|
||||
@ -1855,7 +1855,7 @@ If you do not configure this policy setting, it is not applied to any DCs, and D
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Set Weight in the DC Locator DNS SRV records*
|
||||
- GP name: *LdapSrvWeight*
|
||||
- GP name: *Netlogon_LdapSrvWeight*
|
||||
- GP path: *System\Net Logon\DC Locator DNS Records*
|
||||
- GP ADMX file name: *Netlogon.admx*
|
||||
|
||||
@ -1926,7 +1926,7 @@ If you disable or do not configure this policy setting, the default behavior occ
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Specify maximum log file size*
|
||||
- GP name: *MaximumLogFileSize*
|
||||
- GP name: *Netlogon_MaximumLogFileSize*
|
||||
- GP path: *System\Net Logon*
|
||||
- GP ADMX file name: *Netlogon.admx*
|
||||
|
||||
@ -1999,7 +1999,7 @@ If you do not configure this policy setting, it is not applied to any DCs, and D
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Specify sites covered by the application directory partition DC Locator DNS SRV records*
|
||||
- GP name: *NdncSiteCoverage*
|
||||
- GP name: *Netlogon_NdncSiteCoverage*
|
||||
- GP path: *System\Net Logon\DC Locator DNS Records*
|
||||
- GP ADMX file name: *Netlogon.admx*
|
||||
|
||||
@ -2071,7 +2071,7 @@ The default value for this setting is 45 seconds. The maximum value for this set
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Specify negative DC Discovery cache setting*
|
||||
- GP name: *NegativeCachePeriod*
|
||||
- GP name: *Netlogon_NegativeCachePeriod*
|
||||
- GP path: *System\Net Logon*
|
||||
- GP ADMX file name: *Netlogon.admx*
|
||||
|
||||
@ -2149,7 +2149,7 @@ If you enable this policy setting, domain administrators should ensure that the
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Set Netlogon share compatibility*
|
||||
- GP name: *AllowExclusiveScriptsShareAccess*
|
||||
- GP name: *Netlogon_NetlogonShareCompatibilityMode*
|
||||
- GP path: *System\Net Logon*
|
||||
- GP ADMX file name: *Netlogon.admx*
|
||||
|
||||
@ -2218,7 +2218,7 @@ The default value for this setting is 30 minutes (1800). The maximum value for t
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Specify positive periodic DC Cache refresh for non-background callers*
|
||||
- GP name: *NonBackgroundSuccessfulRefreshPeriod*
|
||||
- GP name: *Netlogon_NonBackgroundSuccessfulRefreshPeriod*
|
||||
- GP path: *System\Net Logon*
|
||||
- GP ADMX file name: *Netlogon.admx*
|
||||
|
||||
@ -2296,7 +2296,7 @@ If you do not configure this policy setting, it is not applied to any computers,
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Use urgent mode when pinging domain controllers*
|
||||
- GP name: *PingUrgencyMode*
|
||||
- GP name: *Netlogon_PingUrgencyMode*
|
||||
- GP path: *System\Net Logon*
|
||||
- GP ADMX file name: *Netlogon.admx*
|
||||
|
||||
@ -2373,7 +2373,7 @@ To enable the setting, click Enabled, and then specify the interval in seconds.
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Set scavenge interval*
|
||||
- GP name: *ScavengeInterval*
|
||||
- GP name: *Netlogon_ScavengeInterval*
|
||||
- GP path: *System\Net Logon*
|
||||
- GP ADMX file name: *Netlogon.admx*
|
||||
|
||||
@ -2446,7 +2446,7 @@ If you do not configure this policy setting, it is not applied to any DCs, and D
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Specify sites covered by the DC Locator DNS SRV records*
|
||||
- GP name: *SiteCoverage*
|
||||
- GP name: *Netlogon_SiteCoverage*
|
||||
- GP path: *System\Net Logon\DC Locator DNS Records*
|
||||
- GP ADMX file name: *Netlogon.admx*
|
||||
|
||||
@ -2519,7 +2519,7 @@ If you do not configure this policy setting, it is not applied to any computers,
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Specify site name*
|
||||
- GP name: *SiteName*
|
||||
- GP name: *Netlogon_SiteName*
|
||||
- GP path: *System\Net Logon*
|
||||
- GP ADMX file name: *Netlogon.admx*
|
||||
|
||||
@ -2597,7 +2597,7 @@ If you enable this policy setting, domain administrators should ensure that the
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Set SYSVOL share compatibility*
|
||||
- GP name: *AllowExclusiveSysvolShareAccess*
|
||||
- GP name: *Netlogon_SysvolShareCompatibilityMode*
|
||||
- GP path: *System\Net Logon*
|
||||
- GP ADMX file name: *Netlogon.admx*
|
||||
|
||||
@ -2672,7 +2672,7 @@ If you do not configure this policy setting, Try Next Closest Site DC Location w
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Try Next Closest Site*
|
||||
- GP name: *TryNextClosestSite*
|
||||
- GP name: *Netlogon_TryNextClosestSite*
|
||||
- GP path: *System\Net Logon\DC Locator DNS Records*
|
||||
- GP ADMX file name: *Netlogon.admx*
|
||||
|
||||
@ -2745,7 +2745,7 @@ If you do not configure this policy setting, it is not applied to any DCs, and D
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Specify dynamic registration of the DC Locator DNS Records*
|
||||
- GP name: *UseDynamicDns*
|
||||
- GP name: *Netlogon_UseDynamicDns*
|
||||
- GP path: *System\Net Logon\DC Locator DNS Records*
|
||||
- GP ADMX file name: *Netlogon.admx*
|
||||
|
||||
|
||||
@ -228,7 +228,7 @@ If you disable this setting or do not configure it, the system asks users whethe
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Subfolders always available offline*
|
||||
- GP name: *AlwaysPinSubFolders*
|
||||
- GP name: *Pol_AlwaysPinSubFolders*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -302,7 +302,7 @@ If you do not configure this policy setting, no files or folders are made availa
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Specify administratively assigned Offline Files*
|
||||
- GP name: *AssignedOfflineFolders*
|
||||
- GP name: *Pol_AssignedOfflineFiles_1*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -376,7 +376,7 @@ If you do not configure this policy setting, no files or folders are made availa
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Specify administratively assigned Offline Files*
|
||||
- GP name: *AssignedOfflineFolders*
|
||||
- GP name: *Pol_AssignedOfflineFiles_2*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -447,7 +447,7 @@ If you disable or do not configure this policy setting, Windows performs a backg
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Configure Background Sync*
|
||||
- GP name: *BackgroundSyncEnabled*
|
||||
- GP name: *Pol_BackgroundSyncSettings*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -528,7 +528,7 @@ This setting replaces the Default Cache Size setting used by pre-Windows Vista s
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Limit disk space used by Offline Files*
|
||||
- GP name: *CacheQuotaLimitUnpinned*
|
||||
- GP name: *Pol_CacheSize*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -612,7 +612,7 @@ Also, see the "Non-default server disconnect actions" setting.
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Action on server disconnect*
|
||||
- GP name: *GoOfflineAction*
|
||||
- GP name: *Pol_CustomGoOfflineActions_1*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -696,7 +696,7 @@ Also, see the "Non-default server disconnect actions" setting.
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Action on server disconnect*
|
||||
- GP name: *GoOfflineAction*
|
||||
- GP name: *Pol_CustomGoOfflineActions_2*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -776,7 +776,7 @@ If you do not configure this setting, disk space for automatically cached files
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Default cache size*
|
||||
- GP name: *DefCacheSize*
|
||||
- GP name: *Pol_DefCacheSize*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -850,7 +850,7 @@ If you do not configure this policy setting, Offline Files is enabled on Windows
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Allow or Disallow use of the Offline Files feature*
|
||||
- GP name: *Enabled*
|
||||
- GP name: *Pol_Enabled*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -927,7 +927,7 @@ This setting is applied at user logon. If this setting is changed after user log
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Encrypt the Offline Files cache*
|
||||
- GP name: *EncryptCache*
|
||||
- GP name: *Pol_EncryptOfflineFiles*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -1007,7 +1007,7 @@ To use this setting, in the "Enter" box, select the number corresponding to the
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Event logging level*
|
||||
- GP name: *EventLoggingLevel*
|
||||
- GP name: *Pol_EventLoggingLevel_1*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -1087,7 +1087,7 @@ To use this setting, in the "Enter" box, select the number corresponding to the
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Event logging level*
|
||||
- GP name: *EventLoggingLevel*
|
||||
- GP name: *Pol_EventLoggingLevel_2*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -1156,7 +1156,7 @@ If you disable or do not configure this policy setting, a user can create a file
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Enable file screens*
|
||||
- GP name: *ExcludedFileTypes*
|
||||
- GP name: *Pol_ExclusionListSettings*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -1230,7 +1230,7 @@ To use this setting, type the file name extension in the "Extensions" box. To ty
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Files not cached*
|
||||
- GP name: *ExcludeExtensions*
|
||||
- GP name: *Pol_ExtExclusionList*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -1314,7 +1314,7 @@ Also, see the "Non-default server disconnect actions" setting.
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Action on server disconnect*
|
||||
- GP name: *GoOfflineAction*
|
||||
- GP name: *Pol_GoOfflineAction_1*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -1398,7 +1398,7 @@ Also, see the "Non-default server disconnect actions" setting.
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Action on server disconnect*
|
||||
- GP name: *GoOfflineAction*
|
||||
- GP name: *Pol_GoOfflineAction_2*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -1472,7 +1472,7 @@ This setting appears in the Computer Configuration and User Configuration folder
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Prevent use of Offline Files folder*
|
||||
- GP name: *NoCacheViewer*
|
||||
- GP name: *Pol_NoCacheViewer_1*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -1546,7 +1546,7 @@ This setting appears in the Computer Configuration and User Configuration folder
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Prevent use of Offline Files folder*
|
||||
- GP name: *NoCacheViewer*
|
||||
- GP name: *Pol_NoCacheViewer_2*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -1620,7 +1620,7 @@ This setting appears in the Computer Configuration and User Configuration folder
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Prohibit user configuration of Offline Files*
|
||||
- GP name: *NoConfigCache*
|
||||
- GP name: *Pol_NoConfigCache_1*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -1694,7 +1694,7 @@ This setting appears in the Computer Configuration and User Configuration folder
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Prohibit user configuration of Offline Files*
|
||||
- GP name: *NoConfigCache*
|
||||
- GP name: *Pol_NoConfigCache_2*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -1767,7 +1767,7 @@ If you disable or do not configure this policy setting, users can manually speci
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Remove "Make Available Offline" command*
|
||||
- GP name: *NoMakeAvailableOffline*
|
||||
- GP name: *Pol_NoMakeAvailableOffline_1*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -1840,7 +1840,7 @@ If you disable or do not configure this policy setting, users can manually speci
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Remove "Make Available Offline" command*
|
||||
- GP name: *NoMakeAvailableOffline*
|
||||
- GP name: *Pol_NoMakeAvailableOffline_2*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -1917,7 +1917,7 @@ If you do not configure this policy setting, the "Make Available Offline" comman
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Remove "Make Available Offline" for these files and folders*
|
||||
- GP name: *NoMakeAvailableOfflineList*
|
||||
- GP name: *Pol_NoPinFiles_1*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -1994,7 +1994,7 @@ If you do not configure this policy setting, the "Make Available Offline" comman
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Remove "Make Available Offline" for these files and folders*
|
||||
- GP name: *NoMakeAvailableOfflineList*
|
||||
- GP name: *Pol_NoPinFiles_2*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -2074,7 +2074,7 @@ This setting appears in the Computer Configuration and User Configuration folder
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Turn off reminder balloons*
|
||||
- GP name: *NoReminders*
|
||||
- GP name: *Pol_NoReminders_1*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -2154,7 +2154,7 @@ This setting appears in the Computer Configuration and User Configuration folder
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Turn off reminder balloons*
|
||||
- GP name: *NoReminders*
|
||||
- GP name: *Pol_NoReminders_2*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -2227,7 +2227,7 @@ If you disable or do not configure this policy setting, remote files will be not
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Enable Transparent Caching*
|
||||
- GP name: *OnlineCachingLatencyThreshold*
|
||||
- GP name: *Pol_OnlineCachingSettings*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -2298,7 +2298,7 @@ If you disable this setting or do not configure it, the system asks users whethe
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Subfolders always available offline*
|
||||
- GP name: *AlwaysPinSubFolders*
|
||||
- GP name: *Pol_AlwaysPinSubFolders*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -2370,7 +2370,7 @@ If you disable this setting or do not configure it, automatically and manually c
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *At logoff, delete local copy of user’s offline files*
|
||||
- GP name: *PurgeOnlyAutoCacheAtLogoff*
|
||||
- GP name: *Pol_PurgeAtLogoff*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -2439,7 +2439,7 @@ If you disable this policy setting, all administratively assigned folders are sy
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Turn on economical application of administratively assigned Offline Files*
|
||||
- GP name: *EconomicalAdminPinning*
|
||||
- GP name: *Pol_QuickAdimPin*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -2513,7 +2513,7 @@ This setting appears in the Computer Configuration and User Configuration folder
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Reminder balloon frequency*
|
||||
- GP name: *ReminderFreqMinutes*
|
||||
- GP name: *Pol_ReminderFreq_1*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -2587,7 +2587,7 @@ This setting appears in the Computer Configuration and User Configuration folder
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Reminder balloon frequency*
|
||||
- GP name: *ReminderFreqMinutes*
|
||||
- GP name: *Pol_ReminderFreq_2*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -2656,7 +2656,7 @@ This setting appears in the Computer Configuration and User Configuration folder
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Initial reminder balloon lifetime*
|
||||
- GP name: *InitialBalloonTimeoutSeconds*
|
||||
- GP name: *Pol_ReminderInitTimeout_1*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -2725,7 +2725,7 @@ This setting appears in the Computer Configuration and User Configuration folder
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Initial reminder balloon lifetime*
|
||||
- GP name: *InitialBalloonTimeoutSeconds*
|
||||
- GP name: *Pol_ReminderInitTimeout_2*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -2794,7 +2794,7 @@ This setting appears in the Computer Configuration and User Configuration folder
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Reminder balloon lifetime*
|
||||
- GP name: *ReminderBalloonTimeoutSeconds*
|
||||
- GP name: *Pol_ReminderTimeout_1*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -2863,7 +2863,7 @@ This setting appears in the Computer Configuration and User Configuration folder
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Reminder balloon lifetime*
|
||||
- GP name: *ReminderBalloonTimeoutSeconds*
|
||||
- GP name: *Pol_ReminderTimeout_2*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -2942,7 +2942,7 @@ If you disable this policy setting, computers will not use the slow-link mode.
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Configure slow-link mode*
|
||||
- GP name: *SlowLinkEnabled*
|
||||
- GP name: *Pol_SlowLinkSettings*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -3016,7 +3016,7 @@ If this setting is disabled or not configured, the default threshold value of 64
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Configure Slow link speed*
|
||||
- GP name: *SlowLinkSpeed*
|
||||
- GP name: *Pol_SlowLinkSpeed*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -3094,7 +3094,7 @@ This setting appears in the Computer Configuration and User Configuration folder
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Synchronize all offline files before logging off*
|
||||
- GP name: *SyncAtLogoff*
|
||||
- GP name: *Pol_SyncAtLogoff_1*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -3172,7 +3172,7 @@ This setting appears in the Computer Configuration and User Configuration folder
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Synchronize all offline files before logging off*
|
||||
- GP name: *SyncAtLogoff*
|
||||
- GP name: *Pol_SyncAtLogoff_2*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -3250,7 +3250,7 @@ This setting appears in the Computer Configuration and User Configuration folder
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Synchronize all offline files when logging on*
|
||||
- GP name: *SyncAtLogon*
|
||||
- GP name: *Pol_SyncAtLogon_1*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -3330,7 +3330,7 @@ This setting appears in the Computer Configuration and User Configuration folder
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Synchronize all offline files when logging on*
|
||||
- GP name: *SyncAtLogon*
|
||||
- GP name: *Pol_SyncAtLogon_2*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -3402,7 +3402,7 @@ If you disable or do not configuring this setting, files are not synchronized wh
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Synchronize offline files before suspend*
|
||||
- GP name: *SyncAtSuspend*
|
||||
- GP name: *Pol_SyncAtSuspend_1*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -3474,7 +3474,7 @@ If you disable or do not configuring this setting, files are not synchronized wh
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Synchronize offline files before suspend*
|
||||
- GP name: *SyncAtSuspend*
|
||||
- GP name: *Pol_SyncAtSuspend_2*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -3543,7 +3543,7 @@ If this setting is disabled or not configured, synchronization will not run in t
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Enable file synchronization on costed networks*
|
||||
- GP name: *SyncEnabledForCostedNetwork*
|
||||
- GP name: *Pol_SyncOnCostedNetwork*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -3612,7 +3612,7 @@ If you disable or do not configure this policy setting, the "Work offline" comma
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Remove "Work offline" command*
|
||||
- GP name: *WorkOfflineDisabled*
|
||||
- GP name: *Pol_WorkOfflineDisabled_1*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
@ -3681,7 +3681,7 @@ If you disable or do not configure this policy setting, the "Work offline" comma
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Remove "Work offline" command*
|
||||
- GP name: *WorkOfflineDisabled*
|
||||
- GP name: *Pol_WorkOfflineDisabled_2*
|
||||
- GP path: *Network\Offline Files*
|
||||
- GP ADMX file name: *OfflineFiles.admx*
|
||||
|
||||
|
||||
@ -125,7 +125,7 @@ Select one of the following:
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Turn on BranchCache*
|
||||
- GP name: *Enable*
|
||||
- GP name: *EnableWindowsBranchCache*
|
||||
- GP path: *Network\BranchCache*
|
||||
- GP ADMX file name: *PeerToPeerCaching.admx*
|
||||
|
||||
@ -203,7 +203,7 @@ Select one of the following:
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Set BranchCache Distributed Cache mode*
|
||||
- GP name: *Enable*
|
||||
- GP name: *EnableWindowsBranchCache_Distributed*
|
||||
- GP path: *Network\BranchCache*
|
||||
- GP ADMX file name: *PeerToPeerCaching.admx*
|
||||
|
||||
@ -287,7 +287,7 @@ Hosted cache clients must trust the server certificate that is issued to the hos
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Set BranchCache Hosted Cache mode*
|
||||
- GP name: *Location*
|
||||
- GP name: *EnableWindowsBranchCache_Hosted*
|
||||
- GP path: *Network\BranchCache*
|
||||
- GP ADMX file name: *PeerToPeerCaching.admx*
|
||||
|
||||
@ -374,7 +374,7 @@ Select one of the following:
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Enable Automatic Hosted Cache Discovery by Service Connection Point*
|
||||
- GP name: *SCPDiscoveryEnabled*
|
||||
- GP name: *EnableWindowsBranchCache_HostedCacheDiscovery*
|
||||
- GP path: *Network\BranchCache*
|
||||
- GP ADMX file name: *PeerToPeerCaching.admx*
|
||||
|
||||
@ -457,7 +457,7 @@ In circumstances where this setting is enabled, you can also select and configur
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Configure Hosted Cache Servers*
|
||||
- GP name: *MultipleServers*
|
||||
- GP name: *EnableWindowsBranchCache_HostedMultipleServers*
|
||||
- GP path: *Network\BranchCache*
|
||||
- GP ADMX file name: *PeerToPeerCaching.admx*
|
||||
|
||||
@ -534,7 +534,7 @@ In circumstances where this policy setting is enabled, you can also select and c
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Configure BranchCache for network files*
|
||||
- GP name: *PeerCachingLatencyThreshold*
|
||||
- GP name: *EnableWindowsBranchCache_SMB*
|
||||
- GP path: *Network\BranchCache*
|
||||
- GP ADMX file name: *PeerToPeerCaching.admx*
|
||||
|
||||
@ -618,7 +618,7 @@ In circumstances where this setting is enabled, you can also select and configur
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Set percentage of disk space used for client computer cache*
|
||||
- GP name: *SizePercent*
|
||||
- GP name: *SetCachePercent*
|
||||
- GP path: *Network\BranchCache*
|
||||
- GP ADMX file name: *PeerToPeerCaching.admx*
|
||||
|
||||
@ -699,7 +699,7 @@ In circumstances where this setting is enabled, you can also select and configur
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Set age for segments in the data cache*
|
||||
- GP name: *SegmentTTL*
|
||||
- GP name: *SetDataCacheEntryMaxAge*
|
||||
- GP path: *Network\BranchCache*
|
||||
- GP ADMX file name: *PeerToPeerCaching.admx*
|
||||
|
||||
@ -783,7 +783,7 @@ Select from the following versions
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Configure Client BranchCache Version Support*
|
||||
- GP name: *PreferredContentInformationVersion*
|
||||
- GP name: *SetDowngrading*
|
||||
- GP path: *Network\BranchCache*
|
||||
- GP ADMX file name: *PeerToPeerCaching.admx*
|
||||
|
||||
|
||||
@ -108,7 +108,7 @@ This policy setting will only take effect when the Diagnostic Policy Service is
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Configure Scenario Execution Level*
|
||||
- GP name: *ScenarioExecutionEnabled*
|
||||
- GP name: *WdiScenarioExecutionPolicy_1*
|
||||
- GP path: *System\Troubleshooting and Diagnostics\Windows Boot Performance Diagnostics*
|
||||
- GP ADMX file name: *PerformanceDiagnostics.admx*
|
||||
|
||||
@ -185,7 +185,7 @@ This policy setting will only take effect when the Diagnostic Policy Service is
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Configure Scenario Execution Level*
|
||||
- GP name: *ScenarioExecutionEnabled*
|
||||
- GP name: *WdiScenarioExecutionPolicy_2*
|
||||
- GP path: *System\Troubleshooting and Diagnostics\Windows System Responsiveness Performance Diagnostics*
|
||||
- GP ADMX file name: *PerformanceDiagnostics.admx*
|
||||
|
||||
@ -262,7 +262,7 @@ This policy setting will only take effect when the Diagnostic Policy Service is
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Configure Scenario Execution Level*
|
||||
- GP name: *ScenarioExecutionEnabled*
|
||||
- GP name: *WdiScenarioExecutionPolicy_3*
|
||||
- GP path: *System\Troubleshooting and Diagnostics\Windows Shutdown Performance Diagnostics*
|
||||
- GP ADMX file name: *PerformanceDiagnostics.admx*
|
||||
|
||||
@ -339,7 +339,7 @@ This policy setting will only take effect when the Diagnostic Policy Service is
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Configure Scenario Execution Level*
|
||||
- GP name: *ScenarioExecutionEnabled*
|
||||
- GP name: *WdiScenarioExecutionPolicy_4*
|
||||
- GP path: *System\Troubleshooting and Diagnostics\Windows Standby/Resume Performance Diagnostics*
|
||||
- GP ADMX file name: *PerformanceDiagnostics.admx*
|
||||
|
||||
|
||||
@ -105,7 +105,7 @@ If you do not configure this policy setting, the Persistent System Timestamp is
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Enable Persistent Time Stamp*
|
||||
- GP name: *TimeStampEnabled*
|
||||
- GP name: *EE_EnablePersistentTimeStamp*
|
||||
- GP path: *System*
|
||||
- GP ADMX file name: *Reliability.admx*
|
||||
|
||||
@ -180,7 +180,7 @@ Also see the "Configure Error Reporting" policy setting.
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Report unplanned shutdown events*
|
||||
- GP name: *IncludeShutdownErrs*
|
||||
- GP name: *PCH_ReportShutdownEvents*
|
||||
- GP path: *Windows Components\Windows Error Reporting\Advanced Error Reporting Settings*
|
||||
- GP ADMX file name: *Reliability.admx*
|
||||
|
||||
@ -258,7 +258,7 @@ If you do not configure this policy setting, the default behavior for the System
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Activate Shutdown Event Tracker System State Data feature*
|
||||
- GP name: *SnapShot*
|
||||
- GP name: *ShutdownEventTrackerStateFile*
|
||||
- GP path: *System*
|
||||
- GP ADMX file name: *Reliability.admx*
|
||||
|
||||
@ -338,7 +338,7 @@ If you do not configure this policy setting, the default behavior for the Shutdo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Display Shutdown Event Tracker*
|
||||
- GP name: *ShutdownReasonOn*
|
||||
- GP name: *ShutdownReason*
|
||||
- GP path: *System*
|
||||
- GP ADMX file name: *Reliability.admx*
|
||||
|
||||
|
||||
@ -124,7 +124,7 @@ If you disable or do not configure this policy setting, user account cross-fores
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Allow logon scripts when NetBIOS or WINS is disabled*
|
||||
- GP name: *Allow-LogonScript-NetbiosDisabled*
|
||||
- GP name: *Allow_Logon_Script_NetbiosDisabled*
|
||||
- GP path: *System\Scripts*
|
||||
- GP ADMX file name: *Scripts.admx*
|
||||
|
||||
@ -199,7 +199,7 @@ If you disable or do not configure this setting the system lets the combined set
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Specify maximum wait time for Group Policy scripts*
|
||||
- GP name: *MaxGPOScriptWait*
|
||||
- GP name: *MaxGPOScriptWaitPolicy*
|
||||
- GP path: *System\Scripts*
|
||||
- GP ADMX file name: *Scripts.admx*
|
||||
|
||||
@ -291,7 +291,7 @@ Within GPO C: C.cmd, C.ps1
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Run Windows PowerShell scripts first at computer startup, shutdown*
|
||||
- GP name: *RunComputerPSScriptsFirst*
|
||||
- GP name: *Run_Computer_PS_Scripts_First*
|
||||
- GP path: *System\Scripts*
|
||||
- GP ADMX file name: *Scripts.admx*
|
||||
|
||||
@ -364,7 +364,7 @@ Also, see the "Run Logon Scripts Visible" setting.
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Run legacy logon scripts hidden*
|
||||
- GP name: *HideLegacyLogonScripts*
|
||||
- GP name: *Run_Legacy_Logon_Script_Hidden*
|
||||
- GP path: *System\Scripts*
|
||||
- GP ADMX file name: *Scripts.admx*
|
||||
|
||||
@ -435,7 +435,7 @@ If you disable or do not configure this policy setting, the instructions are sup
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Display instructions in logoff scripts as they run*
|
||||
- GP name: *HideLogoffScripts*
|
||||
- GP name: *Run_Logoff_Script_Visible*
|
||||
- GP path: *System\Scripts*
|
||||
- GP ADMX file name: *Scripts.admx*
|
||||
|
||||
@ -506,7 +506,7 @@ This policy setting appears in the Computer Configuration and User Configuration
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Run logon scripts synchronously*
|
||||
- GP name: *RunLogonScriptSync*
|
||||
- GP name: *Run_Logon_Script_Sync_1*
|
||||
- GP path: *System\Scripts*
|
||||
- GP ADMX file name: *Scripts.admx*
|
||||
|
||||
@ -577,7 +577,7 @@ This policy setting appears in the Computer Configuration and User Configuration
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Run logon scripts synchronously*
|
||||
- GP name: *RunLogonScriptSync*
|
||||
- GP name: *Run_Logon_Script_Sync_2*
|
||||
- GP path: *System\Scripts*
|
||||
- GP ADMX file name: *Scripts.admx*
|
||||
|
||||
@ -648,7 +648,7 @@ If you disable or do not configure this policy setting, the instructions are sup
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Display instructions in logon scripts as they run*
|
||||
- GP name: *HideLogonScripts*
|
||||
- GP name: *Run_Logon_Script_Visible*
|
||||
- GP path: *System\Scripts*
|
||||
- GP ADMX file name: *Scripts.admx*
|
||||
|
||||
@ -719,7 +719,7 @@ If you disable or do not configure this policy setting, the instructions are sup
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Display instructions in shutdown scripts as they run*
|
||||
- GP name: *HideShutdownScripts*
|
||||
- GP name: *Run_Shutdown_Script_Visible*
|
||||
- GP path: *System\Scripts*
|
||||
- GP ADMX file name: *Scripts.admx*
|
||||
|
||||
@ -793,7 +793,7 @@ If you disable or do not configure this policy setting, a startup cannot run unt
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Run startup scripts asynchronously*
|
||||
- GP name: *RunStartupScriptSync*
|
||||
- GP name: *Run_Startup_Script_Sync*
|
||||
- GP path: *System\Scripts*
|
||||
- GP ADMX file name: *Scripts.admx*
|
||||
|
||||
@ -867,7 +867,7 @@ If you disable or do not configure this policy setting, the instructions are sup
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Display instructions in startup scripts as they run*
|
||||
- GP name: *HideStartupScripts*
|
||||
- GP name: *Run_Startup_Script_Visible*
|
||||
- GP path: *System\Scripts*
|
||||
- GP ADMX file name: *Scripts.admx*
|
||||
|
||||
@ -962,7 +962,7 @@ This policy setting appears in the Computer Configuration and User Configuration
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Run Windows PowerShell scripts first at user logon, logoff*
|
||||
- GP name: *RunUserPSScriptsFirst*
|
||||
- GP name: *Run_User_PS_Scripts_First*
|
||||
- GP path: *System\Scripts*
|
||||
- GP ADMX file name: *Scripts.admx*
|
||||
|
||||
|
||||
@ -97,7 +97,7 @@ If you disable this policy setting, users can only access and search troubleshoo
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Troubleshooting: Allow users to access online troubleshooting content on Microsoft servers from the Troubleshooting Control Panel (via the Windows Online Troubleshooting Service - WOTS)*
|
||||
- GP name: *EnableQueryRemoteServer*
|
||||
- GP name: *BetterWhenConnected*
|
||||
- GP path: *System\Troubleshooting and Diagnostics\Scripted Diagnostics*
|
||||
- GP ADMX file name: *sdiageng.admx*
|
||||
|
||||
@ -168,7 +168,7 @@ Note that this setting also controls a user's ability to launch standalone troub
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Troubleshooting: Allow users to access and run Troubleshooting Wizards*
|
||||
- GP name: *EnableDiagnostics*
|
||||
- GP name: *ScriptedDiagnosticsExecutionPolicy*
|
||||
- GP path: *System\Troubleshooting and Diagnostics\Scripted Diagnostics*
|
||||
- GP ADMX file name: *sdiageng.admx*
|
||||
|
||||
@ -237,7 +237,7 @@ If you disable or do not configure this policy setting, the scripted diagnostics
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Configure Security Policy for Scripted Diagnostics*
|
||||
- GP name: *ValidateTrust*
|
||||
- GP name: *ScriptedDiagnosticsSecurityPolicy*
|
||||
- GP path: *System\Troubleshooting and Diagnostics\Scripted Diagnostics*
|
||||
- GP ADMX file name: *sdiageng.admx*
|
||||
|
||||
|
||||
@ -103,7 +103,7 @@ In Windows Vista, this policy setting monitors essential security settings to in
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Turn on Security Center (Domain PCs only)*
|
||||
- GP name: *SecurityCenterInDomain*
|
||||
- GP name: *SecurityCenter_SecurityCenterInDomain*
|
||||
- GP path: *Windows Components\Security Center*
|
||||
- GP ADMX file name: *Securitycenter.admx*
|
||||
|
||||
|
||||
@ -93,7 +93,7 @@ If you disable or do not configure this policy setting, or if the required files
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Specify settings for optional component installation and component repair*
|
||||
- GP name: *RepairContentServerSource*
|
||||
- GP name: *Servicing*
|
||||
- GP path: *System*
|
||||
- GP ADMX file name: *Servicing.admx*
|
||||
|
||||
|
||||
@ -174,7 +174,7 @@ To prevent users from using other administrative tools, use the "Run only specif
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Prevent access to registry editing tools*
|
||||
- GP name: *DisableRegistryTools*
|
||||
- GP name: *DisableRegedit*
|
||||
- GP path: *System*
|
||||
- GP ADMX file name: *Shell-CommandPrompt-RegEditTools.admx*
|
||||
|
||||
@ -250,7 +250,7 @@ This policy setting only prevents users from running programs that are started b
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Don't run specified Windows applications*
|
||||
- GP name: *DisallowRun*
|
||||
- GP name: *DisallowApps*
|
||||
- GP path: *System*
|
||||
- GP ADMX file name: *Shell-CommandPrompt-RegEditTools.admx*
|
||||
|
||||
@ -325,7 +325,7 @@ This policy setting only prevents users from running programs that are started b
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP English name: *Run only specified Windows applications*
|
||||
- GP name: *RestrictRun*
|
||||
- GP name: *RestrictApps*
|
||||
- GP path: *System*
|
||||
- GP ADMX file name: *Shell-CommandPrompt-RegEditTools.admx*
|
||||
|
||||
|
||||
@ -100,7 +100,7 @@ The [Policy DDF](policy-ddf-file.md) contains the following tags to identify the
|
||||
- \<MSFT:GPRegistryMappedName\>
|
||||
- \<MSFT:GPDBMappedName\>
|
||||
|
||||
For the list MDM-GP mapping list, see [Policy CSPs supported by Group Policy
|
||||
For the list MDM-GP mapping list, see [Policies in Policy CSP supported by Group Policy
|
||||
](policy-csps-supported-by-group-policy.md).
|
||||
|
||||
The MDM Diagnostic report shows the applied configurations states of a device including policies, certificates, configuration sources, and resource information. The report includes a list of blocked GP settings because MDM equivalent is configured, if any. To get the diagnostic report, go to **Settings** > **Accounts** > **Access work or school** > and then click the desired work or school account. Scroll to the bottom of the page to **Advanced Diagnostic Report** and then click **Create Report**.
|
||||
|
||||
@ -43,7 +43,9 @@ To troubleshoot Stop error messages, follow these general steps:
|
||||
2. As a best practice, we recommend that you do the following:
|
||||
|
||||
a. Make sure that you install the latest Windows updates, cumulative updates, and rollup updates. To verify the update status, refer to the appropriate update history for your system:
|
||||
|
||||
- [Windows 10, version 2004](https://support.microsoft.com/help/4555932)
|
||||
- [Windows 10, version 1909](https://support.microsoft.com/help/4529964)
|
||||
- [Windows 10, version 1903](https://support.microsoft.com/help/4498140)
|
||||
- [Windows 10, version 1809](https://support.microsoft.com/help/4464619)
|
||||
- [Windows 10, version 1803](https://support.microsoft.com/help/4099479)
|
||||
- [Windows 10, version 1709](https://support.microsoft.com/help/4043454)
|
||||
|
||||
@ -16,7 +16,7 @@ manager: dansimp
|
||||
|
||||
In this topic, you will learn how to use Microsoft Network Monitor 3.4, which is a tool for capturing network traffic.
|
||||
|
||||
> [Note]
|
||||
> [!NOTE]
|
||||
> Network Monitor is the archived protocol analyzer and is no longer under development. **Microsoft Message Analyzer** is the replacement for Network Monitor. For more details, see [Microsoft Message Analyzer Operating Guide](https://docs.microsoft.com/message-analyzer/microsoft-message-analyzer-operating-guide).
|
||||
|
||||
To get started, [download and run NM34_x64.exe](https://www.microsoft.com/download/details.aspx?id=4865). When you install Network Monitor, it installs its driver and hooks it to all the network adapters installed on the device. You can see the same on the adapter properties, as shown in the following image.
|
||||
|
||||
BIN
windows/deployment/images/sigverif.png
Normal file
BIN
windows/deployment/images/sigverif.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 38 KiB |
@ -5,7 +5,7 @@ manager: laurawi
|
||||
description: You can use Group Policy or your mobile device management (MDM) service to configure Windows Update for Business settings for your devices.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
|
||||
ms.collection: M365initiative-coredeploy
|
||||
audience: itpro
|
||||
author: jaimeo
|
||||
ms.localizationpriority: medium
|
||||
@ -48,7 +48,7 @@ With Windows Update for Business, you can set a device to be on either Windows I
|
||||
|
||||
**Release branch policies**
|
||||
|
||||
| Policy | Sets registry key under **HKLM\Software** |
|
||||
| Policy | Sets registry key under HKLM\Software |
|
||||
| --- | --- |
|
||||
| GPO for Windows 10, version 1607 or later: </br>Computer Configuration > Administrative Templates > Windows Components > Windows Update > Defer Windows Updates > **Select when Feature Updates are received** | \Policies\Microsoft\Windows\WindowsUpdate\BranchReadinessLevel |
|
||||
| GPO for Windows 10, version 1511: </br>Computer Configuration > Administrative Templates > Windows Components > Windows Update > **Defer Upgrades and Updates** | \Policies\Microsoft\Windows\WindowsUpdate\DeferUpgrade |
|
||||
@ -73,7 +73,7 @@ For example, a device on the Semi-Annual Channel with `DeferFeatureUpdatesPeriod
|
||||
</br></br>
|
||||
**Policy settings for deferring feature updates**
|
||||
|
||||
| Policy | Sets registry key under **HKLM\Software** |
|
||||
| Policy | Sets registry key under HKLM\Software |
|
||||
| --- | --- |
|
||||
| GPO for Windows 10, version 1607 later: </br>Computer Configuration > Administrative Templates > Windows Components > Windows Update > Defer Windows Updates > **Select when Feature Updates are received** | \Policies\Microsoft\Windows\WindowsUpdate\DeferFeatureUpdates</br>\Policies\Microsoft\Windows\WindowsUpdate\DeferFeatureUpdatesPeriodInDays |
|
||||
| GPO for Windows 10, version 1511: </br>Computer Configuration > Administrative Templates > Windows Components > Windows Update > **Defer Upgrades and Updates** | \Policies\Microsoft\Windows\WindowsUpdate\DeferUpgradePeriod |
|
||||
@ -97,7 +97,7 @@ In cases where the pause policy is first applied after the configured start date
|
||||
|
||||
**Policy settings for pausing feature updates**
|
||||
|
||||
| Policy | Sets registry key under **HKLM\Software** |
|
||||
| Policy | Sets registry key under HKLM\Software |
|
||||
| --- | --- |
|
||||
| GPO for Windows 10, version 1607 and later: </br>Computer Configuration > Administrative Templates > Windows Components > Windows Update > Defer Windows Updates > **Select when Feature Updates are received** | **1607:** \Policies\Microsoft\Windows\WindowsUpdate\PauseFeatureUpdates</br>**1703 and later:** \Policies\Microsoft\Windows\WindowsUpdate\PauseFeatureUpdatesStartTime |
|
||||
| GPO for Windows 10, version 1511: </br>Computer Configuration > Administrative Templates > Windows Components > Windows Update > **Defer Upgrades and Updates** | \Policies\Microsoft\Windows\WindowsUpdate\Pause |
|
||||
@ -134,7 +134,7 @@ You can set your system to receive updates for other Microsoft products—known
|
||||
|
||||
**Policy settings for deferring quality updates**
|
||||
|
||||
| Policy | Sets registry key under **HKLM\Software** |
|
||||
| Policy | Sets registry key under HKLM\Software |
|
||||
| --- | --- |
|
||||
| GPO for Windows 10, version 1607 and later: </br>Computer Configuration > Administrative Templates > Windows Components > Windows Update > Defer Windows Updates > **Select when Quality Updates are received** | \Policies\Microsoft\Windows\WindowsUpdate\DeferQualityUpdates</br>\Policies\Microsoft\Windows\WindowsUpdate\DeferQualityUpdatesPeriodInDays |
|
||||
| GPO for Windows 10, version 1511: </br>Computer Configuration > Administrative Templates > Windows Components > Windows Update > **Defer Upgrades and Updates** | \Policies\Microsoft\Windows\WindowsUpdate\DeferUpdatePeriod |
|
||||
@ -157,7 +157,7 @@ In cases where the pause policy is first applied after the configured start date
|
||||
|
||||
**Policy settings for pausing quality updates**
|
||||
|
||||
| Policy | Sets registry key under **HKLM\Software** |
|
||||
| Policy | Sets registry key under HKLM\Software |
|
||||
| --- | --- |
|
||||
| GPO for Windows 10, version 1607 and later: </br>Computer Configuration > Administrative Templates > Windows Components > Windows Update > Defer Windows Updates > **Select when Quality Updates are received** |**1607:** \Policies\Microsoft\Windows\WindowsUpdate\PauseQualityUpdates</br>**1703:** \Policies\Microsoft\Windows\WindowsUpdate\PauseQualityUpdatesStartTime |
|
||||
| GPO for Windows 10, version 1511: </br>Computer Configuration > Administrative Templates > Windows Components > Windows Update > **Defer Upgrades and Updates** | \Policies\Microsoft\Windows\WindowsUpdate\Pause |
|
||||
@ -207,7 +207,7 @@ Starting with Windows 10, version 1607, you can selectively opt out of receiving
|
||||
|
||||
**Policy settings to exclude drivers**
|
||||
|
||||
| Policy | Sets registry key under **HKLM\Software** |
|
||||
| Policy | Sets registry key under HKLM\Software |
|
||||
| --- | --- |
|
||||
| GPO for Windows 10, version 1607 and later: </br>Computer Configuration > Administrative Templates > Windows Components > Windows Update > **Do not include drivers with Windows Updates** | \Policies\Microsoft\Windows\WindowsUpdate\ExcludeWUDriversInQualityUpdate |
|
||||
| MDM for Windows 10, version 1607 and later: </br>../Vendor/MSFT/Policy/Config/Update/</br>**ExcludeWUDriversInQualityUpdate** | \Microsoft\PolicyManager\default\Update\ExcludeWUDriversInQualityUpdate |
|
||||
@ -220,7 +220,7 @@ The following are quick-reference tables of the supported policy values for Wind
|
||||
|
||||
| GPO Key | Key type | Value |
|
||||
| --- | --- | --- |
|
||||
| BranchReadinessLevel | REG_DWORD | 2: systems take Feature Updates for the Windows Insider build - Fast (added in Windows 10, version 1709)</br> 4: systems take Feature Updates for the Windows Insider build - Slow (added in Windows 10, version 1709)</br> 8: systems take Feature Updates for the Release Windows Insider build (added in Windows 10, version 1709)</br> 16: for Windows 10, version 1703: systems take Feature Updates for the Current Branch (CB); for Windows 10, version 1709, 1803 and 1809: systems take Feature Updates from Semi-annual Channel (Targeted) (SAC-T); for Windows 10, version 1903 or later: systems take Feature Updates from Semi-annual Channel </br>32: systems take Feature Updates from Semi-annual Channel </br>Note: Other value or absent: receive all applicable updates |
|
||||
| BranchReadinessLevel | REG_DWORD | 2: systems take Feature Updates for the Windows Insider build - Fast (added in Windows 10, version 1709)</br> 4: systems take Feature Updates for the Windows Insider build - Slow (added in Windows 10, version 1709)</br> 8: systems take Feature Updates for the Release Windows Insider build (added in Windows 10, version 1709)</br> 16: for Windows 10, version 1703: systems take Feature Updates for the Current Branch (CB); for Windows 10, version 1709, 1803 and 1809: systems take Feature Updates from Semi-Annual Channel (Targeted) (SAC-T); for Windows 10, version 1903 or later: systems take Feature Updates from Semi-Annual Channel </br>32: systems take Feature Updates from Semi-Annual Channel </br>Note: Other value or absent: receive all applicable updates |
|
||||
| DeferQualityUpdates | REG_DWORD | 1: defer quality updates</br>Other value or absent: don’t defer quality updates |
|
||||
| DeferQualityUpdatesPeriodinDays | REG_DWORD | 0-35: defer quality updates by given days |
|
||||
| PauseQualityUpdatesStartTime | REG_DWORD | 1: pause quality updates</br>Other value or absent: don’t pause quality updates |
|
||||
@ -234,7 +234,7 @@ The following are quick-reference tables of the supported policy values for Wind
|
||||
|
||||
| MDM Key | Key type | Value |
|
||||
| --- | --- | --- |
|
||||
| BranchReadinessLevel | REG_DWORD |2: systems take Feature Updates for the Windows Insider build - Fast (added in Windows 10, version 1709)</br> 4: systems take Feature Updates for the Windows Insider build - Slow (added in Windows 10, version 1709)</br> 8: systems take Feature Updates for the Release Windows Insider build (added in Windows 10, version 1709)</br> 16: for Windows 10, version 1703: systems take Feature Updates for the Current Branch (CB); for Windows 10, version 1709, 1803 and 1809: systems take Feature Updates from Semi-annual Channel (Targeted) (SAC-T); for Windows 10, version 1903 or later: systems take Feature Updates from Semi-annual Channel </br>32: systems take Feature Updates from Semi-annual Channel </br>Note: Other value or absent: receive all applicable updates |
|
||||
| BranchReadinessLevel | REG_DWORD |2: systems take Feature Updates for the Windows Insider build - Fast (added in Windows 10, version 1709)</br> 4: systems take Feature Updates for the Windows Insider build - Slow (added in Windows 10, version 1709)</br> 8: systems take Feature Updates for the Release Windows Insider build (added in Windows 10, version 1709)</br> 16: for Windows 10, version 1703: systems take Feature Updates for the Current Branch (CB); for Windows 10, version 1709, 1803 and 1809: systems take Feature Updates from Semi-Annual Channel (Targeted) (SAC-T); for Windows 10, version 1903 or later: systems take Feature Updates from Semi-Annual Channel </br>32: systems take Feature Updates from Semi-Annual Channel </br>Note: Other value or absent: receive all applicable updates |
|
||||
| DeferQualityUpdatesPeriodinDays | REG_DWORD | 0-35: defer quality updates by given days |
|
||||
| PauseQualityUpdatesStartTime | REG_DWORD | 1: pause quality updates</br>Other value or absent: don’t pause quality updates |
|
||||
| DeferFeatureUpdatesPeriodinDays | REG_DWORD | 0-365: defer feature updates by given days |
|
||||
|
||||
@ -1,6 +1,5 @@
|
||||
---
|
||||
title: Delivery Optimization for Windows 10 updates
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
description: Delivery Optimization is a peer-to-peer distribution method in Windows 10
|
||||
keywords: oms, operations management suite, wdav, updates, downloads, log analytics
|
||||
@ -10,7 +9,9 @@ audience: itpro
|
||||
author: jaimeo
|
||||
ms.localizationpriority: medium
|
||||
ms.author: jaimeo
|
||||
ms.collection: M365-modern-desktop
|
||||
ms.collection:
|
||||
- M365-modern-desktop
|
||||
- M365initiative-coredeploy
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
@ -111,7 +112,7 @@ In MDM, the same settings are under **.Vendor/MSFT/Policy/Config/DeliveryOptimiz
|
||||
|
||||
Starting with Microsoft Intune version 1902, you can set many Delivery Optimization policies as a profile, which you can then apply to groups of devices. For more information, see [Delivery Optimization settings in Microsoft Intune](https://docs.microsoft.com/intune/delivery-optimization-windows))
|
||||
|
||||
**Starting with Windows 10, version 1903,** you can use the Azure Active Directory (AAD) Tenant ID as a means to define groups. To do this set the value for DOGroupIdSource to its new maximum value of 5.
|
||||
**Starting with Windows 10, version 1903,** you can use the Azure Active Directory (Azure AD) Tenant ID as a means to define groups. To do this set the value for DOGroupIdSource to its new maximum value of 5.
|
||||
|
||||
## Reference
|
||||
|
||||
|
||||
@ -6,8 +6,7 @@ ms.mktglfcycl: manage
|
||||
author: jaimeo
|
||||
ms.localizationpriority: medium
|
||||
ms.author: jaimeo
|
||||
ms.date: 07/27/2017
|
||||
ms.reviewer:
|
||||
ms.collection: M365initiative-coredeploy
|
||||
manager: laurawi
|
||||
ms.topic: article
|
||||
---
|
||||
@ -69,7 +68,7 @@ For Windows 10, version 1607, devices can now be configured to receive updates f
|
||||
|
||||
- Device is configured to defer Quality Updates using Windows Update for Business and to be managed by WSUS
|
||||
- Device is configured to “receive updates for other Microsoft products” along with updates to Windows (**Update/AllowMUUpdateService** = enabled)
|
||||
- Admin has also placed Microsoft Update, third-paprty, and locally-published update content on the WSUS server
|
||||
- Admin has also placed Microsoft Update, non-Microsoft, and locally published update content on the WSUS server
|
||||
|
||||
In this example, the deferral behavior for updates to Office and other non-Windows products is slightly different than if WSUS were not enabled.
|
||||
- In a non-WSUS case, these updates would be deferred just as any update to Windows would be.
|
||||
|
||||
@ -9,6 +9,7 @@ ms.author: jaimeo
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.topic: article
|
||||
ms.collection: M365initiative-coredeploy
|
||||
---
|
||||
|
||||
# Prepare servicing strategy for Windows 10 updates
|
||||
@ -29,9 +30,9 @@ In the past, traditional Windows deployments tended to be large, lengthy, and ex
|
||||
Windows 10 spreads the traditional deployment effort of a Windows upgrade, which typically occurred every few years, over smaller, continuous updates. With this change, you must approach the ongoing deployment and servicing of Windows differently. A strong Windows 10 deployment strategy begins with establishing a simple, repeatable process for testing and deploying each feature update. Here’s an example of what this process might look like:
|
||||
|
||||
- **Configure test devices.** Configure test devices in the Windows Insider Program so that Insiders can test feature updates before they’re available to the Semi-Annual Channel. Typically, this would be a small number of test devices that IT staff members use to evaluate pre-release builds of Windows. Microsoft provides current development builds to Windows Insider members approximately every week so that interested users can see the functionality Microsoft is adding. See the section Windows Insider for details on how to enroll in the Windows Insider Program on a Windows 10 device.
|
||||
- **Identify excluded devices.** For some organizations, special-purpose devices such as those used to control factory or medical equipment or run ATMs require a stricter, less frequent feature update cycle than the Semi-annual Channel can offer. For those machines, you must install Windows 10 Enterprise LTSB to avoid feature updates for up to 10 years. Identify these devices, and separate them from the phased deployment and servicing cycles to help remove confusion for your administrators and ensure that devices are handled correctly.
|
||||
- **Identify excluded devices.** For some organizations, special-purpose devices such as those used to control factory or medical equipment or run ATMs require a stricter, less frequent feature update cycle than the Semi-Annual Channel can offer. For those machines, you must install Windows 10 Enterprise LTSB to avoid feature updates for up to 10 years. Identify these devices, and separate them from the phased deployment and servicing cycles to help remove confusion for your administrators and ensure that devices are handled correctly.
|
||||
- **Recruit volunteers.** The purpose of testing a deployment is to receive feedback. One effective way to recruit pilot users is to request volunteers. When doing so, clearly state that you’re looking for feedback rather than people to just “try it out” and that there could be occasional issues involved with accepting feature updates right away. With Windows as a service, the expectation is that there should be few issues, but if an issue does arise, you want testers to let you know as soon as possible. When considering whom to recruit for pilot groups, be sure to include members who provide the broadest set of applications and devices to validate the largest number of apps and devices possible.
|
||||
- **Update Group Policy.** Each feature update includes new group policies to manage new features. If you use Group Policy to manage devices, the Group Policy Admin for the Active Directory domain will need to download a .admx package and copy it to their [Central Store](https://support.microsoft.com/help/929841/how-to-create-the-central-store-for-group-policy-administrative-templa) (or to the [PolicyDefinitions](https://msdn.microsoft.com/library/bb530196.aspx) directory in the SYSVOL of a domain controller if not using a Central Store). Always manage new group polices from the version of Windows 10 they shipped with by using the Remote Server Administration Tools. The ADMX download package is created at the end of each development cycle and then posted for download. To find the ADMX download package for a given Windows build, search for “ADMX download for Windows build xxxx”. For details about Group Policy management, see [How to create and manage the Central Store for Group Policy Administrative Templates in Windows](https://support.microsoft.com/help/3087759/how-to-create-and-manage-the-central-store-for-group-policy-administra)
|
||||
- **Update Group Policy.** Each feature update includes new group policies to manage new features. If you use Group Policy to manage devices, the Group Policy Admin for the Active Directory domain will need to download a .admx package and copy it to their [Central Store](https://support.microsoft.com/help/929841/how-to-create-the-central-store-for-group-policy-administrative-templa) (or to the [PolicyDefinitions](https://msdn.microsoft.com/library/bb530196.aspx) directory in the SYSVOL folder of a domain controller if not using a Central Store). Always manage new group polices from the version of Windows 10 they shipped with by using the Remote Server Administration Tools. The ADMX download package is created at the end of each development cycle and then posted for download. To find the ADMX download package for a given Windows build, search for “ADMX download for Windows build xxxx”. For details about Group Policy management, see [How to create and manage the Central Store for Group Policy Administrative Templates in Windows](https://support.microsoft.com/help/3087759/how-to-create-and-manage-the-central-store-for-group-policy-administra)
|
||||
- **Choose a servicing tool.** Decide which product you’ll use to manage the Windows updates in your environment. If you’re currently using Windows Server Update Services (WSUS) or Microsoft Endpoint Configuration Manager to manage your Windows updates, you can continue using those products to manage Windows 10 updates. Alternatively, you can use Windows Update for Business. In addition to which product you’ll use, consider how you’ll deliver the updates. With Windows 10, multiple peer-to-peer options are available to make update distribution faster. For a comparison of tools, see [Servicing tools](waas-overview.md#servicing-tools).
|
||||
- **Prioritize applications.** First, create an application portfolio. This list should include everything installed in your organization and any webpages your organization hosts. Next, prioritize this list to identify those that are the most business critical. Because the expectation is that application compatibility with Windows 10 will be high, only the most business critical applications should be tested before the pilot phase; everything else can be tested afterwards. For more information about identifying compatibility issues withe applications, see [Manage Windows upgrades with Upgrade Analytics](../upgrade/manage-windows-upgrades-with-upgrade-readiness.md).
|
||||
|
||||
@ -43,7 +44,7 @@ Windows 10 spreads the traditional deployment effort of a Windows upgrade, which
|
||||
Each time Microsoft releases a Windows 10 feature update, the IT department should use the following high-level process to help ensure that the broad deployment is successful:
|
||||
|
||||
1. **Validate compatibility of business critical apps.** Test your most important business-critical applications for compatibility with the new Windows 10 feature update running on your Windows Insider machines identified in the earlier “Configure test machines” step of the Predeployment strategy section. The list of applications involved in this validation process should be small because most applications can be tested during the pilot phase. For more information about device and application compatibility in Windows 10, see the section Compatibility.
|
||||
2. **Target and react to feedback.** With Windows 10, Microsoft expects application and device compatibility to be high, but it’s still important to have targeted groups within both the IT department and business units to verify application compatibility for the remaining applications in your application portfolio. Because only the most business-critical applications are tested beforehand, this will represent the majority of application compatibility testing in your environment. This should not necessarily be a formal process but rather user validation through the use of a particular application. So, the next step is to deploy the feature update to early-adopting IT users and your targeted groups running in the Semi-annual channel that you identified in the “Recruit volunteers” step of the Predeployment strategy section. Be sure to communicate clearly that you’re looking for feedback as soon as possible, and state exactly how users can submit feedback to you. Should an issue arise, have a remediation plan in place to address it.
|
||||
2. **Target and react to feedback.** With Windows 10, Microsoft expects application and device compatibility to be high, but it’s still important to have targeted groups within both the IT department and business units to verify application compatibility for the remaining applications in your application portfolio. Because only the most business-critical applications are tested beforehand, this will represent the majority of application compatibility testing in your environment. This should not necessarily be a formal process but rather user validation through the use of a particular application. So, the next step is to deploy the feature update to early-adopting IT users and your targeted groups running in the Semi-Annual channel that you identified in the “Recruit volunteers” step of the Predeployment strategy section. Be sure to communicate clearly that you’re looking for feedback as soon as possible, and state exactly how users can submit feedback to you. Should an issue arise, have a remediation plan in place to address it.
|
||||
3. **Deploy broadly.** Finally, focus on the large-scale deployment using deployment rings, like the ones discussed in Table 1. Build deployment rings that target groups of computers in your selected update-management product. To reduce risk as much as possible, construct your deployment rings in a way that splits individual departments into multiple rings. This way, if you were to encounter an issue, you don’t prevent any critical business from continuing. By using this method, each deployment ring reduces risk as more and more people have been updated in any particular department.
|
||||
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.mktglfcycl: manage
|
||||
author: jaimeo
|
||||
ms.localizationpriority: medium
|
||||
ms.author: jaimeo
|
||||
ms.reviewer:
|
||||
ms.collection: M365initiative-coredeploy
|
||||
manager: laurawi
|
||||
ms.topic: article
|
||||
---
|
||||
@ -59,7 +59,7 @@ Both Windows 10 feature and quality updates are automatically offered to devices
|
||||
|
||||
To enable Microsoft Updates use the Group Policy Management Console go to **Computer Configuration > Administrative Templates > Windows Components > Windows Update > Configure Automatic Updates** and select **Install updates for other Microsoft products**.
|
||||
|
||||
Drivers are automatically enabled because they are beneficial to device systems. We recommend that you allow the driver policy to allow drivers to updated on devices (the default), but you can turn this setting off if you prefer to manage drivers manually. If you want to disable driver updates for some reason, use the Group Policy Management Console to go to **Computer Configuration > Administrative Templates > Windows Components > Windows Update > Do not include drivers with Windows Updates** and enable the policy.
|
||||
Drivers are automatically enabled because they are beneficial to device systems. We recommend that you allow the driver policy to allow drivers to update on devices (the default), but you can turn this setting off if you prefer to manage drivers manually. If you want to disable driver updates for some reason, use the Group Policy Management Console to go to **Computer Configuration > Administrative Templates > Windows Components > Windows Update > Do not include drivers with Windows Updates** and enable the policy.
|
||||
|
||||
We also recommend that you allow Microsoft product updates as discussed previously.
|
||||
|
||||
@ -138,7 +138,7 @@ When you set these policies, installation happens automatically at the specified
|
||||
|
||||
We recommend that you use **Computer Configuration > Administrative Templates > Windows Components > Windows Update > Specify deadline for automatic updates and restarts** for feature and quality updates to ensure that devices stay secure on Windows 10, version 1709 and later. This works by enabling you to specify the number of days that can elapse after an update is offered to a device before it must be installed. Also you can set the number of days that can elapse after a pending restart before the user is forced to restart.
|
||||
|
||||
This policies also offers an option to opt out of automatic restarts until a deadline is reached by presenting an "engaged restart experience" until the deadline has actually expired. At that point the device will automatically schedule a restart regardles of active hours.
|
||||
This policies also offers an option to opt out of automatic restarts until a deadline is reached by presenting an "engaged restart experience" until the deadline has actually expired. At that point the device will automatically schedule a restart regardless of active hours.
|
||||
|
||||
These notifications are what the user sees depending on the settings you choose:
|
||||
|
||||
|
||||
@ -3,7 +3,7 @@ title: Quick fixes - Windows IT Pro
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
description: Learn how to quickly resolve many problems which may come up during a Windows 10 upgrade.
|
||||
description: Learn how to quickly resolve many problems, which may come up during a Windows 10 upgrade.
|
||||
keywords: deploy, error, troubleshoot, windows, 10, upgrade, code, rollback, ITPro
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
@ -38,6 +38,7 @@ The Microsoft Virtual Agent provided by [Microsoft Support](https://support.micr
|
||||
<li>Check the system drive for errors and attempt repairs. <a href="#repair-the-system-drive" data-raw-source="[More information](#repair-the-system-drive)">More information</a>.</li>
|
||||
<li>Run the Windows Update troubleshooter. <a href="#windows-update-troubleshooter" data-raw-source="[More information](#windows-update-troubleshooter)">More information</a>.</li>
|
||||
<li>Attempt to restore and repair system files. <a href="#repair-system-files" data-raw-source="[More information](#repair-system-files)">More information</a>.</li>
|
||||
<li>Check for unsigned drivers and update or repair them. <a href="#repair-unsigned-drivers" data-raw-source="[More information](#repair-unsigned-drivers)">More information</a>.</li>
|
||||
<li>Update Windows so that all available recommended updates are installed, and ensure the computer is rebooted if this is necessary to complete installation of an update. <a href="#update-windows" data-raw-source="[More information](#update-windows)">More information</a>.</li>
|
||||
<li>Temporarily uninstall non-Microsoft antivirus software.
|
||||
<a href="#uninstall-non-microsoft-antivirus-software" data-raw-source="[More information](#uninstall-non-microsoft-antivirus-software)">More information</a>.</li>
|
||||
@ -152,9 +153,76 @@ To check and repair system files:
|
||||
|
||||
```
|
||||
> [!NOTE]
|
||||
> It may take several minutes for the command operations to be completed. For more information, see [Repair a Windows Image](https://msdn.microsoft.com/windows/hardware/commercialize/manufacture/desktop/repair-a-windows-image).
|
||||
> It may take several minutes for the command operations to be completed. For more information, see [Repair a Windows Image](https://msdn.microsoft.com/windows/hardware/commercialize/manufacture/desktop/repair-a-windows-image) and [Use the System File Checker tool](https://support.microsoft.com/help/929833/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system).
|
||||
|
||||
|
||||
### Repair unsigned drivers
|
||||
|
||||
Drivers that are not properly signed can block the upgrade process. Drivers might not be properly signed if you:
|
||||
- Disabled driver signature verification (highly not recommended).
|
||||
- A catalog file used to sign a driver is corrupt or missing.
|
||||
|
||||
Catalog files are used to sign drivers. If a catalog file is corrupt or missing, the driver will appear to be unsigned, even though it should be signed. This can cause the upgrade process to fail. To restore the catalog file, reinstall the driver or copy the catalog file from another device. You might need to analyze another device to determine the catalog file that is associated with the unsigned driver. All drivers should be signed to ensure the upgrade process works.
|
||||
|
||||
To check your system for unsigned drivers:
|
||||
|
||||
1. Click **Start**.
|
||||
2. Type **command**.
|
||||
3. Right-click **Command Prompt** and then left-click **Run as administrator**.
|
||||
4. If you are prompted by UAC, click **Yes**.
|
||||
5. Type **sigverif** and press ENTER.
|
||||
6. The File Signature Verification tool will open. Click **Start**.
|
||||
|
||||
|
||||
|
||||
7. After the scanning process is complete, if you see **Your files have been scanned and verified as digitally signed** then you have no unsigned drivers. Otherwise, you will see **The following files have not been digitally signed** and a list will be provided with name, location, and version of all unsigned drivers.
|
||||
8. To view and save a log file, click **Advanced**, and then click **View Log**. Save the log file if desired.
|
||||
9. Locate drivers in the log file that are unsigned, write down the location and file names. Also write down the catalog that is associated to the driver if it is provided. If the name of a catalog file is not provided you might need to analyze another device that has the same driver with sigverif and sigcheck (described below).
|
||||
10. Download [sigcheck.zip](https://download.sysinternals.com/files/Sigcheck.zip) and extract the tool to a directory on your computer, for example: **C:\sigcheck**.
|
||||
|
||||
[Sigcheck](https://docs.microsoft.com/sysinternals/downloads/sigcheck) is a tool that you can download and use to review digital signature details of a file. To use sigcheck:
|
||||
|
||||
11. In the command window, use the **cd** command to switch to the directory where you extracted sigcheck, for example **cd c:\sigcheck**.
|
||||
12. Using the list of unsigned drivers and their associated paths that you obtained from the File Signature Verification tool, run sigcheck to obtain details about the driver, including the catalog file used for signing. Type **sigcheck64 -i \<driver path\>** and press ENTER (or sigcheck -i for a 32 bit OS). See the following example:
|
||||
```
|
||||
C:\Sigcheck>sigcheck64.exe -i c:\windows\system32\drivers\afd.sys
|
||||
|
||||
Sigcheck v2.80 - File version and signature viewer
|
||||
Copyright (C) 2004-2020 Mark Russinovich
|
||||
Sysinternals - www.sysinternals.com
|
||||
|
||||
c:\windows\system32\drivers\afd.sys:
|
||||
Verified: Signed
|
||||
Signing date: 6:18 PM 11/29/2017
|
||||
Signing date: 6:18 PM 11/29/2017
|
||||
Catalog: C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Package_163_for_KB4054518~31bf3856ad364e35~x86~~6.1.1.2.cat
|
||||
Signers:
|
||||
Microsoft Windows
|
||||
Cert Status: This certificate or one of the certificates in the certificate chain is not time valid.
|
||||
Valid Usage: NT5 Crypto, Code Signing
|
||||
Cert Issuer: Microsoft Windows Verification PCA
|
||||
Serial Number: 33 00 00 00 4B 76 63 2D 24 A2 39 9A 8B 00 01 00 00 00 4B
|
||||
Thumbprint: B8037C46D0DB7A8CEE502407469B0EE3234D3365
|
||||
Algorithm: sha1RSA
|
||||
Valid from: 11:46 AM 3/1/2017
|
||||
Valid to: 11:46 AM 5/9/2018
|
||||
(output truncated)
|
||||
```
|
||||
|
||||
13. Optionally, you can generate a list of drivers using driverquery.exe, which is included with Windows. To save a list of signed and unsigned drivers with driverquery, type **driverquery /si > c:\drivers.txt** and press ENTER. See the following example:
|
||||
|
||||
```cmd
|
||||
C:\>Driverquery /si
|
||||
|
||||
DeviceName InfName IsSigned Manufacturer
|
||||
============================== ============= ======== =========================
|
||||
Microsoft ISATAP Adapter nettun.inf TRUE Microsoft
|
||||
Generic volume shadow copy volsnap.inf TRUE Microsoft
|
||||
Generic volume volume.inf TRUE Microsoft
|
||||
(truncated)
|
||||
```
|
||||
For more information about using driverquery, see [Two Minute Drill: DriverQuery.exe](https://techcommunity.microsoft.com/t5/ask-the-performance-team/two-minute-drill-driverquery-exe/ba-p/374977) and [driverquery](https://docs.microsoft.com/windows-server/administration/windows-commands/driverquery).
|
||||
|
||||
### Update Windows
|
||||
|
||||
You should ensure that all important updates are installed before attempting to upgrade. This includes updates to hardware drivers on your computer.
|
||||
|
||||
@ -36,7 +36,7 @@ A frequently observed [result code](upgrade-error-codes.md#result-codes) is 0xC1
|
||||
|
||||
The device install log is particularly helpful if rollback occurs during the sysprep operation (extend code 0x30018).
|
||||
|
||||
To resolve a rollback that was caused by driver conflicts, try running setup using a minimal set of drivers and startup programs by performing a [clean boot](https://support.microsoft.com/kb/929135) before initiating the upgrade process.
|
||||
To resolve a rollback that was caused by driver conflicts, try running setup using a minimal set of drivers and startup programs by performing a [clean boot](https://support.microsoft.com/kb/929135) before initiating the upgrade process. Also check to be sure that your drivers are properly signed. For more information, see [Remove unsigned drivers](quick-fixes.md#repair-unsigned-drivers).
|
||||
|
||||
See the following general troubleshooting procedures associated with a result code of 0xC1900101:<br /><br />
|
||||
|
||||
@ -49,7 +49,7 @@ See the following general troubleshooting procedures associated with a result co
|
||||
| 0xC1900101 - 0x30018 | Disconnect all peripheral devices that are connected to the system, except for the mouse, keyboard and display.<br>Contact your hardware vendor to obtain updated device drivers.<br>Ensure that "Download and install updates (recommended)" is accepted at the start of the upgrade process. | A device driver has stopped responding to setup.exe during the upgrade process. |
|
||||
| 0xC1900101 - 0x3000D | Disconnect all peripheral devices that are connected to the system, except for the mouse, keyboard and display.<br>Update or uninstall the display driver. | Installation failed during the FIRST_BOOT phase while attempting the MIGRATE_DATA operation.<br>This can occur due to a problem with a display driver. |
|
||||
| 0xC1900101 - 0x4000D | Check supplemental rollback logs for a setupmem.dmp file, or event logs for any unexpected reboots or errors.<br>Review the rollback log and determine the stop code.<br>The rollback log is located in the <strong>$Windows.~BT\Sources\Rollback</strong> folder. An example analysis is shown below. This example is not representative of all cases:<br> <br>Info SP Crash 0x0000007E detected<br>Info SP Module name :<br>Info SP Bugcheck parameter 1 : 0xFFFFFFFFC0000005<br>Info SP Bugcheck parameter 2 : 0xFFFFF8015BC0036A<br>Info SP Bugcheck parameter 3 : 0xFFFFD000E5D23728<br>Info SP Bugcheck parameter 4 : 0xFFFFD000E5D22F40<br>Info SP Cannot recover the system.<br>Info SP Rollback: Showing splash window with restoring text: Restoring your previous version of Windows.<br> <br>Typically, there is a dump file for the crash to analyze. If you are not equipped to debug the dump, then attempt the following basic troubleshooting procedures:<br> <br>1. Make sure you have enough disk space.<br>2. If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.<br>3. Try changing video adapters.<br>4. Check with your hardware vendor for any BIOS updates.<br>5. Disable BIOS memory options such as caching or shadowing. | A rollback occurred due to a driver configuration issue.<br>Installation failed during the second boot phase while attempting the MIGRATE_DATA operation.<br>This can occur because of incompatible drivers. |
|
||||
| 0xC1900101 - 0x40017 | Clean boot into Windows, and then attempt the upgrade to Windows 10. For more information, see [How to perform a clean boot in Windows](https://support.microsoft.com/kb/929135).<br> <br>Ensure that you select the option to "Download and install updates (recommended)." <br> <br><b>Computers that run Citrix VDA</b> <br>You may see this message after you upgrade a computer from Windows 10, version 1511 to Windows 10, version 1607. After the second system restart, the system generates this error and then rolls back to the previous version. This problem has also been observed in upgrades to Windows 8.1 and Windows 8. <br> <br>This problem occurs because the computer has Citrix Virtual Delivery Agent (VDA) installed. Citrix VDA installs device drivers and a file system filter driver (CtxMcsWbc). This Citrix filter driver prevents the upgrade from writing changes to the disk, so the upgrade cannot complete and the system rolls back. <br> <br>**Resolution**<br> <br>To resolve this problem, install [Cumulative update for Windows 10 Version 1607 and Windows Server 2016: November 8, 2016](https://support.microsoft.com/help/3200970/cumulative-update-for-windows-10-version-1607-and-windows-server-2016).<br> <br>You can work around this problem in two ways:<br> <br>**Workaround 1**<br> <br>1. Use the VDA setup application (VDAWorkstationSetup_7.11) to uninstall Citrix VDA.<br>2. Run the Windows upgrade again.<br>3. Reinstall Citrix VDA.<br> <br>**Workaround 2**<br> <br>If you cannot uninstall Citrix VDA, follow these steps to work around this problem: <br> <br>1. In Registry Editor, go to the following subkey:<br> **HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e967-e325-11ce-bfc1-08002be10318}\CtxMcsWbc**<br>2. Change the value of the **Start** entry from **0** to **4**. This change disables the Citrix MCS cache service.<br>3. Go to the following subkey:<br> **HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e967-e325-11ce-bfc1-08002be10318}**<br>4. Delete the **CtxMcsWbc** entry.<br>5. Restart the computer, and then try the upgrade again.<br> <br>**Non-Microsoft information disclaimer** <br>The non-Microsoft products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products. | Windows 10 upgrade failed after the second reboot.<br>This is usually caused by a faulty driver. For example: antivirus filter drivers or encryption drivers. |
|
||||
| 0xC1900101 - 0x40017 | Clean boot into Windows, and then attempt the upgrade to Windows 10. For more information, see [How to perform a clean boot in Windows](https://support.microsoft.com/kb/929135).<br> <br>Ensure that you select the option to "Download and install updates (recommended)." Also be sure to [remove unsigned drivers](quick-fixes.md#repair-unsigned-drivers).<br> <br><b>Computers that run Citrix VDA</b> <br>You may see this message after you upgrade a computer from Windows 10, version 1511 to Windows 10, version 1607. After the second system restart, the system generates this error and then rolls back to the previous version. This problem has also been observed in upgrades to Windows 8.1 and Windows 8. <br> <br>This problem occurs because the computer has Citrix Virtual Delivery Agent (VDA) installed. Citrix VDA installs device drivers and a file system filter driver (CtxMcsWbc). This Citrix filter driver prevents the upgrade from writing changes to the disk, so the upgrade cannot complete and the system rolls back. <br> <br>**Resolution**<br> <br>To resolve this problem, install [Cumulative update for Windows 10 Version 1607 and Windows Server 2016: November 8, 2016](https://support.microsoft.com/help/3200970/cumulative-update-for-windows-10-version-1607-and-windows-server-2016).<br> <br>You can work around this problem in two ways:<br> <br>**Workaround 1**<br> <br>1. Use the VDA setup application (VDAWorkstationSetup_7.11) to uninstall Citrix VDA.<br>2. Run the Windows upgrade again.<br>3. Reinstall Citrix VDA.<br> <br>**Workaround 2**<br> <br>If you cannot uninstall Citrix VDA, follow these steps to work around this problem: <br> <br>1. In Registry Editor, go to the following subkey:<br> **HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e967-e325-11ce-bfc1-08002be10318}\CtxMcsWbc**<br>2. Change the value of the **Start** entry from **0** to **4**. This change disables the Citrix MCS cache service.<br>3. Go to the following subkey:<br> **HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e967-e325-11ce-bfc1-08002be10318}**<br>4. Delete the **CtxMcsWbc** entry.<br>5. Restart the computer, and then try the upgrade again.<br> <br>**Non-Microsoft information disclaimer** <br>The non-Microsoft products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products. | Windows 10 upgrade failed after the second reboot.<br>This is usually caused by a faulty driver. For example: antivirus filter drivers or encryption drivers. |
|
||||
|
||||
## 0x800xxxxx
|
||||
|
||||
|
||||
@ -95,6 +95,7 @@ The following methodology was used to derive the network endpoints:
|
||||
|wdcp.microsoft.com|HTTPS|Used for Windows Defender when Cloud-based Protection is enabled
|
||||
|activity.windows.com|TLSV1.2|Used by Activity Feed Service which enables multiple cross-device data roaming scenarios on Windows
|
||||
|adl.windows.com|HTTP|Used for compatibility database updates for Windows
|
||||
|spclient.wg.spotify.com|TLSV1.2|Used for Spotify Live Tile
|
||||
|
||||
## Windows 10 Pro
|
||||
|
||||
@ -159,6 +160,7 @@ The following methodology was used to derive the network endpoints:
|
||||
|windows.policies.live.net|HTTP|OneDrive
|
||||
|activity.windows.com|TLSV1.2|Used by Activity Feed Service which enables multiple cross-device data roaming scenarios on Windows
|
||||
|adl.windows.com|HTTP|Used for compatibility database updates for Windows
|
||||
|spclient.wg.spotify.com|TLSV1.2|Used for Spotify Live Tile
|
||||
|
||||
## Windows 10 Education
|
||||
|
||||
|
||||
@ -95,8 +95,7 @@ Sign-in a certificate authority or management workstations with _Enterprise Admi
|
||||
The certificate template is configured to supersede all the certificate templates provided in the certificate templates superseded templates list. However, the certificate template and the superseding of certificate templates is not active until you publish the certificate template to one or more certificate authorities.
|
||||
|
||||
> [!NOTE]
|
||||
> * The Domain Controller Certificate must be present in the NTAuth store. By default, Microsoft Enterprise CAs are added to the NTAuth store.
|
||||
> * If you are using a 3rd party CA, add the certificate to the NTAuth store. If the Domain Controller Certificate is not present in the NTAuth store, user authentication will fail.
|
||||
> The domain controller's certificate must chain to a root in the NTAuth store. By default, the Active Directory Certificate Authority's root certificate is added to the NTAuth store. If you are using a third-party CA, this may not be done by default. If the domain controller certificate does not chain to a root in the NTAuth store, user authentication will fail.
|
||||
|
||||
### Enrollment Agent certificate template
|
||||
|
||||
|
||||
@ -39,7 +39,7 @@ Sign-in a domain controller or management workstation with _Domain Admin_ equiva
|
||||
2. Click the **Users** container in the navigation pane.
|
||||
3. Right-click **Key Admins** in the details pane and click **Properties**.
|
||||
4. Click the **Members** tab and click **Add**
|
||||
5. In the **Enter the object names to select** text box, type the name of the Azure AD Connect service account. Click **OK**.
|
||||
5. In the **Enter the object names to select** text box, type the name of the service account used as an AD DS Connector account and click **OK**.
|
||||
6. Click **OK** to return to **Active Directory Users and Computers**.
|
||||
|
||||
### Section Review
|
||||
|
||||
@ -48,44 +48,54 @@ The following client-side components are also required:
|
||||
- Trusted Platform Module (TPM)
|
||||
|
||||
## VPN device compliance
|
||||
|
||||
At this time, the Azure AD certificates issued to users do not contain a CRL Distribution Point (CDP) and are not suitable for Key Distribution Centers (KDCs) to issue Kerberos tokens. For users to gain access to on-premises resources such as files on a network share, client authentication certificates must be deployed to the Windows profiles of the users, and their VPNv2 profiles must contain the <SSO> section.
|
||||
|
||||
Server-side infrastructure requirements to support VPN device compliance include:
|
||||
|
||||
- The VPN server should be configured for certificate authentication
|
||||
- The VPN server should trust the tenant-specific Azure AD CA
|
||||
- For client access using Kerberos/NTLM, a domain-trusted certificate is deployed to the client device and is configured to be used for single sign-on (SSO)
|
||||
- The VPN server should be configured for certificate authentication.
|
||||
- The VPN server should trust the tenant-specific Azure AD CA.
|
||||
- For client access using Kerberos/NTLM, a domain-trusted certificate is deployed to the client device and is configured to be used for single sign-on (SSO).
|
||||
|
||||
After the server side is set up, VPN admins can add the policy settings for conditional access to the VPN profile using the VPNv2 DeviceCompliance node.
|
||||
|
||||
Two client-side configuration service providers are leveraged for VPN device compliance.
|
||||
|
||||
- VPNv2 CSP DeviceCompliance settings
|
||||
- VPNv2 CSP DeviceCompliance settings:
|
||||
|
||||
- **Enabled**: enables the Device Compliance flow from the client. If marked as **true**, the VPN client attempts to communicate with Azure AD to get a certificate to use for authentication. The VPN should be set up to use certificate authentication and the VPN server must trust the server returned by Azure AD.
|
||||
- **Sso**: entries under SSO should be used to direct the VPN client to use a certificate other than the VPN authentication certificate when accessing resources that require Kerberos authentication.
|
||||
- **Sso/Enabled**: if this field is set to **true**, the VPN client looks for a separate certificate for Kerberos authentication.
|
||||
- **Sso/IssuerHash**: hashes for the VPN client to look for the correct certificate for Kerberos authentication.
|
||||
- **Sso/Eku**: comma-separated list of Enhanced Key Usage (EKU) extensions for the VPN client to look for the correct certificate for Kerberos authentication.
|
||||
|
||||
- HealthAttestation CSP (not a requirement) - functions performed by the HealthAttestation CSP include:
|
||||
|
||||
- Collects TPM data used to verify health states
|
||||
- Forwards the data to the Health Attestation Service (HAS)
|
||||
- Provisions the Health Attestation Certificate received from the HAS
|
||||
- Upon request, forwards the Health Attestation Certificate (received from HAS) and related runtime information to the MDM server for verification
|
||||
|
||||
> [!NOTE]
|
||||
>Currently, it is required that certificates be issued from an on-premises CA, and that SSO be enabled in the user’s VPN profile. This will enable the user to obtain Kerberos tickets in order to access resources on-premises. Kerberos currently does not support the use of Azure AD certificates.
|
||||
> Currently, it is required that certificates used for obtaining Kerberos tickets must be issued from an on-premises CA, and that SSO must be enabled in the user’s VPN profile. This will enable the user to access on-premises resources.
|
||||
|
||||
## Client connection flow
|
||||
|
||||
The VPN client side connection flow works as follows:
|
||||
|
||||
|
||||
> [!div class="mx-imgBorder"]
|
||||
> 
|
||||
|
||||
When a VPNv2 Profile is configured with \<DeviceCompliance> \<Enabled>true<\/Enabled> the VPN client uses this connection flow:
|
||||
|
||||
1. The VPN client calls into Windows 10’s Azure AD Token Broker, identifying itself as a VPN client.
|
||||
|
||||
2. The Azure AD Token Broker authenticates to Azure AD and provides it with information about the device trying to connect. The Azure AD Server checks if the device is in compliance with the policies.
|
||||
3. If compliant, Azure AD requests a short-lived certificate
|
||||
|
||||
3. If compliant, Azure AD requests a short-lived certificate.
|
||||
|
||||
4. Azure AD pushes down a short-lived certificate to the Certificate Store via the Token Broker. The Token Broker then returns control back over to the VPN client for further connection processing.
|
||||
|
||||
5. The VPN client uses the Azure AD-issued certificate to authenticate with the VPN server.
|
||||
|
||||
## Configure conditional access
|
||||
|
||||
@ -622,7 +622,7 @@ You can restrict which files are protected by WIP when they are downloaded from
|
||||
|
||||
- [What is Azure Rights Management?](https://docs.microsoft.com/information-protection/understand-explore/what-is-azure-rms)
|
||||
|
||||
- [Create and deploy Windows Information Protection (WIP) app protection policy with Intune and MAM](https://docs.microsoft.com/intune/deploy-use/create-windows-information-protection-policy-with-intune)
|
||||
- [Create a Windows Information Protection (WIP) protection policy using Microsoft Intune](https://docs.microsoft.com/windows/security/information-protection/windows-information-protection/overview-create-wip-policy)
|
||||
|
||||
- [Intune MAM Without Enrollment](https://blogs.technet.microsoft.com/configmgrdogs/2016/02/04/intune-mam-without-enrollment/)
|
||||
|
||||
|
||||
@ -60,7 +60,7 @@ Specify the level of subfolders within an archive folder to scan | Scan > Specif
|
||||
Configure low CPU priority for scheduled scans | Scan > Configure low CPU priority for scheduled scans | Disabled | Not available
|
||||
|
||||
> [!NOTE]
|
||||
>If real-time protection is enabled, files are scanned before they are accessed and executed. The scanning scope includes all files, including those on mounted removable devices such as USB drives.
|
||||
> If real-time protection is turned on, files are scanned before they are accessed and executed. The scanning scope includes all files, including files on mounted removable media, such as USB drives. If the device performing the scan has real-time protection or on-access protection turned on, the scan will also include network shares.
|
||||
|
||||
## Use PowerShell to configure scanning options
|
||||
|
||||
|
||||
@ -13,7 +13,7 @@ ms.author: deniseb
|
||||
ms.custom: nextgen
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.date: 09/28/2020
|
||||
ms.date: 10/06/2020
|
||||
---
|
||||
|
||||
# Manage Microsoft Defender Antivirus updates and apply baselines
|
||||
@ -33,8 +33,7 @@ There are two types of updates related to keeping Microsoft Defender Antivirus u
|
||||
> [!IMPORTANT]
|
||||
> Keeping Microsoft Defender Antivirus up to date is critical to assure your devices have the latest technology and features needed to protect against new malware and attack techniques.
|
||||
> This also applies to devices where Microsoft Defender Antivirus is running in [passive mode](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-antivirus/microsoft-defender-antivirus-compatibility).
|
||||
|
||||
> [!NOTE]
|
||||
>
|
||||
> You can use the below URL to find out what are the current versions:
|
||||
> [https://www.microsoft.com/security/encyclopedia/adlpackages.aspx?action=info](https://www.microsoft.com/security/encyclopedia/adlpackages.aspx?action=info)
|
||||
|
||||
@ -47,48 +46,55 @@ Microsoft Defender Antivirus uses [cloud-delivered protection](utilize-microsoft
|
||||
> Microsoft Defender Antivirus: KB2267602
|
||||
> System Center Endpoint Protection: KB2461484
|
||||
|
||||
The cloud-delivered protection is always on and requires an active connection to the Internet to function, while the security intelligence updates occur on a scheduled cadence (configurable via policy). See the [Utilize Microsoft cloud-provided protection in Microsoft Defender Antivirus](utilize-microsoft-cloud-protection-microsoft-defender-antivirus.md) topic for more details about enabling and configuring cloud-provided protection.
|
||||
Cloud-delivered protection is always on and requires an active connection to the Internet to function. Security intelligence updates occur on a scheduled cadence (configurable via policy). For more information, see [Use Microsoft cloud-provided protection in Microsoft Defender Antivirus](utilize-microsoft-cloud-protection-microsoft-defender-antivirus.md).
|
||||
|
||||
Engine updates are included with the security intelligence updates and are released on a monthly cadence.
|
||||
Engine updates are included with security intelligence updates and are released on a monthly cadence.
|
||||
|
||||
## Product updates
|
||||
|
||||
Microsoft Defender Antivirus requires [monthly updates (KB4052623)](https://support.microsoft.com/help/4052623/update-for-windows-defender-antimalware-platform) (known as "platform updates"), and will receive major feature updates alongside Windows 10 releases.
|
||||
Microsoft Defender Antivirus requires [monthly updates (KB4052623)](https://support.microsoft.com/help/4052623/update-for-windows-defender-antimalware-platform) (known as *platform updates*), and will receive major feature updates alongside Windows 10 releases.
|
||||
|
||||
You can manage the distribution of updates through one of the following methods:
|
||||
|
||||
- [Windows Server Update Service (WSUS)](https://docs.microsoft.com/mem/configmgr/protect/deploy-use/endpoint-definitions-wsus#to-synchronize-endpoint-protection-definition-updates-in-standalone-wsus)
|
||||
- [Microsoft Endpoint Configuration Manager](https://docs.microsoft.com/configmgr/sum/understand/software-updates-introduction)
|
||||
- The usual method you use to deploy Microsoft and Windows updates to endpoints in your network.
|
||||
|
||||
You can manage the distribution of updates through [Windows Server Update Service (WSUS)](https://docs.microsoft.com/mem/configmgr/protect/deploy-use/endpoint-definitions-wsus#to-synchronize-endpoint-protection-definition-updates-in-standalone-wsus), with [Microsoft Endpoint Configuration Manager](https://docs.microsoft.com/configmgr/sum/understand/software-updates-introduction), or in the normal manner that you deploy Microsoft and Windows updates to endpoints in your network.
|
||||
For more information, see [Manage the sources for Microsoft Defender Antivirus protection updates](https://docs.microsoft.com/mem/configmgr/protect/deploy-use/endpoint-definitions-wsus#to-synchronize-endpoint-protection-definition-updates-in-standalone-wsus).
|
||||
|
||||
> [!NOTE]
|
||||
> We release these monthly updates in phases. This results in multiple packages showing up in your WSUS server.
|
||||
> We release these monthly updates in phases. This results in multiple packages visible in your WSUS server.
|
||||
|
||||
## Monthly platform and engine versions
|
||||
|
||||
For information how to update or how to install the platform update, please see [Update for Windows Defender antimalware platform](https://support.microsoft.com/help/4052623/update-for-windows-defender-antimalware-platform).
|
||||
For information how to update or how to install the platform update, see [Update for Windows Defender antimalware platform](https://support.microsoft.com/help/4052623/update-for-windows-defender-antimalware-platform).
|
||||
|
||||
All our updates contain:
|
||||
* performance improvements
|
||||
* serviceability improvements
|
||||
* integration improvements (Cloud, MTP)
|
||||
- performance improvements
|
||||
- serviceability improvements
|
||||
- integration improvements (Cloud, Microsoft 365 Defender)
|
||||
<br/>
|
||||
|
||||
|
||||
<details>
|
||||
<summary> September-2020 (Platform: 4.18.2009.X | Engine: 1.1.17500.4)</summary>
|
||||
<summary> September-2020 (Platform: 4.18.2009.7 | Engine: 1.1.17500.4)</summary>
|
||||
|
||||
 Security intelligence update version: **1.325.10.0**
|
||||
 Released: **October 01, 2020**
|
||||
 Platform: **4.18.2009.X**
|
||||
 Platform: **4.18.2009.7**
|
||||
 Engine: **1.1.17500.4**
|
||||
 Support phase: **Security and Critical Updates**
|
||||
|
||||
### What's new
|
||||
*Admin permissions are required to restore files in quarantine
|
||||
*XML formatted events are now supported
|
||||
*CSP support for ignoring exclusion merge
|
||||
*New management interfaces for:
|
||||
+UDP Inspection
|
||||
+Network Protection on Server 2019
|
||||
+IP Address exclusions for Network Protection
|
||||
*Improved visibility into TPM measurements
|
||||
*Improved Office VBA module scanning
|
||||
- Admin permissions are required to restore files in quarantine
|
||||
- XML formatted events are now supported
|
||||
- CSP support for ignoring exclusion merge
|
||||
- New management interfaces for:
|
||||
- UDP Inspection
|
||||
- Network Protection on Server 2019
|
||||
- IP Address exclusions for Network Protection
|
||||
- Improved visibility into TPM measurements
|
||||
- Improved Office VBA module scanning
|
||||
|
||||
### Known Issues
|
||||
No known issues
|
||||
@ -108,7 +114,7 @@ No known issues
|
||||
* Improved scan event telemetry
|
||||
* Improved behavior monitoring for memory scans
|
||||
* Improved macro streams scanning
|
||||
* Added "AMRunningMode" to Get-MpComputerStatus PowerShell CmdLet
|
||||
* Added `AMRunningMode` to Get-MpComputerStatus PowerShell CmdLet
|
||||
|
||||
### Known Issues
|
||||
No known issues
|
||||
@ -188,7 +194,7 @@ No known issues
|
||||
|
||||
### What's new
|
||||
* WDfilter improvements
|
||||
* Add more actionable event data to ASR detection events
|
||||
* Add more actionable event data to attack surface reduction detection events
|
||||
* Fixed version information in diagnostic data and WMI
|
||||
* Fixed incorrect platform version in UI after platform update
|
||||
* Dynamic URL intel for Fileless threat protection
|
||||
@ -293,8 +299,7 @@ When this update is installed, the device needs the jump package 4.10.2001.10 to
|
||||
</details>
|
||||
|
||||
## Microsoft Defender Antivirus platform support
|
||||
As stated above, platform and engine updates are provided on a monthly cadence.
|
||||
Customers must stay current with the latest platform update to be fully supported. Our support structure is now dynamic, evolving into two phases depending on the availability of the latest platform version:
|
||||
Platform and engine updates are provided on a monthly cadence. To be fully supported, keep current with the latest platform updates. Our support structure is dynamic, evolving into two phases depending on the availability of the latest platform version:
|
||||
|
||||
|
||||
* **Security and Critical Updates servicing phase** - When running the latest platform version, you will be eligible to receive both Security and Critical updates to the anti-malware platform.
|
||||
@ -322,7 +327,7 @@ The below table provides the Microsoft Defender Antivirus platform and engine ve
|
||||
Windows 10 release info: [Windows lifecycle fact sheet](https://support.microsoft.com/help/13853/windows-lifecycle-fact-sheet).
|
||||
|
||||
|
||||
## In this section
|
||||
## See also
|
||||
|
||||
Article | Description
|
||||
---|---
|
||||
|
||||
@ -77,7 +77,7 @@ The following table summarizes the functionality and features that are available
|
||||
|Automatic disabled mode |No |Yes |No |No |No |
|
||||
|
||||
- In Active mode, Microsoft Defender Antivirus is used as the antivirus app on the machine. All configuration made with Configuration Manager, Group Policy, Intune, or other management products will apply. Files are scanned and threats remediated, and detection information are reported in your configuration tool (such as Configuration Manager or the Microsoft Defender Antivirus app on the machine itself).
|
||||
- In Passive mode, Microsoft Defender Antivirus is not used as the antivirus app, and threats are not remediated by Microsoft Defender Antivirus. Files are scanned and reports are provided for threat detections which are shared with the Microsoft Defender ATP service.
|
||||
- In Passive mode, Microsoft Defender Antivirus is not used as the antivirus app, and threats are not remediated by Microsoft Defender Antivirus. Files are scanned and reports are provided for threat detections which are shared with the Microsoft Defender ATP service. Therefore, you might encounter alerts in the Security Center console with Microsoft Defender Antivirus as a source, even when Microsoft Defender Antivirus is in Passive mode.
|
||||
- When [EDR in block mode](../microsoft-defender-atp/edr-in-block-mode.md) (currently in private preview) is turned on, Microsoft Defender Antivirus is not used as the primary antivirus solution, but can still detect and remediate malicious items.
|
||||
- In Automatic disabled mode, Microsoft Defender Antivirus is not used as the antivirus app. Files are not scanned and threats are not remediated.
|
||||
|
||||
|
||||
@ -64,6 +64,9 @@ See [Prevent users from locally modifying policy settings](configure-local-polic
|
||||
|
||||
You can prevent users from pausing scans, which can be helpful to ensure scheduled or on-demand scans are not interrupted by users.
|
||||
|
||||
> [!NOTE]
|
||||
> This setting is not supported on Windows 10.
|
||||
|
||||
### Use Group Policy to prevent users from pausing a scan
|
||||
|
||||
1. On your Group Policy management machine, open the [Group Policy Management Console](https://docs.microsoft.com/previous-versions/windows/desktop/gpmc/group-policy-management-console-portal), right-click the Group Policy Object you want to configure and click **Edit**.
|
||||
|
||||
@ -33,13 +33,15 @@ Check if network protection has been enabled on a local device by using Registry
|
||||
|
||||
1. Select the **Start** button in the task bar and type **regedit** to open Registry editor
|
||||
1. Choose **HKEY_LOCAL_MACHINE** from the side menu
|
||||
1. Navigate through the nested menus to **SOFTWARE** > **Policies** > **Microsoft** > **Windows Defender** > **Policy Manager**
|
||||
1. Navigate through the nested menus to **SOFTWARE** > **Policies** > **Microsoft** > **Windows Defender** > **Windows Defender Exploit Guard** > **Network Protection**
|
||||
1. Select **EnableNetworkProtection** to see the current state of network protection on the device
|
||||
|
||||
* 0, or **Off**
|
||||
* 1, or **On**
|
||||
* 2, or **Audit** mode
|
||||
|
||||
|
||||
|
||||
## Enable network protection
|
||||
|
||||
Enable network protection by using any of these methods:
|
||||
@ -107,7 +109,7 @@ Confirm network protection is enabled on a local computer by using Registry edit
|
||||
|
||||
1. Select **Start** and type **regedit** to open **Registry Editor**.
|
||||
|
||||
2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows Defender\Windows Defender Exploit Guard\Network Protection
|
||||
2. Navigate to **HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows Defender\Windows Defender Exploit Guard\Network Protection**
|
||||
|
||||
3. Select **EnableNetworkProtection** and confirm the value:
|
||||
* 0=Off
|
||||
|
||||
@ -51,6 +51,12 @@ In order to preview new features and provide early feedback, it is recommended t
|
||||
|
||||
### RHEL and variants (CentOS and Oracle Linux)
|
||||
|
||||
- Install `yum-utils` if it isn't installed yet:
|
||||
|
||||
```bash
|
||||
sudo yum install yum-utils
|
||||
```
|
||||
|
||||
- Note your distribution and version, and identify the closest entry for it under `https://packages.microsoft.com/config/`.
|
||||
|
||||
In the below commands, replace *[distro]* and *[version]* with the information you've identified:
|
||||
@ -74,12 +80,6 @@ In order to preview new features and provide early feedback, it is recommended t
|
||||
sudo rpm --import http://packages.microsoft.com/keys/microsoft.asc
|
||||
```
|
||||
|
||||
- Install `yum-utils` if it isn't installed yet:
|
||||
|
||||
```bash
|
||||
sudo yum install yum-utils
|
||||
```
|
||||
|
||||
- Download and make usable all the metadata for the currently enabled yum repositories:
|
||||
|
||||
```bash
|
||||
|
||||
@ -14,7 +14,9 @@ author: denisebmsft
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.collection:
|
||||
- M365-security-compliance
|
||||
- m365solution-scenario
|
||||
ms.topic: article
|
||||
ms.date: 09/22/2020
|
||||
ms.reviewer: chventou
|
||||
|
||||
@ -14,7 +14,9 @@ author: denisebmsft
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.collection:
|
||||
- M365-security-compliance
|
||||
- m365solution-scenario
|
||||
ms.topic: article
|
||||
ms.date: 09/22/2020
|
||||
ms.reviewer: chventou
|
||||
|
||||
@ -14,7 +14,9 @@ author: denisebmsft
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.collection:
|
||||
- M365-security-compliance
|
||||
- m365solution-scenario
|
||||
ms.topic: article
|
||||
ms.date: 09/22/2020
|
||||
ms.reviewer: chventou
|
||||
|
||||
@ -14,7 +14,9 @@ author: denisebmsft
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.collection:
|
||||
- M365-security-compliance
|
||||
- m365solution-scenario
|
||||
ms.topic: article
|
||||
ms.date: 09/22/2020
|
||||
ms.reviewer: chventou
|
||||
|
||||
@ -14,7 +14,9 @@ author: denisebmsft
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.collection:
|
||||
- M365-security-compliance
|
||||
- m365solution-scenario
|
||||
ms.topic: conceptual
|
||||
ms.date: 09/22/2020
|
||||
ms.reviewer: chventou
|
||||
|
||||
@ -17,6 +17,7 @@ audience: ITPro
|
||||
ms.collection:
|
||||
- M365-security-compliance
|
||||
- m365solution-McAfeemigrate
|
||||
- m365solution-scenario
|
||||
ms.custom: migrationguides
|
||||
ms.topic: article
|
||||
ms.date: 09/24/2020
|
||||
|
||||
@ -17,6 +17,7 @@ audience: ITPro
|
||||
ms.collection:
|
||||
- M365-security-compliance
|
||||
- m365solution-mcafeemigrate
|
||||
- m365solution-scenario
|
||||
ms.topic: article
|
||||
ms.custom: migrationguides
|
||||
ms.date: 09/22/2020
|
||||
|
||||
@ -17,6 +17,7 @@ audience: ITPro
|
||||
ms.collection:
|
||||
- M365-security-compliance
|
||||
- m365solution-mcafeemigrate
|
||||
- m365solution-scenario
|
||||
ms.topic: article
|
||||
ms.custom: migrationguides
|
||||
ms.date: 09/22/2020
|
||||
|
||||
@ -70,6 +70,18 @@ Beta versions of macOS are not supported. macOS Sierra (10.12) support ended on
|
||||
|
||||
After you've enabled the service, you may need to configure your network or firewall to allow outbound connections between it and your endpoints.
|
||||
|
||||
### Licensing requirements
|
||||
|
||||
Microsoft Defender Advanced Threat Protection for Mac requires one of the following Microsoft Volume Licensing offers:
|
||||
|
||||
- Microsoft 365 E5 (M365 E5)
|
||||
- Microsoft 365 E5 Security
|
||||
- Microsoft 365 A5 (M365 A5)
|
||||
|
||||
> [!NOTE]
|
||||
> Eligible licensed users may use Microsoft Defender Advanced Threat Protection on up to five concurrent devices.
|
||||
> Microsoft Defender Advanced Threat Protection is also available for purchase from a Cloud Solution Provider (CSP). When purchased via a CSP, it does not require Microsoft Volume Licensing offers listed.
|
||||
|
||||
### Network connections
|
||||
|
||||
The following downloadable spreadsheet lists the services and their associated URLs that your network must be able to connect to. You should ensure that there are no firewall or network filtering rules that would deny access to these URLs, or you may need to create an *allow* rule specifically for them.
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
ms.localizationpriority: medium
|
||||
ms.collection:
|
||||
- M365-security-compliance
|
||||
- m365solution-scenario
|
||||
ms.custom: migrationguides
|
||||
ms.reviewer: chriggs, depicker, yongrhee
|
||||
f1.keywords: NOCSH
|
||||
|
||||
@ -15,6 +15,7 @@ audience: ITPro
|
||||
ms.collection:
|
||||
- M365-security-compliance
|
||||
- m365solution-endpointprotect
|
||||
- m365solution-scenario
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
|
||||
@ -15,6 +15,7 @@ audience: ITPro
|
||||
ms.collection:
|
||||
- M365-security-compliance
|
||||
- m365solution-endpointprotect
|
||||
- m365solution-scenario
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
|
||||
@ -15,6 +15,7 @@ audience: ITPro
|
||||
ms.collection:
|
||||
- M365-security-compliance
|
||||
- m365solution-endpointprotect
|
||||
- m365solution-scenario
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
|
||||
@ -16,6 +16,7 @@ audience: ITPro
|
||||
ms.collection:
|
||||
- M365-security-compliance
|
||||
- m365solution-endpointprotect
|
||||
- m365solution-scenario
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
|
||||
@ -16,6 +16,7 @@ audience: ITPro
|
||||
ms.collection:
|
||||
- M365-security-compliance
|
||||
- m365solution-endpointprotect
|
||||
- m365solution-scenario
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
|
||||
@ -77,8 +77,11 @@ None. Changes to this policy setting become effective without a computer restart
|
||||
### <a href="" id="bkmk-impleconsiderations"></a>Implementation considerations
|
||||
|
||||
Implementation of this policy setting is dependent on your operational environment. You should consider threat vectors, deployed operating systems, and deployed apps, for example:
|
||||
|
||||
- The likelihood of an account theft or a DoS attack is based on the security design for your systems and environment. You should set the account lockout threshold in consideration of the known and perceived risk of those threats.
|
||||
|
||||
- When negotiating encryption types between clients, servers, and domain controllers, the Kerberos protocol can automatically retry account sign-in attempts that count toward the threshold limits that you set in this policy setting. In environments where different versions of the operating system are deployed, encryption type negotiation increases.
|
||||
|
||||
- Not all apps that are used in your environment effectively manage how many times a user can attempt to sign-in. For instance, if a connection drops repeatedly when a user is running the app, all subsequent failed sign-in attempts count toward the account lockout threshold.
|
||||
|
||||
For more information about Windows security baseline recommendations for account lockout, see [Configuring Account Lockout](https://blogs.technet.microsoft.com/secguide/2014/08/13/configuring-account-lockout/).
|
||||
@ -87,22 +90,31 @@ For more information about Windows security baseline recommendations for account
|
||||
|
||||
This section describes how an attacker might exploit a feature or its configuration, how to implement the countermeasure, and the possible negative consequences of countermeasure implementation.
|
||||
|
||||
> [!NOTE]
|
||||
> A lockout threshold policy will apply to both local member computer users and domain users, in order to allow mitigation of issues as described under "Vulnerability". The built-in Administrator account, however, whilst a highly privileged account, has a different risk profile and is excluded from this policy. This ensures there is no scenario where an administrator cannot sign in to remediate an issue. As an administrator, there are additional mitigation strategies available, such as a strong password. See also [Appendix D: Securing Built-In Administrator Accounts in Active Directory](https://docs.microsoft.com/windows-server/identity/ad-ds/plan/security-best-practices/appendix-d--securing-built-in-administrator-accounts-in-active-directory).
|
||||
|
||||
### Vulnerability
|
||||
|
||||
Brute force password attacks can use automated methods to try millions of password combinations for any user account. The effectiveness of such attacks can be almost eliminated if you limit the number of failed sign-in attempts that can be performed.
|
||||
However, a DoS attack could be performed on a domain that has an account lockout threshold configured. An attacker could programmatically attempt a series of password attacks against all users in the organization. If the number of attempts is greater than the account lockout threshold, the attacker might be able to lock every account without needing any special privileges or being authenticated in the network.
|
||||
|
||||
> **Note:** Offline password attacks are not countered by this policy setting.
|
||||
> [!NOTE]
|
||||
> Offline password attacks are not countered by this policy setting.
|
||||
|
||||
|
||||
### <a href="" id="bkmk-countermeasure"></a>Countermeasure
|
||||
|
||||
Because vulnerabilities can exist when this value is configured and when it is not configured, two distinct countermeasures are defined. Organizations should weigh the choice between the two, based on their identified threats and the risks that they want to mitigate. The two countermeasure options are:
|
||||
|
||||
- Configure the **Account lockout threshold** setting to 0. This configuration ensures that accounts will not be locked, and it will prevent a DoS attack that intentionally attempts to lock accounts. This configuration also helps reduce Help Desk calls because users cannot accidentally lock themselves out of their accounts. Because it does not prevent a brute force attack, this configuration should be chosen only if both of the following criteria are explicitly met:
|
||||
|
||||
- The password policy setting requires all users to have complex passwords of 8 or more characters.
|
||||
- A robust audit mechanism is in place to alert administrators when a series of failed sign-ins occur in the environment.
|
||||
|
||||
- Configure the **Account lockout threshold** policy setting to a sufficiently high value to provide users with the ability to accidentally mistype their password several times before the account is locked, but ensure that a brute force password attack still locks the account.
|
||||
|
||||
[Windows security baselines](https://docs.microsoft.com/windows/security/threat-protection/windows-security-baselines) recommend configuring a threshold of 10 invalid sign-in attempts, which prevents accidental account lockouts and reduces the number of Help Desk calls, but does not prevent a DoS attack.
|
||||
|
||||
Using this type of policy must be accompanied by a process to unlock locked accounts. It must be possible to implement this policy whenever it is needed to help mitigate massive lockouts caused by an attack on your systems.
|
||||
|
||||
### Potential impact
|
||||
|
||||
@ -76,7 +76,7 @@ Types of password attacks include dictionary attacks (which attempt to use commo
|
||||
|
||||
### Countermeasure
|
||||
|
||||
Configure the **** policy setting to a value of 8 or more. If the number of characters is set to 0, no password will be required.
|
||||
Configure the **Minimum password length** policy setting to a value of 8 or more. If the number of characters is set to 0, no password will be required.
|
||||
|
||||
In most environments, we recommend an eight-character password because it is long enough to provide adequate security, but not too difficult for users to easily remember. This configuration provides adequate defense against a brute force attack. Using the [Password must meet complexity requirements](password-must-meet-complexity-requirements.md) policy setting in addition to the **Minimum password length** setting helps reduce the possibility of a dictionary attack.
|
||||
|
||||
|
||||
@ -44,10 +44,12 @@ Note that prior to Windows 10, version 1709, Windows Defender Application Contro
|
||||
|
||||
### WDAC System Requirements
|
||||
|
||||
WDAC policies can only be created on devices running Windows 10 build 1903+ on any SKU, pre-1903 Windows 10 Enterprise, or Windows Server 2016 and above.
|
||||
WDAC policies can be created on any client edition of Windows 10 build 1903+ or on Windows Server 2016 and above.
|
||||
|
||||
WDAC policies can be applied to devices running any edition of Windows 10 or Windows Server 2016 and above via a Mobile Device Management (MDM) solution like Intune, a management interface like Configuration Manager, or a script host like PowerShell. Group Policy can also be used to deploy WDAC policies to Windows 10 Enterprise edition or Windows Server 2016 and above, but cannot deploy policies to devices running non-Enterprise SKUs of Windows 10.
|
||||
|
||||
For more information on which individual WDAC features are available on which WDAC builds, see [WDAC feature availability](feature-availability.md).
|
||||
|
||||
## AppLocker
|
||||
|
||||
AppLocker was introduced with Windows 7 and allows organizations to control which applications are allowed to run on their Windows clients. AppLocker helps to prevent end users from running unapproved software on their computers, but it does not meet the servicing criteria for being a security feature.
|
||||
@ -65,12 +67,13 @@ AppLocker policies can be deployed using Group Policy or MDM.
|
||||
|
||||
## Choose when to use WDAC or AppLocker
|
||||
|
||||
Generally, it is recommended that customers who are able to implement application control using WDAC rather than AppLocker do so. WDAC is undergoing continual improvements and will be getting added support from Microsoft management platforms. AppLocker is a legacy technology which will continue to receive security fixes but will not undergo new feature improvements.
|
||||
Generally, it is recommended that customers who are able to implement application control using WDAC rather than AppLocker do so. WDAC is undergoing continual improvements and will be getting added support from Microsoft management platforms. Although AppLocker will continue to receive security fixes, it will not undergo new feature improvements.
|
||||
|
||||
In some cases, however, AppLocker may be the more appropriate technology for your organization. AppLocker is best when:
|
||||
|
||||
- You have a mixed Windows operating system (OS) environment and need to apply the same policy controls to Windows 10 and earlier versions of the OS.
|
||||
- You need to apply different policies for different users or groups on shared computers.
|
||||
- You do not want to enforce application control on application files such as DLLs or drivers.
|
||||
|
||||
AppLocker can also be deployed as a complement to WDAC to add user- or group-specific rules for shared device scenarios where it is important to prevent some users from running specific apps.
|
||||
As a best practice, you should enforce WDAC at the most restrictive level possible for your organization, and then you can use AppLocker to further fine-tune the restrictions.
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user