Using the AppLocker Windows PowerShell Cmdlets
Updated: November 9, 2009
Applies To: Windows 7, Windows Server 2008 R2
This topic describes how each AppLocker Windows PowerShell cmdlet can help you administer your AppLocker application control policies.
AppLocker Windows PowerShell cmdlets
The five AppLocker cmdlets are designed to streamline the administration of an AppLocker policy. They can be used to help create, test, maintain, and troubleshoot an AppLocker policy. The cmdlets are intended to be used in conjunction with the AppLocker user interface that is accessed through the Microsoft Management Console (MMC) snap-in extension to the Local Security Policy snap-in and Group Policy Management Console.
To edit or update a Group Policy Object (GPO) by using the AppLocker cmdlets, you must have Edit Setting permission. By default, members of the Domain Admins group, the Enterprise Admins group, and the Group Policy Creator Owners group have this permission. To perform tasks by using the Local Security policy snap-in, you must be a member of the local Administrators group, or equivalent, on the computer.
Import the AppLocker PowerShell cmdlet module
To use the AppLocker cmdlets, you must first import the AppLocker module by using the following command at the Windows PowerShell command prompt:
C:\PS> Import-Module AppLocker. Scripting must be enabled on the computer.
For information about Windows PowerShell, see the Windows PowerShell Help file (WindowsPowerShellHelp.chm) on computers running Windows Server 2008 R2 or Windows 7.
Retrieve application information
The Get-AppLockerFileInformation (http://go.microsoft.com/fwlink/?LinkId=169154) cmdlet retrieves the AppLocker file information from a list of files or from an event log. File information that is retrieved can include publisher information, file hash information, and file path information. File information from an event log may not contain all of these fields. Files that are not signed do not have any publisher information.
Set AppLocker policy
The Set-AppLockerPolicy (http://go.microsoft.com/fwlink/?LinkId=169167) cmdlet sets the specified GPO to contain the specified AppLocker policy. If no Lightweight Directory Access Protocol (LDAP) is specified, the local GPO is the default.
Retrieve an AppLocker policy
The Get-AppLockerPolicy (http://go.microsoft.com/fwlink/?LinkId=169165) cmdlet gets the AppLocker policy from the local GPO, from a specified GPO, or from the effective AppLocker policy on the computer. The output of the AppLocker policy is an AppLockerPolicy object or an XML-formatted string.
Generate rules for a given user or group
The New-AppLockerPolicy (http://go.microsoft.com/fwlink/?LinkId=169166) cmdlet uses a list of file information to automatically generate rules for a given user or group. It can generate rules based on publisher, hash, or path information. Use Get-AppLockerFileInformation to create the list of file information.
Test the AppLocker Policy against a file set
The Test-AppLockerPolicy (http://go.microsoft.com/fwlink/?LinkID=169000) cmdlet uses the specified AppLocker policy to test whether a specified list of files are allowed to run or not on the local computer for a specific user.