Are you using the Audit Plus Application Inventory within the Inventory Solution or are you just using the Basic Inventory?



If you use IS, then you can find all of the machines with the individual applications installed and compare these machines with those that indicate the applications as installed within the "Add/Remove Programs" control panel.



Does this help?



Regards,



QuietLeni

I have the same issue with the Technical Communication Suite. The Add-Remove has an entry for Technical Communication Suite as well as an entry for each of the applications bundled in that suite.

I'm thinking about creating a collection of those machines with Technical Communication Suite in the Add-Remove table, then create another collection from the Add-Remove table for one of the elements, Captivate for example, and use the exclusion option on this collection to exclude those machines in the Technical Communication Suite collection.

Is there a better way to identify the stand-alone Captivates?

When you repackage adobe with Wise package studio you are able to edit the registry settings that are used for add/remove programs.
In that case you can give every seperate products it's own name and the whole suite just the name Adobe suite.
I do this in SVS packages. It helps me much to sort out problems.
One of the enhancements I made for SVS packages is license reporting. In that case it sees the active package and counts the license inside depending on the guid of the layer and not the apps inside.

off topic, but I would suggest adding "branding" information to your installation packages. This is usually a predefined location in the HKLM registry hive. The "branding" is unique for every package, and can be queried using Altris. It's a very simple way of keeping an accurate software inventory. I sure Erik knows what I'm talking about.

Cheers
Phil