cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Hi,

 

Need your help guys. I have a situation wherein in the process of software deployment via SCCM, it downloads the installer on the machine for easier installation (or if necessary uninstall the software). However, having a newer version of the same software process-wise is that it removes the old version and installs the new version but the problem is that the installer or setup.exe of the old version is already downloaded on the user's machine, and the existence of which is being read by FNMS stating that it has both the new version and old version on it. All installers via software center/deployment are all stored in a folder called ccmcache located in c:\Windows. Mind you that ARP when checking on the machine directly shows that the installed version is the new one and the existence of the old one has already been removed.

Any thoughts on what should I do so FNMS won't read the machine to have old and new versions just because of the installer evidence?

(1) Reply

@jjoaquin 

The majority of applications on the Windows Platform in the ARL are recognized only by Installer Evidence and not by File Evidence due to the scenario that are are describing.

In addition, when File Scanning is enabled, the Flexera Agent by default ignores anything under the default Windows folder.

It would be interesting to see what evidence that is being picked up for one of your scenarios that you describe above:

Pick a specific scenario that you are describing on a specific device.

Within FNMS, find that device on the Active Inventory page, go into the properties of the device and then go to the Evidence tab.

On the Installer Evidence page, search for the recognized application name to see what raw installer evidence (if any) is used to recognize this application.

Next, go to the File Evidence page.  Go into Column Chooser and make sure that the Raw File Path column is on the view.  Then, filter on the recognized application name to see what raw file evidence (is any) is used to recognize this application and what File Path the EXE is found in.