Adobe Acrobat DC & App Volumes

Hello. We are attempting to create an Application in App Volumes for Adobe Acrobat DC. In the past, we have been able to simply do the following to achieve this :

1. Create an Application in AppVolumes and fire up the packaging machine

2. Install Adobe Acrobat from our standalone installer and use our volume serial key

3. Use the Adobe PRTK / APPTEE Tool to generate a Prov.xml file (customized with our serial / product identifier number)

4. Use the Adobe PRTK / APPTEE Tool to consume the Prov.xml file

5. Complete packaging and deploy out the Application to entitled users.

However, it appears that in November of 2019, Serial activation of Adobe Acrobat has become a deprecated procedure. I contacted Adobe support and they tried to have me use a piece I am totally unfamiliar with called the Microsoft Application Virtualization Sequencer (AKA App-V Sequencer). This process entails creating a package in the sequencer, having it invoke the installer, supplying some arguments / switches to a template and it creating some kind of packaged version of Acrobat that will play nice with App Volumes deployments.

My technician however overlooked the fact that the App-V sequencer is no longer available for Windows 10 Version 1909, which we are on. I have not heard back from my technician but am quite frustrated that the process has become so convoluted since last time I did this.

I wanted to reach out to the community and see if anyone on similar versions of App Volumes has successfully created Adobe Acrobat DC Applications (appstacks) and what their method was? As it seems this method has only changed since last November, I am trying to find feedback from recent setups. All our version information is as follows:

Adobe Acrobat DC Professional & Standard (2015 Classic Track) using a CLP (Cumulative licensing program) Serial Key

Windows 10 - Version 1909 - OS Build 18363.592

VMware Horizon version 7.11.0 build - 15231595

VMware App Volumes Version

VMware Dynamic Environment Manager (DEM, previously UEM) Version


0 Kudos
1 Reply


I recommend the link below if you have not done so already. specifically, Named User Section. You want to make sure to capture <user>/appdata/Roaming with DEM to roam license. Also remember to disable auto update on the appstack. I have Acrobat DC installed in our gold image and it worked for us after they changed licensing to Names User in November.

VMware Horizon Deployments — Acrobat Virtualization Guide