Collection filter using Windows features does not work as expected
Hi,
using PDQ inventory 7.3, I see the following behaviour which I do not understand.
If I create a collection filter searching for the Name of a Windows Feature starting with the string "Hyper-V" (added "" for clarity here) the collection contains 0 members. Even if I copy and paste the name of the windows feature from the "open computer" window this does not change.
On the other hand, if I change the comparison operator to "Contains" or even "Ends with", then the collection contains the expected machines (running W2K8 and W2K12). This is completely unintuitive because in the "open computer" windows, all the Hyper-V features have that string at the beginning of the name and NOT at the end
The problem is not restricted to "Hyper-V" features, doing this with "Bitlocker" does not change the strange behaviour.
Is this a bug or am I doing something wrong here?
Comments
Hi,
This is "sort of" a bug that you've uncovered. If you open a machines details and go to the Windows Features pane there is a small grid icon in the top left of the column headers. When you click on that you'll see that Name is an additional column that you can add to the view. Once that's added you'll see that Hyper-V is actually called Microsoft-Hyper-V-All. So the bug here is that we should have a column for you to choose in the collections called Feature Name instead of just Name but if you change that accordingly then you should be able to get this to work.
Personally, I would call this type of inconsistency a bug. Identifiers in the collection editor should correspond (almost) directly with the identifiers at the top of the machine details window. If you keep the pretty display name "Feature", then I would expect to be able to create filters for this display name _as well as_ for the (for now hidden) "Name" identifier.
Thanks for the explanation.
I just started the Enterprise trial today and I'm having this same problem and I think that Jason's work around is invalid. When searching for Windows Server Features every server is going to have every feature listed and at least one will be enabled so if you were to create a collection as described by Jason to filter for say domain controllers it would list every machine with a server OS because every server has the DomainServices-DomainController feature and every server OS typically has at least one feature enabled. It seems you cannot filter a collection based off of a specific windows feature. I setup a collection below and it returns every server available.
I am still using an older version of PDQ Inventory (PRO) and cannot reproduce the wrong behaviour. The collection shows all domain controllers (feature "DirectoryServices-DomainController" enabled) and those servers where feature "DirectoryServices-DomainController-Tools" is enabled.
I tried to append a (slightly redacted) definition of the collection but this board software only allows pictures :-/
Ok, at least there is code markup...
I imported this again and get the same correct results.