My customer noticed that the number of Installed Visio Products within DSS is much lower than what is reported in the Tivoli Endpoint Manager Console . He utilized the Tivoli Endpoint Manager Excel Connector querying the “Microsoft Visio Version Detection (Windows)” Analysis (BES Inventory and License site) and noted that 623 Machines were returned. However within DSS only 203 machines show to have visio installed.
I did notice that it appears that the Catalog does not have any entries for “Microsoft Office Visio XXXX XXX”. It does however have “Microsoft Visio XXXX XXX”. Is this a Catalog issue and do I need to add these manually if it is?
We intentionally rename Microsoft Office Visio to Microsoft Visio.
Since Visio belong to multiple packages within out catalog, your customer is going to need to disambiguate it. The way to do it is to add package to STV you care about in this case Microsoft Visio, it should look something like “Microsoft Office Visio -14.*”. I’ll find a package information in “Unknown Package” list (if it’s not in catalog already).
Another option to disambiguate software is to delete software causes Vision ambiguity, that your customer doesn’t care about it. For example, since Vision could belong to multiple Microsoft Office packages, the customer can delete of of them.
Note, in both cases you need to run full Import.
The third approach would be to use definitive package for Visio detection. You can use “Microsoft Visio Version Detection (Windows)” Analysis as your definitive package.
Add package string as a package in catalog to Visio STV, then add “Microsoft Visio Version Detection (Windows)” analysis as “definitive property” and run full import.