Client Management Suite

I am trying to determine if what I am doing is possible.  I have created a Software Resource and I want to detect that it is on a system using Detection Rules to look for a file on the system that does not get collected through file inventory. 

What is the best route to do this?   I tried to do a Static File Expression Detection Rule that would look for the file, but this only works if I tell it to look exactly where the file is known to be (on my test system), but it could potentially be anywhere on the drive in production.  Is there a way to do Detection Rules that looks in all folders for a match.  I was hoping wildcards would allow the rule to look in sub-folders, but it is not finding the files.  For example, The base folder is the StartMenu and then File Path is *\MyFileHere.lnk.

Thanks in advance!

You'll need to do this with a custom inventory rule... I don't believe you can accomplish this with a detection rule, as it looks for a specific location to reside the setting / file. You could do a custom inventory and then create a dynamic filter off of that, utilizing a MSD policy to push to the machines that had that file.

Without a path, you would need a custom inventory.  You could then target the resource based on this data in the CMDB (the custom inventory is outside the detection rule).  Alternatively, you could use the custom inventory data to inform your creation of the detection rule.  For example, maybe you find that it was installed into six locations in 99.5% of the installs, so you could use those six paths in your detection rule, plus perhaps a seventh for the "proper" location.

Hope this helps answer your question.

Thanks for the feedback.  You confirmed what I was thinking was the case.  I already have custom inventory scripts running on the clients that populate custom inventory tables for reporting and filters, etc.  I just wanted them to start showing up in the InstalledSoftware table so they would show up in the normal software reports.  I think I will use the results of the custom inventory to tell the detection rules where to look and just have to keep an occasional eye on it for new sources that might show up.  I wish it allowed wildcards, it would make it easier.  Or, if the detection rules could be created automatically using queries from the database!  That would be nice.  Thanks again.