From e37b6e4272aafa018039e15b1f18e7cafafda760 Mon Sep 17 00:00:00 2001 From: Gary Moore Date: Tue, 19 Oct 2021 15:05:20 -0700 Subject: [PATCH] Acrolinx: "Powershell" --- ...e-authorized-apps-deployed-with-a-managed-installer.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/windows/security/threat-protection/windows-defender-application-control/configure-authorized-apps-deployed-with-a-managed-installer.md b/windows/security/threat-protection/windows-defender-application-control/configure-authorized-apps-deployed-with-a-managed-installer.md index b33350aaa1..a31d84c88e 100644 --- a/windows/security/threat-protection/windows-defender-application-control/configure-authorized-apps-deployed-with-a-managed-installer.md +++ b/windows/security/threat-protection/windows-defender-application-control/configure-authorized-apps-deployed-with-a-managed-installer.md @@ -84,19 +84,19 @@ Currently, neither the AppLocker policy creation UI in GPO Editor nor the PowerS 2. Manually rename the rule collection to ManagedInstaller - Change + Change: ```powershell ``` - to + to: ```powershell ``` -An example of a valid Managed Installer rule collection, using Microsoft Endpoint Config Manager (MEMCM), MEM (Intune), Powershell, and PowerShell ISE, is shown below. Remove any rules that you do not wish to designate as a Managed Installer. +An example of a valid Managed Installer rule collection, using Microsoft Endpoint Config Manager (MEMCM), MEM (Intune), PowerShell, and PowerShell ISE, is shown below. Remove any rules that you do not wish to designate as a Managed Installer. ```xml @@ -197,7 +197,7 @@ Below are steps to create a WDAC policy that allows Windows to boot and enables Set-CIPolicyIdInfo -FilePath -PolicyName "" -ResetPolicyID ``` -3. Set Option 13 (Enabled:Managed Installer) +3. Set Option 13 (Enabled:Managed Installer). ```powershell Set-RuleOption -FilePath -Option 13