Summary

How to implement usage tracking on UNKNOWN PRODUCTS's

Synopsis

When the below can be seen in your usageagnet log, (once usage tracking has been setup) it means you will not be getting monitoring usage on the application.

Session logging: UNKNOWN PRODUCT Session end (Path: C:\Program Files (x86)\Mozilla Firefox\firefox.exe, product is unknown) Session will not be added to cache.

Whenever a product is unknown no usage information is collected.

Discussion

By default the usage agent only recognizes MSI and ManageSoft packages, but application such as Firefox lack these so won't be tracked by default. However it is possible to track these applications, but it has to be configured manually, by using manual mappers.

The manual mapper relates to actual files to track e.g. .exe files so it's not the registry key names that matter - within the manual mapper registry structure you can name the key as desired as long as you follow the correct hierarchy as covered in documentation (which i have attached, please view page 425) e.g. [HKEY_LOCAL_MACHINE\ManageSoft Corp\ManageSoft\Usage Agent\CurrentVersion\Manual Mapper\ApplicationName] then you create the strings mentioned i.e.

Application=WebSphere
ExecutablePath= D:\Websphere\WebSphere.exe
Version=*
Regex=False

This would monitor an executable called WebSphere.exe in the D:\WebSphere directory.

You will then also have to set 'UseManualMapper ' to true (false by default), this should allow you to track the mappers. The attached documentation is quite old, but the section on manual mappers mostly still applies.