mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-21 05:13:40 +00:00
Updated instances of MEMCM to Configuration Manager and click to select
This commit is contained in:
@ -29,7 +29,7 @@ ms.localizationpriority: medium
|
|||||||
|
|
||||||
You can use Microsoft Endpoint Configuration Manager to configure Windows Defender Application Control (WDAC) on client machines.
|
You can use Microsoft Endpoint Configuration Manager to configure Windows Defender Application Control (WDAC) on client machines.
|
||||||
|
|
||||||
## Use MEMCM's built-in policies
|
## Use Configuration Manager's built-in policies
|
||||||
|
|
||||||
Microsoft Endpoint Configuration Manager includes native support for WDAC, which allows you to configure Windows 10 and Windows 11 client computers with a policy that will only allow:
|
Microsoft Endpoint Configuration Manager includes native support for WDAC, which allows you to configure Windows 10 and Windows 11 client computers with a policy that will only allow:
|
||||||
|
|
||||||
@ -41,22 +41,22 @@ Microsoft Endpoint Configuration Manager includes native support for WDAC, which
|
|||||||
|
|
||||||
Note that Configuration Manager does not remove policies once deployed. To stop enforcement, you should switch the policy to audit mode, which will produce the same effect. If you want to disable Windows Defender Application Control (WDAC) altogether (including audit mode), you can deploy a script to delete the policy file from disk, and either trigger a reboot or wait for the next reboot.
|
Note that Configuration Manager does not remove policies once deployed. To stop enforcement, you should switch the policy to audit mode, which will produce the same effect. If you want to disable Windows Defender Application Control (WDAC) altogether (including audit mode), you can deploy a script to delete the policy file from disk, and either trigger a reboot or wait for the next reboot.
|
||||||
|
|
||||||
### Create a WDAC Policy in MEMCM
|
### Create a WDAC Policy in Configuration Manager
|
||||||
|
|
||||||
1. Select **Asset and Compliance** > **Endpoint Protection** > **Windows Defender Application Control** > **Create Application Control Policy**
|
1. Select **Asset and Compliance** > **Endpoint Protection** > **Windows Defender Application Control** > **Create Application Control Policy**
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
2. Enter the name of the policy > **Next**
|
2. Enter the name of the policy > **Next**
|
||||||
3. Enable **Enforce a restart of devices so that this policy can be enforced for all processes**
|
3. Enable **Enforce a restart of devices so that this policy can be enforced for all processes**
|
||||||
4. Select the mode which you want the policy to run (Enforcement enabled / Audit Only)
|
4. Select the mode which you want the policy to run (Enforcement enabled / Audit Only)
|
||||||
5. Click **Next**
|
5. Click **Next**
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
6. Click **Add** to begin creating rules for trusted software
|
6. Select **Add** to begin creating rules for trusted software
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
7. Select **File** or **Folder** to create a path rule > **Browse**
|
7. Select **File** or **Folder** to create a path rule > **Browse**
|
||||||
|
|
||||||
@ -69,13 +69,13 @@ Note that Configuration Manager does not remove policies once deployed. To stop
|
|||||||
9. Select **OK** to add the rule to the table of trusted files or folder
|
9. Select **OK** to add the rule to the table of trusted files or folder
|
||||||
10. Select **Next** to navigate to the summary page > **Close**
|
10. Select **Next** to navigate to the summary page > **Close**
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
### Deploy the WDAC Policy in MEMCM
|
### Deploy the WDAC Policy in Configuration Manager
|
||||||
|
|
||||||
1. Right-click the newly created policy > **Deploy Application Control Policy**
|
1. Right-click the newly created policy > **Deploy Application Control Policy**
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
2. Select **Browse**
|
2. Select **Browse**
|
||||||
|
|
||||||
@ -91,7 +91,7 @@ Note that Configuration Manager does not remove policies once deployed. To stop
|
|||||||
|
|
||||||
For more information on using Configuration Manager's native WDAC policies, see [Windows Defender Application Control management with Configuration Manager](/mem/configmgr/protect/deploy-use/use-device-guard-with-configuration-manager).
|
For more information on using Configuration Manager's native WDAC policies, see [Windows Defender Application Control management with Configuration Manager](/mem/configmgr/protect/deploy-use/use-device-guard-with-configuration-manager).
|
||||||
|
|
||||||
The entire WDAC in MEMCM Lab Paper is available for download [here](../pdfs/WDAC-Deploy-WDAC-using-MEMCM.pdf).
|
The entire WDAC in Configuration Manager Lab Paper is available for download [here](/pdfs/WDAC-Deploy-WDAC-using-MEMCM.pdf).
|
||||||
|
|
||||||
## Deploy custom WDAC policies using Packages/Programs or Task Sequences
|
## Deploy custom WDAC policies using Packages/Programs or Task Sequences
|
||||||
|
|
||||||
|
Reference in New Issue
Block a user