I hate to ask this but I must: what if you are not using the FlexNet agent, but are collecting your inventory via SCCM and JAMF? ... View more

So that should be the indicator that it is a paid version.  Just spoke with Adobe who said they did this intentionally.  Argh!!!! ... View more

and do you show Distiller installed? ... View more

see attached for file evidence.  I think one of the real problems is that AcroRd32.exe appears in both versions.  However, acrobat.exe is unique to the Pro Install, as is AcroBroker and AcroDist.  But the distiller version can differ from the executable.  The Pro version executable has no file size, so not sure why that is not being distinguished from the Reader Version   ... View more

and this piece of evidence if overstepping itself. ... View more

Also, the program size is considerably different between the two versions.  Acrobat Pro 2.68GB and Reader is only 495MB, if that helps.   ... View more

I tested the swidtag by uninstalling the Pro version, rebooting, reinstalling from CC Desktop and the swidtag did not get updated, so no, i don't trust those entirely.  Once I reinstalled, I show one entry for Adobe Acrobat Reader DC and then another for Adobe Acrobat DC (the Pro version - see attached).  I am working with our packaging team to add Pro to our deployed packages.  I'd be careful on the suite, unless you do one massive piece of file evidence that can be applied against different versions (for example, Adobe DC shows up as 22.x but Distiller is 21.x - so the required could kill that idea, but Distiller is the best way of determining Pro/Standard from Reader. ... View more

Also, i did a clean uninstall of my Acrobat Pro 2022, re-installed through Creative Cloud and my software tag never got updated.  Still reads exactly the same: regid.1986-12.com.adobe_V7{}AcrobatCont-12-Win-GM.swidtag with a datestapm ofd 10/27/2020. ... View more

So, what happens if you are not using the FlexNet agent and are getting inventory from JAMF and SCCM? WMI does not really come in.  Why can't Flexera use a combination of Distiller and Acrobat to determine if it is not Reader.  That would seem to be a pretty direct way of identifying at least free versions from paid versions. ... View more

Correction - you should run a recon without bringing in New Inventory, which will update the dashboard ... View more

Okay - that worked and it did not require a recon.  Using the Publisher Portfolio Dashboard, i was able to identify the licenses contributing to that number.  It's the licenses that did not have a value in Override that was causing the inflated numbers.  Once i adjusted them, the problem resolved itself.   ... View more

I went into the Cognos piece to see if i could pinpoint where that number was coming from and there was an SAP license with no Override price.  I put one in - we'll see if that changes it tomorrow. ... View more

Let's put it this way, i adjusted enough of the licenses that the metric should have gone down significantly.  It did not move one $   ... View more

I did.  I even did a couple of before and after comparisons.  Even after changing the Override Unit price, the raw extract of that table showed a considerable difference from my starting number to ending number, but the metric didn't budge at all. ... View more

Tried that.  Doesn't work.  I even then set the Override to 0.01 in case it didn't like 0.00 - the metric on the dashboard did not budge, no matter how we set the override price. ... View more