Optimizing AppLocker Performance
Updated: November 9, 2009
Applies To: Windows 7, Windows Server 2008 R2
This topic describes how to optimize AppLocker policy enforcement in Windows Server 2008 R2 and Windows 7.
AppLocker policies can be implemented by organization unit (OU) using Group Policy. If so, your Group Policy infrastructure should be optimized and retested for performance when AppLocker policies are added to existing Group Policy Objects (GPOs) or new GPOs are created, as you do with adding any policies to your GPOs.
For additional information, see the Best Practices for Optimizing Group Policy Performance article in TechNet Magazine (http://go.microsoft.com/fwlink/?LinkId=163238).
GPOs have a 2 MB size limit for performance.
The more rules per GPO, the longer AppLocker requires for evaluation. There is no set limitation on the number of rules per GPO, but the number of rules that can fit into a 2 MB GPO varies based on the complexity of the rule, such as the number of file hashes included in a single file hash condition.
When the DLL rule collection is enabled, AppLocker must check each DLL that an application loads. The more DLLs, the longer AppLocker requires to complete the evaluation.