cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Detection of Adobe Acrobat DC editions for the Acrobat DC unified installer (versions 2021 or later)

jborchers
Moderator Moderator
Moderator
5 4 718

We are pleased to announce that with the ARL Update #2702 Flexera's Agent inventory capabilities have been extended. Our agent can now  detect different Adobe Acrobat DC editions, such us Professional, Standard and Reader for the Acrobat DC unified installer versions 2021 (or later) on desktop machines.

We have seen a high demand among our customers to enhance Adobe Acrobat DC edition recognition.

The existing identification methods (e.g. swidtag information) do not work for the Acrobat DC unified installer versions 2021 (or later) and cannot distinguish between the Standard and Professional installations. With the content change in July 2022, we have unlinked and remapped Acrobat DC installer evidence to Acrobat Reader. However, we have received feedback from many customers that the edition is needed to get better transparency.

This new functionality is only available for the Flexera Agent on Windows 10 and Windows 11 desktops. The enhancement has been added to the InventorySettings.xml file, which will be delivered to all customers by means of an ARL release. An agent update is not required.

To take advantage of this enhancement, navigate to Data Collection > IT Assets Inventory Tasks > Inventory Settings, scroll down to the Inventory Extensions Version and select Always use the latest version (currently xx). This will automatically deploy the latest InventorySettings.xml file to the agent.

Better transparency across Adobe estate

The editions are determined from the logged-in user in Adobe DC. The agent generates extra installer evidence, which shows the specific Adobe Acrobat DC edition (Professional, Standard or Reader) in the NDI. In a scenario, where multiple users are sharing a desktop machine to run different Adobe Acrobat DC editions from the same installation, each edition of Adobe Acrobat DC will be recognized. If the file-based usage data for Arobat.exe is processed, this also will be displayed for the recognized editions. 

 

 

4 Comments
mag00_75
Level 8 Champion
Level 8 Champion

Hi

Good that the Acrobat detection is getting improved. However we are still having issues with very strange inventory results even after this ARL update, maybe due to that we need to manually ignore evidences from ARL.

Right now the Acrobat DC (2022) continues pro has acrobat.exe as "required" file evidence, that basically link all STD, PRO and Reader to that application. For Acrobat DC (2022) continues standard the acrobat.exe is "not for recognition"

Do we need to ignore the linked file evidences in the ARL to get this to work?

Screenshot 2022-09-22 at 12.34.06.png

shuduguru
Level 7 Flexeran
Level 7 Flexeran

@mag00_75 ,

This is fixed as part of last week's ARL release (23rd September 2022) - Build no. 2703. 

Thank you, 
Srivatsa HS

ChrisG
Community Manager Community Manager
Community Manager

For anybody still considering deploying the InventorySettings.xml file update referred in this post, I would suggest considering to hold off and wait for the next update to this file to be published to avoid any issues related to the following: Known Issue: Adobe Acrobat DC detection in InventorySettings.xml revision 66 may trigger a Windows Installer consistency check when inventory is gathered (IOK-932379).

Watch the FlexNet Manager Content Blog for an announcement about an ARL release containing a further update.

ChrisG
Community Manager Community Manager
Community Manager

The issue noted in my previous comment has been resolved in the InventorySettings.xml file version 67, now available as part of Application Recognition Library #2705.