2.4 KiB
title, description, ms.author, ms.localizationpriority, ms.topic, ms.prod, ms.technology, author, ms.date, ms.reviewer, manager
title | description | ms.author | ms.localizationpriority | ms.topic | ms.prod | ms.technology | author | ms.date | ms.reviewer | manager |
---|---|---|---|---|---|---|---|---|---|---|
Policy CSP - ADMX_DeviceGuard | Policy CSP - ADMX_DeviceGuard | dansimp | medium | article | w10 | windows | manikadhiman | 09/08/2021 | dansimp |
Policy CSP - ADMX_DeviceGuard
ADMX_DeviceGuard policies
ADMX_DeviceGuard/ConfigCIPolicy
Edition | Windows 10 | Windows 11 |
---|---|---|
Home | No | No |
Pro | No | No |
Business | No | No |
Enterprise | Yes | Yes |
Education | Yes | Yes |
[!div class = "checklist"]
- Device
This policy setting lets you deploy a Code Integrity Policy to a machine to control what is allowed to run on that machine.
If you deploy a Code Integrity Policy, Windows will restrict what can run in both kernel mode and on the Windows Desktop based on the policy.
To enable this policy the machine must be rebooted.
The file path must be either a UNC path (for example, \\ServerName\ShareName\SIPolicy.p7b
),
or a locally valid path (for example, C:\FolderName\SIPolicy.p7b)
.
The local machine account (LOCAL SYSTEM) must have access permission to the policy file.
If using a signed and protected policy then disabling this policy setting doesn't remove the feature from the computer. Instead, you must either:
- First update the policy to a non-protected policy and then disable the setting.
- Disable the setting and then remove the policy from each computer, with a physically present user.
ADMX Info:
- GP Friendly name: Deploy Windows Defender Application Control
- GP name: ConfigCIPolicy
- GP path: Windows Components/DeviceGuard!DeployConfigCIPolicy
- GP ADMX file name: DeviceGuard.admx