'Applications' for Acrobat Pro XII (DC 2015) License setup

[nalinih]

(Apologize if this question has already been covered in different post; did not see anything related directly, we are not using FlexNet Agent)

Not seeing any consumption for Acrobat Pro XII (DC 2015), currently has Applications :

Acrobat DC (2015)

Acrobat DC (2015) Pro.

Also see : Acrobat DC (2015) Classic (not yet added, as was not sure if it related to the above license)

Realize this an old license, any input would be appreciated.

Thanks

[kclausen]

When you go to your Installed Applications view and filter on Acrobat DC, what do you see for software titles? 

If you are not using the FlexNet Agent, then your current Discovery Tool is likely not getting the information out of the ISO Tag that is needed to determine what edition of Acrobat DC is installed.

[nalinih]

'Installed Applications' view shows the following:

DC (2015) Classic

DC (2015) Continuous

----------

I can add these 2, but would there be a problem with applications included due to downgrade?

[kclausen · Accepted solution]

@nalinih - On the Applications tab of your license, you can add these 2 titles to make sure that the installs get consumed by the license.  You should also make sure that the primary application of Acrobat DC (2015) Pro is added so that the correct downgrade rights are applied and the license consumes installs of Acrobat XI Pro and Acrobat X Pro are included.

An additional question, are your purchases for Acrobat DC Pro perpetual device-based licenses, or are they purchased as an Acrobat Cloud subscription?  

[nalinih]

1. Already had 'Acrobat DC (2015)' in the application list, but that was not showing any consumption, which was the problem.

2.  Acrobat Pro XII (DC 2015) is a  'Perpetual' license, so did not add the 'Continuous' but  only the 'Acrobat DC (2015) Classic ' to the Applications list

3. After the reconcile last night,  consumption is > 0 

Thank you for your review/input.

[EHacking]

My suggestion is to submit a case for this. Apparently it is a known bug with Acrobat. If you are using SCCM to collect data, it is an issue Microsoft knows about. If you are using the Flexera agent, it is also known.

[nalinih]

EHacking,

Adobe licensing and Evidence  and naming convention changes by Adobe has been challenging.