(imported topic written by mcalvi91)
how often do the software catalogs update?
(imported comment written by SystemAdmin)
At this point, the software identification catalog is updated every 1 to 1.5 months. However, as we move the update process to use BigFix fixlet content and the catalog updates are fulfilled via our hosted servers, the updates may be more frequent. Sound reasonable?
(imported comment written by SystemAdmin)
Hi,
we are an new customer to SUA, last week we installed the latest catalog, but the versions of some software isn’t the lastet like XML Spy, Mindmanager, Ultra Edit, PL/SQL Developer… and so on.
(imported comment written by hanspjacobsen)
Are the updates done manualy or is there an automatic process?
(imported comment written by SystemAdmin)
Catalog updates are not yet automatic. However, the Catalog updater engine is part of the base product and Catalog updates are simply XML files that get imported and merged into an existing Catalog. We have the mechanisms in place in the product, so we will begin distributing Catalog updates via DSS SAM content site subscription. At that point, it will be possible to run the updates automatically or manually.
(imported comment written by hanspjacobsen)
Hi Jeff what is the command or process to start this update manualy?
(imported comment written by SystemAdmin)
jeffs
Catalog updates are not yet automatic. However, the Catalog updater engine is part of the base product and Catalog updates are simply XML files that get imported and merged into an existing Catalog. We have the mechanisms in place in the product, so we will begin distributing Catalog updates via DSS SAM content site subscription. At that point, it will be possible to run the updates automatically or manually.
Is there an update on when this will be implemented? And is there a way (manual or automatic feedback) to provide input into the catalog for additions?
(imported comment written by SystemAdmin)
jspanitz
Is there an update on when this will be implemented? And is there a way (manual or automatic feedback) to provide input into the catalog for additions?
We will begin shipping catalog updates separate from the product binaries within a few weeks.
We would love to have community contributions to the catalog! The best mechanism at this point is to send your list to us, preferably in the format of the catalog:
-
Publisher
-
Software Title
-
Software Title Version
-
Package strings (i.e. what would appear in the Uninstall keys in the registry)
-
Application name (and version)
-
Executable file name and version
We’d also entertain getting the “raw” data from your DSS SAM inventory processes from you and/or we can give you an automated tool that you run on some of your computers that sends the results to the catalog team for their consideration.
(imported comment written by SystemAdmin)
Hi Jeff,
Do you have a particular method that you like to receive our contributions? Emailed to support? Perhaps a dss@bigfix.com address 
Thanks!
Mike
(imported comment written by SystemAdmin)
Is there a way to have the changes we make automatically feedback to BigFix on a scheduled basis? We’d rather not run a tool on the client but would be fine with doing that on the server.
(imported comment written by gsmith91)
Hello,
I am also interested to know if there has been any udpate on this. The catalog seems to quickly get out of date with updates/patches to applications such as Adobe Acrobat.
Thanks.
(imported comment written by SystemAdmin)
Great news for everyone: we have released our first generally available Software Catalog update shipped independent of the DSS SAM server binaries!
Please consult the instructions (just a few steps) here:
http://support.bigfix.com/product/documents/dss/Software_Catalog_Upgrade_Guide_2010-01.pdf
The catalog itself is downloadable from here:
http://software.bigfix.com/download/dss/SAMCatalog.zip (13MB)
It should take just a few minutes to unzip the package to your DSS SAM server and update your catalog.
Note that we intend to enhance this service by making catalog updates available via fixlet content at some point soon. At that point, catalog update management will be a bit more autonomous, but for now it’s a manual download and update.
Enjoy!
– Jeff
(imported comment written by SystemAdmin)
Excellent news!!! The update went very smoothly. Now to verify custom entries. Keep them coming.
Will there be a way to take customer scans that don’t match catelog entries and send them back to BigFix automagically?
John
(imported comment written by SystemAdmin)
Your custom entries will not be directly affected – they will always stay intact and have precedence. However (there’s always a “however”) there could be conditions where your changes are affected indirectly by the update:
(1) If we add an entry that is both a duplicate and a sibling to one of your entries:
-
At the application level, you will see both our entry and your entry in the drilldown reports. The computer count will be de-duplicated at the software title version and above so you won’t get double counts, but at the application level you will see two entries – yours and ours – that are the same product. You will want to delete one of the siblings from the catalog.
-
At the STV level and higher, the above condition could also occur, but you also have the risk of introducing an accidental ambiguous item. This would occur if one or both of the duplicate items (yours and ours) don’t include package strings to help the matching process disambiguate the title.
(2) If we delete a branch of the catalog where you had previously made changes, your changes may get deleted by the update. This will be extremely rare and we will publish any deletions in the documentation. There were none in this update. If you encounter this, condition you can still undelete the items – they’re in the db but have a deleted flag.
(3) If we reorganize a branch of the catalog, your changes will be carried along, but you might be surprised by the reorganization.
In general:
-
You should have a scan through the documentation to see if there were changes to items in our update that you also changed. Compare these to your Catalog audit log.
-
After the update, spot check a few things like the Ambiguous Entries tool and a few of the titles you customized.
Feedback and recommendations are always welcome :-).
– Jeff
(imported comment written by SystemAdmin)
jspanitz
Will there be a way to take customer scans that don’t match catelog entries and send them back to BigFix automagically?
John
Yes, we want to do something like that, along with a way to aggregate custom entries for possible integration and redistribution with our catalog.
(imported comment written by SystemAdmin)
Hi Everyone,
Per the discussion in this thread, we want to start working on the process to receive results from deployments that we can then feed back into our catalog production process to improve the breadth and accuracy of our catalog.
If you’re interesting in working with us on this, can you please contact me via email (jeff_spitulnik@bigfix.com).
And can I ask you to take the first manual step now:
-
Using SQL Management Studio, run the following query for your DSS SAM database:
select name from [BFInventory].dbo.unknown_packages;
-
Copy the results to a text file and email it to me.
The results list will show misc package data that is not yet used by the catalog, although don’t worry about its length or contents – it is
not
a list of unrecognized software in your environment.
Thanks!
(imported comment written by SystemAdmin)
All:
We’ve just released the latest catalog update (Catalog 2010-02) in addition to a new release of DSS SAM (v1.2).
DSS SAM 1.2 includes the full new catalog, but if you just want to update the catalog in a pre-1.2 server, you can get it here:
http://software.bigfix.com/download/dss/SAMCatalog.zip
(13 MB)
Catalog upgrade instructions and the list of changes since the catalog included with the previous DSS SAM release (v1.1.2) are at:
http://support.bigfix.com/product/documents/dss/Software_Catalog_Upgrade_Guide_2010-02.pdf
Thanks!
– Jeff