Software Usage Metering - How to Monitor Unknown Product Known?

Software Usage Metering - How to Monitor Unknown Product Known?


How to implement usage tracking on UNKNOWN PRODUCTS's


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

"C:\Windows\Temp\Managesoft\usageagent.log" there are a lot of products marked as "UKNOWN PRODUCT": [2.12.2016 12:39:44 (G, 0)] {3328} 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.


By default the usage agent only recognises 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.

ExecutablePath= D:\Websphere\WebSphere.exe

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

UseAddRemove option does mean that only the MSI database should be scanned but this is intentional. Experience shows that the UseAddRemove option can cause issues due to the quality of entries in the AddRemove database i.e. evidence being matched to multiple paths / versions / products etc so I'd recommend leaving that disabled.

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

Was this article helpful? Yes No
100% helpful (1/1)

Hi @jkeighley,

thanks a lot for your information and the PDF. It was very helpful.

The only thing  what I have noticed during my tests was
my ExecutablePath is working without double \ in the path, e.g.
c:\program files\notepad++\notepad++.exe

I have tried this, because with double \ the logfile has shown:
Adding product 'Notepad++' (priority 20) to product cache
Adding file '"c:\\program files\\notepad++\\notepad++.exe"' to product 'Notepad++'
UNKNOWN PRODUCT Session end (Path: C:\Program Files\Notepad++\notepad++.exe

With a single \ I got:
Adding product 'Notepad++' (priority 20) to product cache
Adding file 'c:\program files\notepad++\notepad++.exe' to product 'Notepad++'
KNOWN PRODUCT Session start (Path: C:\Program Files\Notepad++\notepad++.exe, Product: Notepad++, Product version: *)

Best regards

today I have made an export of the the regkey to a *.reg. Here I can see the double \

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ManageSoft Corp\ManageSoft\Usage Agent\CurrentVersion\Manual Mapper\Notepad++]
"ExecutablePath"="c:\\program files\\notepad++\\notepad++.exe"

Best regards

Version history
Revision #:
8 of 8
Last update:
‎Oct 22, 2020 03:16 PM
Updated by: