mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 05:17:22 +00:00
Merge branch 'master' into MDBranch20H2MixedRealityPolicyCSP
This commit is contained in:
ManikaDhiman
commit
4dd0e20d6a
@ -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)
|
||||
@ -4921,27 +4921,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
|
||||
|
||||
|
||||
@ -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)
|
||||
|
||||
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 |
@ -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
|
||||
|
||||
|
||||
@ -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.
|
||||
> [!NOTE]
|
||||
> 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/)
|
||||
|
||||
|
||||
@ -74,39 +74,14 @@ All our updates contain:
|
||||
- serviceability improvements
|
||||
- integration improvements (Cloud, Microsoft 365 Defender)
|
||||
<br/>
|
||||
<details>
|
||||
<summary> September-2020 (Platform: 4.18.2009.x | Engine: 1.1.17500.4)</summary>
|
||||
|
||||
 Security intelligence update version: **1.323.2254.0**
|
||||
 Released: **October 6, 2020**
|
||||
 Platform: **4.18.2009.x**
|
||||
 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: <br/>
|
||||
- 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
|
||||
<br/>
|
||||
</details>
|
||||
|
||||
|
||||
<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**
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
@ -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