Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

Help on a dynamic collection regarding a registry value?

I'm trying to create a dynamic collection where the computers have a combination of 2 registry Value Names and Values, that would exist in a Registry item under HKLM:\SYSTEM\CurrentControlSet\Control\Class\{4d36e972-e325-11ce-bfc1-08002be10318}\[could be any name here after the \].

For example could be "HKLM\SYSTEM\CurrentControlSet\Control\Class\{4d36e972-e325-11ce-bfc1-08002be10318}\002" or "003". 

This, I think should return computers that have a value of 1. However it's only returning a computer that I know actually has a value of "0" when I check its registry.

I'm a bit confused on how to make it work. 

 

2

Comments

6 comments
Date Votes
  • Just to confirm, you have set up and ran a scan profile to scan the computers for these registry values correct? PDQ Inventory will not be aware of these entries unless you scan for them specifically.

     

     

    1
  • Gary White

    Yes definitely. I believe I confirm this too by seeing the exactly keys and names/values I'm needing to report on in the Computer's Registry details in PDQ Inventory.

    When I right-click them though I don't see a way to create a collection from it. I wonder if that's something they could add to make this easier (similar to installed applications right-click option)? 

    1
  • John Q, I'm testing to try to replicate. I do not have any reg entries with SelectiveSuspend so can you tell me is it at the same level as DriverDesc or is it in a subkey below there?

    1
  • Gary White

    Yes so here's the full path from Inventory scan:


    The DriverDesc one:

    1
  • I can't get consistent results. I can't find a way to force it to match registry Value Name and Value ONLY if they appear under a specific path and that's just for one set of Value Name and Value. Let alone two. Nesting the filters doesn't seem to help. For me at least, computers are matching as long as they contain the registry path, the Value Name and the Value, but the Value Name and Value are not being required to be in that path. It is just verifying that all of them exist somewhere in the results. Sorry John Q, but I'm stumped. 

    1
  • Gary White

    It's all good. I'm a newb to this stuff so that doesn't help either. 

    My XY problem here is that I need to deploy a script that changes those values. 

    That said, I guess my work-around would be to create a new simple registry value as part of my script, and then just make the collection of people "missing the script" to be missing that custom registry item I create with the script. 

    1