Evidence for Adobe Acrobat DC and Adobe Acrobat Reader DC
Due to changes FlexNet/Flexera One has no way of telling Adobe Acrobat DC (subscription) and Adobe Acrobat Reader DC (freeware) a part when the information comes in from the discovery tool. Reference the ticket submitted to Flexera below:
Please find below a comment from our Product team on this case.
Thanks for submitting this ticket and sorry for the inconvenience…
The recent change in ARL should lead an SCCM customer to not recognize any Acrobat DC 2021 and 2022, as the installer evidences are now only mapped to Acrobat Reader (Freeware).
There is, unfortunately, no solution today for an SCCM customer for differentiating today Acrobat Reader and Acrobat DC… and this is not a Flexera recognition issue but more an Adobe packaging issue. Or maybe, if you find how differentiation can happen from file or installer evidences (only ones collected by SCCM), we can tweak our recognition.
At this stage, the only way customers can recognize Acrobat is to use swidtags… or registry keys… and SCCM cannot do this. If you know that SCCM collects this type of information and stores it in specific tables, we may extend our data collection… but we see no solution at this stage.
Does anyone out there have an alternate solution(s) to track Adobe Acrobat DC applications from Adobe Acrobat Reader DC applications?
You can blame Adobe for their lack of following standard packaging conventions.
Adobe has created a "universal" 64-bit install package for Acrobat, that includes both Acrobat Reader and full Acrobat. When you look at an Add/Remove Program Name or the main EXE, there is now no difference in what you see. For example, previously an install of Acrobat Reader would have a primary EXE Name of ACRORD32.EXE, and would have an Add/Remove Program Name similar to "Adobe Acrobat Reader DC"
With the new 64-bit universal installer, you will now see the following evidence when Acrobat Reader 64-bit is installed:
1) Main exe file name is ACROBAT.EXE
2) Add/Remove Program Name is "Adobe Acrobat DC"
If SCCM is used for deployment, have a look at your collection data. There should be multiple collections for different applications. This info could be used to create a new evidence (rather complex) or be the basis for a business import doing allocations (less complext).
The only way we solved this problem was to push out the Flexera agent. It was actually a huge driver in us finally getting the agent approved to be installed. Thanks to Adobe we now have the agent out there collecting this information for us.
IT Software Asset Manager, Lead Sr.
I'm adding a note here to ensure people see the following post for some current further discussion related to this topic: Content Change Notification: Change in the recognition rules for Adobe Acrobat DC