(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.