This is an example of the log that prevents it identifying the Adobe apps and comes once the first Adobe app is matched to the path usageagent_qh11205368.log:[26/06/2019 10:58:57 AM (G, 0)] {3744} Session logging: UNKNOWN PRODUCT Session (Path: C:\Program Files (x86)\Adobe\Adobe Creative Cloud\ACC\Creative Cloud.exe, product is unknown) Session will not be added to cache.   I have attached the log from the usage agent that we submitted with the call we has open on this issue ... View more

Not quite the problem is the first application for example will report back as Photoshop.exe and from then on all other Adobe executable will not report back and will simply be listed as UnMappedExes and have no name to identify the application and match back to evidence. I did have a call open for this and attached the logs that shows the usage agent doesn't map the exe's back after the first one. ... View more

We have completed extensive testing with this setting and unfortunately it doesn't help with the Adobe applications, the problem is they are all installed in the same location on the device, so basically it detects the first Adobe application it finds and reports usage for that application,  but doesn't report on any other Adobe applications after this due to the fact the path is already assigned to the first application that was discovered. So unfortunately it doesn't help for the reporting of usage for the Adobe CC products. I believe the issue with the Adobe apps is going to be resolved in Q1 this year with the next release of FNMS ... View more