From bc14cfad4894ad080727512fa8ddce437e616e60 Mon Sep 17 00:00:00 2001 From: MaratMussabekov <48041687+MaratMussabekov@users.noreply.github.com> Date: Tue, 30 Jul 2019 15:52:37 +0500 Subject: [PATCH] Update applocker-csp.md --- .../client-management/mdm/applocker-csp.md | 20 ++++--------------- 1 file changed, 4 insertions(+), 16 deletions(-) diff --git a/windows/client-management/mdm/applocker-csp.md b/windows/client-management/mdm/applocker-csp.md index 7018d14a99..a56feb5fbf 100644 --- a/windows/client-management/mdm/applocker-csp.md +++ b/windows/client-management/mdm/applocker-csp.md @@ -156,22 +156,8 @@ Each of the previous nodes contains one or more of the following leaf nodes:
Policy
Policy nodes define the policy for launching executables, Windows Installer files, scripts, store apps, and DLL files. The contents of a given Policy node is precisely the XML format for a RuleCollection node in the corresponding AppLocker XML policy.
-Policy nodes are a Base64-encoded blob of the binary policy representation. The binary policy may be signed or unsigned.
-For CodeIntegrity/Policy, you can use the certutil -encode command line tool to encode the data to base-64.
-Here is a sample certutil invocation:
- -``` -certutil -encode WinSiPolicy.p7b WinSiPolicy.cer -``` - -An alternative to using certutil would be to use the following PowerShell invocation:
- -``` -[Convert]::ToBase64String($(Get-Content -Encoding Byte -ReadCount 0 -PathIf you are using hybrid MDM management with System Center Configuration Manager or using Intune, ensure that you are using Base64 as the Data type when using Custom OMA-URI functionality to apply the Code Integrity policy.
-Data type is string. Supported operations are Get, Add, Delete, and Replace.
For nodes, other than CodeIntegrity, policy leaf data type is string. Supported operations are Get, Add, Delete, and Replace.
+For CodeIntegrity/Policy, data type is Base64. Supported operations are Get, Add, Delete, and Replace.
EnforcementMode