This commit is contained in:
greg-lindsay 2021-07-19 12:37:00 -07:00
commit a7a2dc06c6
2 changed files with 4 additions and 4 deletions

View File

@ -14,7 +14,7 @@ author: jsuther1974
ms.reviewer: jogeurte ms.reviewer: jogeurte
ms.author: dansimp ms.author: dansimp
manager: dansimp manager: dansimp
ms.date: 11/13/2020 ms.date: 07/19/2021
ms.technology: mde ms.technology: mde
--- ---
@ -25,7 +25,7 @@ ms.technology: mde
- Windows 10 version 1903 and above - Windows 10 version 1903 and above
- Windows Server 2022 and above - Windows Server 2022 and above
Prior to Windows 10 1903, WDAC only supported a single active on a system at any given time. This significantly limited customers in situations where multiple policies with different intents would be useful. Beginning with Windows 10 version 1903, WDAC supports up to 32 active policies on a device at once in order to enable the following scenarios: Prior to Windows 10 1903, WDAC only supported a single active policy on a system at any given time. This significantly limited customers in situations where multiple policies with different intents would be useful. Beginning with Windows 10 version 1903, WDAC supports up to 32 active policies on a device at once in order to enable the following scenarios:
1. Enforce and Audit Side-by-Side 1. Enforce and Audit Side-by-Side
- To validate policy changes before deploying in enforcement mode, users can now deploy an audit-mode base policy side by side with an existing enforcement-mode base policy - To validate policy changes before deploying in enforcement mode, users can now deploy an audit-mode base policy side by side with an existing enforcement-mode base policy

View File

@ -10,7 +10,7 @@ ms.reviewer: jogeurte
ms.author: jogeurte ms.author: jogeurte
ms.manager: jsuther ms.manager: jsuther
manager: dansimp manager: dansimp
ms.date: 04/14/2021 ms.date: 07/19/2021
ms.technology: mde ms.technology: mde
ms.topic: article ms.topic: article
ms.localizationpriority: medium ms.localizationpriority: medium
@ -41,4 +41,4 @@ For more information on using MEMCM's native WDAC policies, see [Windows Defende
## Deploy custom WDAC policies using Packages/Programs or Task Sequences ## Deploy custom WDAC policies using Packages/Programs or Task Sequences
Using MEMCM's built-in policies can be a helpful starting point, but customers may find the available circle-of-trust options available in MEMCM too limiting. To define your own circle-of-trust, you can use MEMCM to deploy custom WDAC policies using [script-based deployment](deploy-wdac-policies-with-script.md) via Software Distribution Packages and Programs or Operating System Deployment Task Sequences. Using MEMCM's built-in policies can be a helpful starting point, but customers may find the circle-of-trust options available in MEMCM too limiting. To define your own circle-of-trust, you can use MEMCM to deploy custom WDAC policies using [script-based deployment](deploy-wdac-policies-with-script.md) via Software Distribution Packages and Programs or Operating System Deployment Task Sequences.