Activating Adobe Acrobat in a non-persistent environment

So, yeah recent events at a customer lead me to writing this article for my own purposes of documenting what I did and sharing this with you to prevent the frustration I’ve encountered.

Lets just say Adobe isn’t that keen on using its software in a SBC environment or VDI infrastructure. Or you might say they still have the perception of the traditional stand alone work-space. -This is just my opinion

Using a product such as Adobe Acrobat DC requires activation for every single user that uses it, perhaps you have encountered it before. Upon starting Adobe Acrobat, the program closes itself and you are prompted with the following screen:

This to me is just unfeasible in a SBC or non-persistent environment, I guess that’s why this application gets packaged into a Microsoft App-V or VMware thinapp so often.

But since we haven’t got these tools to our possession we needed a different solution. This solution can be found by using adobe_prtk.exe which is part of the Adobe Provisioning Toolkit.

First of all we discovered the customer had a single user license, which will get you nowhere if you want to activate the product for multiple users. Adobe is software that cannot be easily fooled around with (which is a good thing from a anti-piracy standpoint).

So after a quick chat with Adobe support and the software distributor, the client purchased a volume license based on the English language (since this was cheaper).

Now we where able to activate and stream the license (that’s the way Adobe works) to the machines. To do this we will need the following things:

  1. The serial number
  2. Grant an offline exception for the product through the Adobe Customization Wizard
  3. Know if the product is Continues Track or Classic Track (see here)
  4. License ID or LEID (see here)
  5. The command lines

As I said before you’ll need a volume license serial number, the track the customer had or used was “Continuous” and the accompanying “LEID” is: “V7{}AcrobatESR-12-Win-GM”

This leads to the following command line for Adobe_PRTK.exe: “Adobe_prtk –tool=VolumeSerialize –generate –serial=XXXX-XXXX-XXXX-XXXX-XXXX-XXXX –leid=V7{}AcrobatESR-12-Win-GM –regsuppress=ss –eulasuppress”

As you can see, the Return Code is “0”, which is a good thing. After running the command above a prov.xml is generated. This file holds the license information. This “prov.xml” file on it’s turn can be used to stream the activation of Adobe Acrobat against machines that are non-persistent such as a VDI work-space, Citrix XenApp MCS or PVS etc.

The command line to use the prov.xml is: adobe_prtk.exe” –tool=VolumeSerialize –provfile=”prov.xml” –stream

Again if everything is successful the Return Code will be “0”. We have created a job that after every boot or reboot the command line above is executed against every machine Adobe Acrobat is installed on.

This will resolve the “sign-in required” screen in your user sessions. The activation is machine based, however make sure people cannot start Adobe Acrobat more times then you have licenses for.

This situation resolved the activation issues with the customer. However there was one oddity happening which we have recently discovered. If you have supplied alternative languages in the Adobe Acrobat Customization Wizard DC, you will need to provide and purchase a license in the desired language. So if you want to have a Dutch Acrobat installation, purchase a Dutch license (licenses in other languages appear to be more expensive then native English).

Our software distributor provided a English license because this was cheaper for the client, but when the client switched the desktop from English to Dutch, Adobe needed activation again, the currently streamed license was insufficient and the “Sign-in” required screen prompted again. To avoid this make sure you will only install the English language.

After returning the question to the software distributor the feedback was as following:

Purchase the language you desire and English is always available, purchase a English only license and no other language can or may be selected.

Hope you find this useful and it will save you time and energy.

– Something wrong? Did I mess up, talking BS or got another trick up your sleeve? Please let me know in the comment section!

Cheers! Rens

14 thoughts on “Activating Adobe Acrobat in a non-persistent environment

  1. SysAdmin_TN

    Just used this to fix the issue in my environment. One issue I had was during the copy/paste of the command to generate the xml, I kept getting return code 19. I fixed this by adding an additional “-” in front of the individual commands. Not sure if it’s a version change or what, but there it is.

    Hopefully this helps someone else. Great, informative post, Rens!

    Reply
  2. Greg

    I kept getting return code 14 but adobe changed the LEID, this is the command I used.

    Adobe_PRTK.exe Adobe_prtk –tool=VolumeSerialize –generate –serial=”1111-1111-1111-1111-1111-1111″ –leid=”V7{}AcrobatESR-17-Win-GM” –regsuppress=ss –eulasuppress –locales=en_US –provfile=”C:\Adobe\prov.xml”

    Reply
    1. Rens Hollanders Post author

      Hi Greg, usefull information, so the command you provided is the new correct command?

      Reply
        1. Shaun

          There are two ‘-‘ at the start of each command in my comment above. The font/css is substituting them out for a single when publishing text.

          Reply
  3. behzad

    Excellent article, very useful.
    I am able to create the prov.xml file just fine (error code 0), so no issue here.
    But when I try to apply the prov.xml file to the VDI instance I am getting error code 20 and I am still getting the sign-in popup.

    Error 20 = Loading of permanent activation grace failed (due to malformed xml, corrupt or missing
    Enigma data, or some other error)

    Any suggestions.

    Reply
    1. Rens Hollanders Post author

      Hi,

      Unfortunately I have no idea. I know over time ID’s have changed and Adobe’s tracks/channels have changed too. What happens when you load the xml manually and not automated in the final solution?

      Kind regards,

      Rens

      Reply
  4. ramil de los reyes

    Great article, thank you. Question: if you already have Acrobat DC installed and users each logging in using their own Adobe Cloud credentials, then later get a volume license, must you re-install Acrobat or can your process be applied to an existing installation?

    Reply
    1. Rens Hollanders Post author

      Hi,

      Unfortunately I have no experience with Adobe CC, I can imagine the process works kind of the same as MS Office. You either get a license through your Office account on a Microsoft 365 subscription. Or you install a software version (such as Office 2016) with a volume license.
      Question is which version is supported for which environment.

      Reply
      1. Nicola

        Hi Rens Hollanders, thanks for the article! it was very very helpful in solving my problem in a Citrix Farm with VDI MCS. I would like to ask you: how did you automate the command when starting the VDI? You can publish the solution to automate “adobe_prtk.exe” –tool = VolumeSerialize –provfile = ”prov.xml” –stream, to be launched at every virtual machine start

        Reply
  5. Nicola

    Hi Rens Hollanders, thanks for the article! it was very very helpful in solving my problem in a Citrix Farm with VDI MCS. I would like to ask you: how did you automate the command when starting the VDI? You can publish the solution to automate “adobe_prtk.exe” –tool = VolumeSerialize –provfile = ”prov.xml” –stream to be launched at every virtual machine start

    Reply
    1. Rens Hollanders Post author

      Hi Nicola,

      Thanks for your kind replies on my website and LinkedIn. To manage the command line to be executed at the start of every VM. This can be done via either a computer configuration GPO or a scheduled task to run after the computer has finished booting.

      Kind regards,

      Rens

      Reply

Leave a Reply to Adobe Actions Cancel reply

Your email address will not be published.