Acrobat DC activation exception causes license issues with Master Collection build

Report · Nov 30, 2015

Working with Acrobat DC, found the method to create an exception for the master image. Ran the command before saving the image. Acrobat now works (doesn't ask for a login), but my previous install of the Master Collection, which ran with another prov.xml licensing solution has reverted back to it's unlicensed conditon. The Acrobat DC exception also removes the credentials from the Adobe Creative Cloud Desktop. Is there anyway to make these pieces of software play nice for imaging?

Report · Nov 30, 2015

"found the method" is too vague to troubleshoot. Start here and report back: Common Deployment Options and Methods — Enterprise Administration Guide

Ben

Report · Nov 30, 2015

I apologize. I did start there and created the prov.xml as instructed. I then installed Acrobat DC on the masterbuild, ran the command at the bottom of that page, sysprepped and saved. Once the image is deployed, the fix works for the Acrobat product, but also removes the saved credentials in Adobe Creative Desktop and reverts the Master Collection install back to a trial state. I have that product working through a prov.xml that was created with the Customization tool. My opinion is that there is a conflict between the two.

Report · Nov 30, 2015

Thanks. I've pinged some folks that have the ability to test such a scenario.

Ben