In AA Console each field is searched individually, which makes the filter engine simple but does lead to some consequences in that you may not get the computers you’re looking for.
If you want a collection showing computers with Adobe Reader versions other than 10 you might create the following filter:
This seem like like an obvious way to get what you’re looking for, but once you realize that it’s matching the applications individually, you see a problem.
You would expect your computer to not match the filter because it has version 10.1 of Adobe Reader, but it does because it has another application that doesn’t have 10.1. We got around this in AA Console by adding a new field called Application Name and Version which concatenates the name and version in a single value to allow for them to be matched together. But this doesn’t help with all of the other fields that you might want to work with.
PDQ Inventory resolves this problem by grouping fields underneath their respective types of inventory data. Now, to implement the logic above you would just create a single application filter:
The new architecture of the PDQ Inventory filters allows this to be done easily and logically. You can even add more Application filters to the same collection to combine the varous filters.
This issue has been one of the more confusing in AA Console and we’re glad to finally be able to clear it up with our new software. If you haven’t had a chance to try out PDQ Inventory, please give the beta a try. The software is free to use just like PDQ Deploy and we hope you find some good use for it.