mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-13 13:57:22 +00:00
Merge pull request #8117 from jsuther1974/WDAC-Docs
Fixed WDAC documentation issues
This commit is contained in:
commit
1f56c28c3b
@ -9,7 +9,7 @@ ms.reviewer: jogeurte
|
|||||||
ms.author: jogeurte
|
ms.author: jogeurte
|
||||||
ms.manager: jsuther
|
ms.manager: jsuther
|
||||||
manager: aaroncz
|
manager: aaroncz
|
||||||
ms.date: 02/02/2023
|
ms.date: 04/04/2023
|
||||||
ms.technology: itpro-security
|
ms.technology: itpro-security
|
||||||
ms.topic: article
|
ms.topic: article
|
||||||
ms.localizationpriority: medium
|
ms.localizationpriority: medium
|
||||||
@ -47,7 +47,7 @@ For **single policy format WDAC policies**, in addition to the two locations abo
|
|||||||
|
|
||||||
## Known issues
|
## Known issues
|
||||||
|
|
||||||
### Managed Installer and ISG will cause garrulous events
|
### Managed Installer and ISG may cause excessive events
|
||||||
|
|
||||||
When Managed Installer and ISG are enabled, 3091 and 3092 events will be logged when a file didn't have Managed Installer or ISG authorization, regardless of whether the file was allowed. These events have been moved to the verbose channel beginning with the September 2022 Update Preview since the events don't indicate an issue with the policy.
|
When Managed Installer and ISG are enabled, 3091 and 3092 events will be logged when a file didn't have Managed Installer or ISG authorization, regardless of whether the file was allowed. These events have been moved to the verbose channel beginning with the September 2022 Update Preview since the events don't indicate an issue with the policy.
|
||||||
|
|
||||||
|
@ -10,10 +10,10 @@ ms.pagetype: security
|
|||||||
ms.localizationpriority: medium
|
ms.localizationpriority: medium
|
||||||
audience: ITPro
|
audience: ITPro
|
||||||
author: vinaypamnani-msft
|
author: vinaypamnani-msft
|
||||||
ms.reviewer: isbrahm
|
ms.reviewer: jsuther
|
||||||
ms.author: vinpa
|
ms.author: vinpa
|
||||||
manager: aaroncz
|
manager: aaroncz
|
||||||
ms.date: 09/30/2020
|
ms.date: 04/04/2023
|
||||||
ms.custom: asr
|
ms.custom: asr
|
||||||
ms.technology: itpro-security
|
ms.technology: itpro-security
|
||||||
ms.topic: article
|
ms.topic: article
|
||||||
@ -51,7 +51,7 @@ Prior to Windows 10 version 1709, Windows Defender Application Control was known
|
|||||||
|
|
||||||
Windows Defender Application Control (WDAC) policies can be created on any client edition of Windows 10 build 1903+, or Windows 11, or on Windows Server 2016 and above.
|
Windows Defender Application Control (WDAC) policies can be created on any client edition of Windows 10 build 1903+, or Windows 11, or on Windows Server 2016 and above.
|
||||||
|
|
||||||
WDAC policies can be applied to devices running any edition of Windows 10, Windows 11, or Windows Server 2016 and above, via a Mobile Device Management (MDM) solution, for example, Intune; a management interface such as Configuration Manager; or a script host such as PowerShell. Group Policy can also be used to deploy WDAC policies to Windows 10 and Windows 11 Enterprise edition, or Windows Server 2016 and above, but can't deploy policies to devices running non-Enterprise SKUs of Windows 10.
|
WDAC policies can be applied to devices running any edition of Windows 10, Windows 11, or Windows Server 2016 and above, via a Mobile Device Management (MDM) solution, for example, Intune; a management interface such as Configuration Manager; or a script host such as PowerShell. Group Policy can also be used to deploy WDAC policies, but is limited to single-policy format policies that work on Windows Server 2016 and 2019.
|
||||||
|
|
||||||
For more information on which individual WDAC features are available on specific WDAC builds, see [WDAC feature availability](feature-availability.md).
|
For more information on which individual WDAC features are available on specific WDAC builds, see [WDAC feature availability](feature-availability.md).
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user