From 5357026a1593e728c6017a9b5d1a236cda404f9b Mon Sep 17 00:00:00 2001 From: Andreas Stenhall Date: Wed, 16 Oct 2019 08:38:01 +0200 Subject: [PATCH] Update deploy-multiple-windows-defender-application-control-policies.md --- ...oy-multiple-windows-defender-application-control-policies.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/windows-defender-application-control/deploy-multiple-windows-defender-application-control-policies.md b/windows/security/threat-protection/windows-defender-application-control/deploy-multiple-windows-defender-application-control-policies.md index a9c5251d57..57220733e6 100644 --- a/windows/security/threat-protection/windows-defender-application-control/deploy-multiple-windows-defender-application-control-policies.md +++ b/windows/security/threat-protection/windows-defender-application-control/deploy-multiple-windows-defender-application-control-policies.md @@ -52,7 +52,7 @@ New-CIPolicy -MultiplePolicyFormat -foo –bar Optionally, you can choose to make the new base policy supplementable (allow supplemental policies). ```powershell -Set-RuleOption -FilePath 17 +Set-RuleOption -FilePath -Option 17 ``` For signed base policies that are being made supplementable, you need to ensure that supplemental signers are defined. Use the "Supplemental" switch in Add-SignerRule to provide supplemental signers.