Wierd SAM Catalog Problem

Usage and Config BFI
1

(imported topic written by SystemAdmin)

Not sure if this is new with the catalog that was released with DSS 1.2 but Internet Explorer 6 and 7 no longer show in the inventory. Digging into this, it seems that all different version of IE (From IE 5 to 8) are tied to IE6, IE7 and IE8. Is anyone else seeing this? We have no custom entries for IE nor any ambiguous ones.

Anyone else seeing this? We were tempted to just delete the wrong versions from the entries, but then thought the problem may be bigger than just us.

2

(imported comment written by B3UM_vincent_shyu)

For SAM 1.2. In order for SAM properly detect IE version, we explicitly added ambiguous condition in executable level and allowing package string to disambiguate IE versions.

In 1.2, there is an update on Installed Application Information analysis to pull additional IE information outside of registry Uninstall folder

Following steps would need for client to get an accurate IE recognition.

Get the latest SAM content that contains IE detection (In should happen automatically)

Allowing all the Windows endpoints report back to BES with package information (or simply select all the computers in Computers tab and click “Send Refresh” button)

Upgrade DSS SAM to version 1.2

upon completion of SAM 1.2 upgrade, reset and run a full ETL

What does Customer expect to see?

Customer might see the number of IE has reduced quiet a bit on DSS SAM reporting. It is due to following reasons:

Before 1.2

In the case when user upgrades IE, it leaves a copy of previous IE main executables; as result, DSS SAM would detect both previous and current IE versions.

In 1.2

With new analysis to detect IE package data, Customer shall see a proper IE detection.

In the case some endpoints did not shown IE detection; in such case, be sure these endpoints are active rather than offline. By default, the Installed Application evaluation interval is set to 1 day, customer can manually select these endpoint computers and click on “Send Refresh” button in BES console Computer tab to allow these endpoints to report back IE package information.

3

(imported comment written by SystemAdmin)

Adding to speedy’s comments…

It turns out that there are frequently old artifacts left behind by old versions when IE is upgraded. Specifically, we found cases where the old binaries appear to be left behind even though the computer has been upgraded. Therefore there were two updates we implemented with 1.2:

  • The catalog now accommodates the cases where multiple old versions might be left behind, but the computer is actually upgraded to the latest version
  • The Installed Applications analysis reports additional context from computers to clarify which version of IE is actually installed even if old “cruft” is left behind

To get the full update, you’ll have to upgrade to 1.2, ensure your computers have recently reported the Installed Applications data, and an import in DSS SAM has recently occurred.

Let us know if you’re still seeing weird inventory counts with 1.2 and the new analysis data and we can try to isolate the issue.

4

(imported comment written by SystemAdmin)

At this point, we have just 59 systems showing IE as being installed. All are version 6 and 8. Out standard desktop is IE7 with some leftover IE6 systems out there. The servers have IE7 and IE 8. So perhaps the IE7 machines just have not reported in yet? I guess we can wait a little longer to see if they show up, but I am sure at least one would have reported in by now.

John

5

(imported comment written by SystemAdmin)

John, do you have a package entry under Internet Explorer 7 listed at “Internet Explore 7.*”?

Can you edit that entry or create a new entry to list it as “Internet Explorer 7.*” (with an ‘r’ for Explorer)

Then check “Perform full import” and Run an import. See if your IE 7 machines show up correctly now.

6

(imported comment written by SystemAdmin)

Jeff / Speedy

We do have that package defined. I modified it and performed the import. That fixed it I think - we are seeing more clients, not all of them but more. Woohoo. Thanks! I would not have caught the missing r. If they don’t all show up within our scan period I will report back.

John

7

(imported comment written by SystemAdmin)

So we are seeing a similar problem with Adobe Acrobat. Reader shows up fine but our Acrobat 8 and 9 software is not showing up anymore. I checked for typos in the catelog but didn’t see anything similar to what we saw with IE. Anyone else seeing this?

8

(imported comment written by SystemAdmin)

Hi John,

My guess is that Adobe Acrobat has been updated in your environment to a recent minor version (Adobe issued some updates last month, around the time we were preparing the catalog) that isn’t yet catalogued yet.

A quick check:

  1. Go to the catalog entry for Adobe Acrobat 8 Standard.

  2. Click on the Add link under Packages

  3. Click on the Discover Unmapped Packages link

  4. In the filter box, type “acrobat 8 st” without the quotes, and click Filter

You will likely see a list of package strings like this:

Adobe Acrobat 8.2.0 Standard - 8.2.0

Adobe Acrobat 8.1.7 Standard - 8.1.7

Adobe Acrobat 8.1.6 Standard - 8.1.6

Adobe Acrobat 8.1.5 Standard - 8.1.5

Adobe Acrobat 8.1.4 Standard - 8.1.4

Adobe Acrobat 8.1.3 Standard - 8.1.3

  1. Shift click to select the range of items that look like the list above.

  2. Click Use Selection

  3. Click Save

  4. Perform a full import

Before you do step 7, you might want to do the same on the Applications side of Adobe Acrobat 8 (i.e. filter for acrobat.exe in the Add executables from the Unmapped Executables link) in case you have a version of the acrobat.exe that isn’t indexed yet.

If you have Acrobat Professional, you will want to do the steps above to add the package strings, but you will be looking for “acrobat 8 pro” in your unmapped packages.

We will also catch these updates in our next catalog update.

9

(imported comment written by SystemAdmin)

Yup, this seems to be the issue. I thought they were showing up before the update, but I guess not. We’ve created the manual mappings and are eagerly awaiting the next catalog update! Thanks.

10

(imported comment written by Marty23)

since we are talking about SAM Catalog issues,

Is there a reason that you are not Cataloging Microsoft Office OneNote version 12? I see an entry for Microsoft Office OneNote version 11 -

Publisher: Microsoft Corporation

Software Title: Microsoft Office OneNote

Software Title Versiob: Microsoft Office OneNote 2003

Package: Microsoft Office OneNote 2003 - 11.*

Applications: Microsoft Office OneNote 2003

Executables: OneNote.exe 11.0

But nothing for OneNote.exe 12.0!

11

(imported comment written by dgies91)

This was added to the catalog under OneNote 2007 in DSS SAM 1.1.2 which was released in October 2009.

There are two ways you can get the latest catalog: By upgrading to the latest version of DSS SAM, or by updating just the catalog. The most recent version of the server is 1.2.1, and the most recent standalone catalog is February 2010.

12

(imported comment written by Marty23)

i beleive i have the latest catalog!! When I try and run the catalog update, it tells me that i have 1.2!

13

(imported comment written by Marty23)

Attached is a screen shot of the message i get when i try and run the upgrade.

14

(imported comment written by dgies91)

Yes, it appears you have the latest catalog.

What happens when you search the catalog for onenote.exe 12.0?

15

(imported comment written by Marty23)

attached is the results of the catalog search for onenote 12.0

16

(imported comment written by Marty23)

Here is the result of double clicking on the first item displayed in the list.