Merged PR 6733: Merge app-v to master

This commit is contained in:
Justin Hall
2018-03-29 13:16:47 +00:00
2 changed files with 6 additions and 4 deletions

View File

@ -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
<RuleCollection Type="ManagedInstaller" EnforcementMode="AuditOnly">