Acrobat DC activation exception causes license issues with Master Collection build

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.