17: Troubleshooting Item Level Targeting (ILT) Evaluations when using the PolicyPak ILT Engine

Starting with CSE 3068, PolicyPak replaces the in-box Microsoft Item Level Targeting Evaluation engine with its own PolicyPak ILT Engine.

When the PP ILT engine is used, new logging occurs should you need extra troubleshooting.

User side logs: %LocalAppData%\PolicyPak\component_name\ppTargetingFilters_v2.log
Computer side logs: %ProgramData% PolicyPak\component_name\ppTargetingFilters_v2.log

An example of this can be seen here, when ILT is used with PolicyPak Admin Templates Manager on the USER side:

How the PolicyPak ILT Engine Works / Error Handling

With this new ILT engine every single condition is evaluated separately and asynchronously, and the results are logged as they become available. The ppTargetingFilters_v2.log will contain the details of every individual condition being assessed, including interim results (i.e., paths with resolved variable names, etc.). If there is an error, the error gets logged as well.

When an individual condition cannot be evaluated because of an error, the PP ILT engine will try to use a previously cached result for that single condition (not the entire filter).

For example, a typical error you could encounter is where an LDAP condition cannot be evaluated because the DC is not available, (i.e., the user is logged into a remote PC but has not established a VPN connection to the company network as yet).

In this case the PP ILT engine will try to use the previously CACHED or manually defined “DEFAULT” result if available, but will still attempt to re-evaluate any other conditions in the same filter.

Disabling PolicyPak Item Level Targeting and using in-Box Preferences Targeting

If you encounter a serious issue which requires that you stop using the PolicyPak ILT engine and must instead revert back to the Microsoft ILT engine you can use a PolicyPak ADMX setting to do it.

Tip: Learn how to implement the PolicyPak ADMX settings from this KB.