Why can’t registry signatures be auto generated?

Content Authoring SUA Signatures
1

Hi,

Since BFI scans the Windows registry and brings all that info into its database, why do we still need to create extended signatures manually?

2

Any thoughts on this topic?

3

How much automation are you looking for? It may not be prudent to generate an entry for every possible package, since it BFI is primarily designed to help you manage software assets (those products that you spend money on :slight_smile:)

If you go to the Package Data report, you can click on the gray down arrow in the cell next to the name of the software package, and it will provide a clickable link to populate the Create Signature panel in Catalog Customization.

I just watched the latest BigFix Inventory Beta demo. It included a capability to do a one-click signature creation from aggregated package data (registry data in Windows). Here is the description from the presentation:

Bernie uses the new, aggregated report with Package Data summary that is calculated on demand. This report allows him to create custom signatures in a semi-automated way. He can also quickly check which software is already covered by the existing discovery signatures.

image
image1721×659 239 KB

4

We were under the impression that Package Data generation would create a file-based signature. Sounds like we were wrong. Thanks for helping us clear that up.

I googled the BigFix Inventory Beta demo but couldn’t find it online. Do you mind sharing the URL?

Thanks

5

Send an email to talk2sam@us.ibm.com - send your IBM ID and Company Name along with your request to participate in the Beta.It’s open to anyone to join. This will allow you to gain access to the presentation and other materials.