From ce67a7a1615992919bbac1e0cb888d3081ab4ff7 Mon Sep 17 00:00:00 2001 From: Justin Hall Date: Wed, 28 Mar 2018 12:53:43 -0700 Subject: [PATCH] added link to blog post --- .../device-guard/deploy-managed-installer-for-device-guard.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/windows/security/threat-protection/device-guard/deploy-managed-installer-for-device-guard.md b/windows/security/threat-protection/device-guard/deploy-managed-installer-for-device-guard.md index c3cefa3e19..b97a44ed0e 100644 --- a/windows/security/threat-protection/device-guard/deploy-managed-installer-for-device-guard.md +++ b/windows/security/threat-protection/device-guard/deploy-managed-installer-for-device-guard.md @@ -45,7 +45,9 @@ There are three primary steps to keep in mind: The identity of the managed installer executable(s) is specified in an AppLocker policy in a Managed Installer rule collection. Currently the AppLocker policy creation UI and cmdlets do not allow for directly specifying rules for the Managed Installer rule collection, however a text editor can be used to make the simple changes needed to an EXE or DLL rule collection policy to specify Type="ManagedInstaller". -An example of a valid Managed Installer rule collection is shown below. +An example of a valid Managed Installer rule collection is shown below. +For more information about creating an AppLocker policy that includes a managed installer and configuring client devices, see [Simplify application whitelisting with Configuration Manager and Windows 10](https://cloudblogs.microsoft.com/enterprisemobility/2016/06/20/configmgr-as-a-managed-installer-with-win10/). + ```code