We are using DDS v1.3.0.592, Catalog 2011-Jun-13 (which was loaded close to two weeks ago). We are unable to see Visio 2010 in the drill down even though we have hosts that have Visio installed.
For example, locating a host in Computers shows Visio.exe in the Raw Executable Scan Data but not under Tracked Applications. The Last exe scan is 6/25, Last App Tracking/Seen is 7/1. Daily imports are happening with no issues.
Why are we not seeing Visio under the Drill Down
After importing a new catalog, does new software appear shortly after or does a host need to upload its results again?
Because Microsoft packages Visio 2010 in multiple ways (e.g. standalone, professional, premium), Visio 2010 requires DSS SAM’s (TEM SUA’s) two-factor detection: 1) the presence of the exe, and 2) the presence of package string in the uninstall hive of the registry. You have determined that the visio.exe 14.0 is present on the machines, but what about the second factor? You can drill down to the Computer Details report in DSS SAM and have a look in the Raw Installed Applications Data of one of the computers where you believe Visio 2010 is installed and see what appears there relating to Visio 2010. You should add that string to the appropriate STV in the DSS SAM catalog. Or you can go to the Catalog entry for the appropriate Visio 2010 STV, click on Add under Packages, and use the Unmapped Packages tool to find the Visio package string and add it.
Regarding question 2:
Computers don’t need to send new results, but DSS SAM needs to do a full import after the Catalog is updated so the raw data already present on your server can be correlated into the new Catalog entries for potential matches.
You raised a good point, stating that it is a best practice to perform a full import after a new catalog has been updated. I was hopping that that was the issue, but it wasn’t.
The Raw Executable Scan and Raw Installed App (shown below) both show Visio 2010 as being installed.
Microsoft Visio 2010 Service Pack 1 (SP1)–|||-----|||—Microsoft–|||-----|||—“C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Oarpmany.exe” /removereleaseinpatch “{91140000-0057-0000-0000-0000000FF1CE}” “{01D8AE4B-A04D-47E5-81BF-E3F98B81B8C3}” “1033” “0”
Microsoft Visio Professional 2010–|||—14.0.6029.1000–|||—Microsoft Corporation–|||-----|||—“C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\setup.exe” /uninstall VISIOR /dll OSETUP.DLL
I didn’t try manually adding the string to the STV, as I don’t want to “correct” something that should be working.
We have only made a few manual entries to the catalog and I wouldn’t have a problem performing a catalog import with the overwrite string (I think there is a way to do that) if we think that may help.
As you know now, looks like you found an error in the catalog. Adding the correct package string yourself (per the instructions from 7/5) is the right way to go for now. Specifically, add one of these under the appropriate STV:
Microsoft Visio Premium 2010 - 14.*
Microsoft Visio Professional 2010 - 14.*
We missed the hyphen in our catalog and we’ll have this fixed in the next catalog release, scheduled for July 18th.
When the catalog update is available and you merge it into your local catalog, it will just augment what you’ve added. You can delete the packages you added or just leave them there, with no detrimental effect.