Whoops: I should credit user kglad for posting that link to the original question asker's thread.

Thanks, kglad!

Use the reg pref here: Services integration (bAdobeSendPluginToggle)

If you're following the Wiz instruction (loading a pkg, not running from a dmg image, etc) and the CCP instructions in the Admin Guide, then I don't have the knowledge to help (not a mac user). I'll try to find someone who might know.

Ben

Hi,

I am looking to utilize 'Adobe Acrobat Pro DC'  via a Terminal Server (Multiple users via 'Dumb' Terminals).

My questions are as follows:

1. Will each 'User/Machine' accessing the Terminal Server require a dedicate Adobe License?

         - If so what licensing (Product Code/Number) will I need to purchase?
or

2. Will a single 'Adobe Acrobat Pro DC' license cover all Users accessing the software via a Terminal Server?

Any help would be appreciated, Thank you.

Steve,

Pointing out the line that says "Failed to validate the serial number" does not help the customer with his problem.  We know the validation failed; that goes with code 14.  What the customer needs is help finding WHY it failed.  Also, I need the same.

In my own case, I have checked network connectivity and can reach adobe servers. 

I'm using a serial number retrieved from a redemption code for Acrobat DC (12).  I have entered the serial number with no spaces, with spaces, and with hyphens instead of spaces.  Now, pay attention to this:

I HAVE HAD A CO-WORKER CHECK MY TYPING TO ENSURE THAT I ENTERED THE SERIAL CODE CORRECTLY.

Also, we are working from a printout of the serial code as provided by Adobe, NOT manually copied from the screen.

Several lines above the "Failed" line, the error log (running on a separate machine or I'd copy/paste it) says that this is an "OOBELib Bad Serial Number."  Given that this serial is a printout from Adobe and HAS BEEN TYPED CORRECTLY, then that's IMPOSSIBLE.

What is going on??

I've deployed Adobe Reader DC using the msi and transform created with the Acrobat Customization Wizard DC. 

It install fine but when users first run Reader they are prompted for an administrator credentials because the program C:\Program Files (x86)\Adobe\Acrobat Reader DC\Reader\ADelRCP.exe is trying to run.

Our users do have local admin rights.  How do I prevent this popup occuring on Reader startup and what does this ADelRCP.exe do?

Check a couple of things:

Is the URL used by the Adobe Customization Wizard being blocked by a firewall, proxy, security software, etc...

Does the PRTK tool work on it's own to validate the serial number?  In other words, are you able to serialize a default installation using the Adobe Provisioning Tool?

The URL is NOT blocked by our firewall.  I administer the firewall, so that was easy to check.  We don't use proxies and blockers and security software have been pushed aside or disabled.  I even tried this on a bare machine.

As far as the provisioning tool, I haven't used it. However, I did use this serial number on an installation and it validated perfectly fine, with the security software turned on.  That's how we discovered Adobe's obstructive, useless "constant sign-in required" which would not be a proper set-up for that multi-user workstation.  (PLEASE DO NOT try to argue why or why not this would not function for that workstation.  That is not the topic here.  The topic is getting the customization wizard to function properly.)  I did not sign in.  After researching how to disable this idiocy, I stayed on-line and did a proper removal, allowing the Adobe un-installer to do the work.  Ultimately, the key code has already been demonstrated to be valid and is not in use.

Let's remember that Adobe regularly publishes broken software with lame, hard-coded requirements.  For example, many Adobe installers require that one be logged in as the local machine administrator, not just a user with local admin privileges.  Also, the local admin CANNOT be renamed, which is a step many shops take for security reasons, but Adobe can't figure out how to require only admin priv's, rather than hard coding a specific username.  In the previous iteration of the Customization Wizard, version 11, there was a hard-coded leftover from version 10 where an executable would get called from the version 10 folder, which does not exist on a version 11 installation of the customization wizard.  The workaround was to manually create the version 10 folders and copy the v11 executable in question into the folder, but run the main program from the proper version 11 folder.  All that to point out that Adobe regularly publishes broken software.

Now, what mysterious little ticks are broken in the DC version of CW & how do I work around them?

Here is the error log from today's attempt at running the Wizard.  I've tried looking into the axlibv7.dll file and gotten nowhere.

12/10/15 10:22:43:284 | [INFO] |  |  |  | Adobe PRTK |  |  | 724 | *** Adobe PRTK tool START ***

12/10/15 10:22:43:284 | [INFO] |  |  |  | Adobe PRTK |  |  | 724 | Adobe PRTK tool VolumeSerialize invoked

12/10/15 10:22:43:284 | [ERROR] |  |  |  | Adobe PRTK |  |  | 724 | C:\Users\ADMINI~1\AppData\Local\Temp\CusE88B1100

12/10/15 10:22:43:284 | [INFO] |  |  |  | Adobe PRTK |  |  | 724 | creating  C:\Users\ADMINI~1\AppData\Local\Temp\CusE88B1100\prov.xml

12/10/15 10:22:43:284 | [INFO] |  |  |  | OOBELib |  |  | 724 | *************OOBELib Session Starts*************

12/10/15 10:22:43:284 | [INFO] |  |  |  | OOBELib |  |  | 724 | Version 9.0.0.21,7.0

12/10/15 10:22:43:284 | [INFO] |  |  |  | PCDService |  |  | 724 | PCD Service in non-threaded mode

12/10/15 10:22:43:284 | [INFO] |  |  |  | DispatchClientLib |  |  | 724 | Dispatch table loaded from path: C:\Users\ADMINI~1\AppData\Local\Temp\CusE88B.tmp\dispatchtable.xml

12/10/15 10:22:43:284 | [INFO] |  |  |  | DispatchClientLib |  |  | 724 | (re)load Local Dispatch Table status-[0].

12/10/15 10:22:43:284 | [INFO] |  |  |  | DispatchClientLib |  |  | 724 | Scope : [2]

12/10/15 10:22:43:284 | [INFO] |  |  |  | DispatchClientLib |  |  | 724 | Setting scope to GM

12/10/15 10:22:44:033 | [ERROR] |  |  |  | OPMWrapper |  |  | 724 | Failed in getting value for key in OPMGetValueForKey

12/10/15 10:22:44:033 | [INFO] |  |  |  | OOBELib |  |  | 724 | Failed to get Proxy username in OPM DB

12/10/15 10:22:44:033 | [INFO] |  |  |  | AXFBLicensing |  |  | 724 | Failed to load axlibv7.dll, trying again

12/10/15 10:22:44:033 | [INFO] |  |  |  | AXFBLicensing |  |  | 724 | Failed to load axlibv7.dll, trying again with axlib in ACF

12/10/15 10:22:44:033 | [INFO] |  |  |  | AXFBLicensing |  |  | 724 | Failed to load axlibv7.dll from ACF

12/10/15 10:22:44:033 | [INFO] |  |  |  | OOBELib |  |  | 724 | Received Params for Online Validation : Driver : V7{}AcrobatESR-12-Win-GM, Caller : 3

12/10/15 10:22:44:048 | [INFO] |  |  |  | OOBELib |  |  | 724 | received LEID : V7{}AcrobatESR-12-Win-GM

12/10/15 10:22:44:048 | [INFO] |  |  |  | OOBELib |  |  | 724 | Supported Locales : ALL

12/10/15 10:22:44:048 | [INFO] |  |  |  | OOBELib |  |  | 760 | OOBELib ValidateSerialOnline

12/10/15 10:22:44:048 | [INFO] |  |  |  | DispatchClientLib |  |  | 760 | Scope : [2]

12/10/15 10:22:44:048 | [INFO] |  |  |  | DispatchClientLib |  |  | 760 | Setting scope to GM

12/10/15 10:22:44:048 | [INFO] |  |  |  | OOBELib |  |  | 760 | Validate using Driver LEID : V7{}AcrobatESR-12-Win-GM, App LEID : <blank>, SN : 910182170481708027387763

12/10/15 10:22:44:048 | [ERROR] |  |  |  | OOBELib |  |  | 760 | Failed to get system default proxy in setProxyCredentialsForIALSession

12/10/15 10:22:44:048 | [INFO] |  |  |  | OOBELib |  |  | 760 | Failed to set proxy credentials for IAL session while validating serial number

12/10/15 10:22:44:048 | [INFO] |  |  |  | OOBELib |  |  | 760 | IALClient IAL_SetCaller-[0] took-[0.00]ms.

12/10/15 10:22:44:048 | [INFO] |  |  |  | DispatchClientLib |  |  | 760 | EndPoint requested: [AES]

12/10/15 10:22:44:048 | [INFO] |  |  |  | DispatchClientLib |  |  | 760 | Length of the URL: [51]

12/10/15 10:22:44:048 | [INFO] |  |  |  | DispatchClientLib |  |  | 760 | Returning from getEndpointAddr: [0]

12/10/15 10:22:44:048 | [INFO] |  |  |  | DispatchClientLib |  |  | 760 | EndPoint requested: [AES]

12/10/15 10:22:44:048 | [INFO] |  |  |  | DispatchClientLib |  |  | 760 | Length of the URL: [51]

12/10/15 10:22:44:048 | [INFO] |  |  |  | DispatchClientLib |  |  | 760 | URL found [https://lm.licenses.adobe.com/aes/aes/v1/serialInfo]

12/10/15 10:22:44:048 | [INFO] |  |  |  | DispatchClientLib |  |  | 760 | Returning from getEndpointAddr: [0]

12/10/15 10:22:44:111 | [INFO] |  |  |  | OOBELib |  |  | 760 | HTTPCommunicationAgent::processMessage is https://lm.licenses.adobe.com/aes/aes/v1/serialInfo (extURL=)

12/10/15 10:22:44:938 | [INFO] |  |  |  | OOBELib |  |  | 2384 | HTTP Request Status code 200.

12/10/15 10:22:44:938 | [INFO] |  |  |  | OOBELib |  |  | 760 | HTTPCommunicationAgent- Return Code:[0] response size-[3172] time taken-[821.19]ms.

12/10/15 10:22:44:938 | [INFO] |  |  |  | OOBELib |  |  | 760 | Validate Serial status-[0] took-[887.02]ms.

12/10/15 10:22:44:938 | [INFO] |  |  |  | OOBELib |  |  | 760 | IALClient IAL_SetCaller-[0] took-[0.00]ms.

12/10/15 10:22:44:938 | [INFO] |  |  |  | OOBELib |  |  | 760 | OOBELib No associated locales returned by IAL

12/10/15 10:22:44:938 | [INFO] |  |  |  | DispatchClientLib |  |  | 760 | Scope : [2]

12/10/15 10:22:44:938 | [INFO] |  |  |  | DispatchClientLib |  |  | 760 | Setting scope to GM

12/10/15 10:22:44:938 | [INFO] |  |  |  | DispatchClientLib |  |  | 760 | EndPoint requested: [GetSLConfig]

12/10/15 10:22:44:938 | [INFO] |  |  |  | DispatchClientLib |  |  | 760 | Length of the URL: [58]

12/10/15 10:22:44:938 | [INFO] |  |  |  | DispatchClientLib |  |  | 760 | Returning from getEndpointAddr: [0]

12/10/15 10:22:44:938 | [INFO] |  |  |  | DispatchClientLib |  |  | 760 | EndPoint requested: [GetSLConfig]

12/10/15 10:22:44:938 | [INFO] |  |  |  | DispatchClientLib |  |  | 760 | Length of the URL: [58]

12/10/15 10:22:44:938 | [INFO] |  |  |  | DispatchClientLib |  |  | 760 | URL found [https://lm.licenses.adobe.com/arlm/slconfig/v1/getSLConfig]

12/10/15 10:22:44:938 | [INFO] |  |  |  | DispatchClientLib |  |  | 760 | Returning from getEndpointAddr: [0]

12/10/15 10:22:44:938 | [INFO] |  |  |  | OOBELib |  |  | 760 | HTTPCommunicationAgent::processMessage is https://lm.licenses.adobe.com/arlm/slconfig/v1/getSLConfig (extURL=)

12/10/15 10:22:45:359 | [INFO] |  |  |  | OOBELib |  |  | 2888 | HTTP Request Status code 200.

12/10/15 10:22:45:468 | [INFO] |  |  |  | OOBELib |  |  | 760 | HTTPCommunicationAgent- Return Code:[0] response size-[37520] time taken-[519.25]ms.

12/10/15 10:22:45:484 | [INFO] |  |  |  | OOBELib |  |  | 760 | Get SLConfig File Data status-[0] took-[549.94]ms.

12/10/15 10:22:45:484 | [DEBUG] |  |  |  | OOBELib |  |  | 760 | File successfully downloaded

12/10/15 10:22:45:484 | [DEBUG] |  |  |  | OOBELib |  |  | 760 | Creating the SLConfigs folder

12/10/15 10:22:45:484 | [DEBUG] |  |  |  | OOBELib |  |  | 760 | Creating the folder for leid

12/10/15 10:22:45:484 | [DEBUG] |  |  |  | OOBELib |  |  | 760 | Creating/Updating SLConfig.xml

12/10/15 10:22:45:484 | [DEBUG] |  |  |  | OOBELib |  |  | 760 | Error creating SLConfig.xml

12/10/15 10:22:45:484 | [INFO] |  |  |  | OOBELib |  |  | 760 | checking LEID V7{}AcrobatESR-12-Win-GM

12/10/15 10:22:45:484 | [INFO] |  |  |  | OOBELib |  |  | 760 | LEID : V7{}AcrobatESR-12-Win-GM qualifies for install

12/10/15 10:22:45:484 | [ERROR] |  |  |  | OOBELib |  |  | 760 | Cannot accept a Retail SN in the AAMEE workflow

12/10/15 10:22:45:484 | [ERROR] |  |  |  | OOBELib |  |  | 760 | Using Driver/ALL combination for offline/invalid SNs scenario

12/10/15 10:22:45:484 | [ERROR] |  |  |  | OOBELib |  |  | 760 | SN validated for AAMEE mode

12/10/15 10:22:45:484 | [INFO] |  |  |  | OOBELib |  |  | 760 | OOBELib stat = 27

12/10/15 10:22:46:076 | [ERROR] |  |  |  | Adobe PRTK |  |  | 724 | Failed to validate the serial number

12/10/15 10:22:46:076 | [INFO] |  |  |  | Adobe PRTK |  |  | 724 | Return code 14

12/10/15 10:22:46:076 | [INFO] |  |  |  | Adobe PRTK |  |  | 724 | *** Adobe PRTK tool END ***

Are you using a VOLUME serial number or a RETAIL serial number?

Same as Citrix: Doc says "Adobe requires that organizations have a valid Acrobat software license for every user that has access to Acrobat on the Citrix  server. Note the 10.x licenses can only be used for 10.x products, 11.x licenses can only be used for 11.x products, and so on."

I've asked for a link to the latest licensing policy. Will send when in hand.

hth,

Ben

See this new video: https://youtu.be/hsRVj1JntXs

hth,

Ben

We got this installation via redemption code bundled with scanner hardware.  That would lead me to believe, as you phrase it, the 7th line, working up from the bottom of the log.

I also noticed that the 5 line up says "SN validated for AAMEE mode."  That means the serial number was validated.

So, does the CW work with only one type of license, Volume OR Retail, not each??  What does that mean for the log message that the SN was validated??

Amazing...that's all it was. I was under the impression that the .pkg installer created from the Creative Cloud Packager was the file I needed to import into the Wizard.

I just saw the video and it turns out that it is a .pkg *inside* that CCP package export that I must reference.

/<Creative Cloud Package of DC.pkg>/Contents/Resources/Setup/APRO15.0en_US/Acrobat DC/Acrobat DC Installer.pkg

I can't believe it was that simple. I should have known considering the Windows customization process is similar in that you must navigate to the exceptions folder and locate a similarly nested .MSI file.

Thank you for your response!

Hi,

How do i deploy Adobe Reader DC without it taking PDF reader ownership from another non Adobe PDF reader?

My transform file is setup as follows:

Default viewer for PDF files - Installer will decide...

Direct Editor > Properties:

DEFAULT_VERB=Open (changed this from Read)

LEAVE_PDFOWNERSHIP=YES (i added this. I also tried this in the install command line)

OWNERSHIP_STATE=0 (this is for Win8 only. I'm installing on Win7 but thought it couldn't hurt to try it)

I've tried with different variations of the above.

The other PDF reader is Nuance Power PDF Advanced. This is the one i want to remain as the PDF viewer owner.

Thanks,

Aaron

Hello,

Is it possible to deploy a certificate chain, with the Wizard tool or otherwise, during an install of Acrobat DC or Reader DC for Mac? In the Windows counterpart, there is an option to enable certificates already in the system trusted root to be used for signing, however there is no similar option I can see for Mac.

I need to have a particular certificate chain "baked-in" the install in order to allow our users to digitally sign documents properly.

The setting in question that I am referring to is found here in Preferences > Signatures > Identities & Trusted Certificates:

Is it possible perform this import either via bash/shell script or during deployment somehow?

Image may be NSFW.
Clik here to view.

Thank you very much!

Glad it worked. Real hero is the guy who authored the video and sent it to me (Steve C.).

Ben

See this: Security Setting Import-Export — Digital Signatures Guide for IT

It may also be helpful to note all the file and registry settings/prefs are nearly identical for Mac and Win. Most of the doc examples are Win, but Mac uses similar paths.

hth,

Ben

Hi, I am using adobe reader DC. I would like to customise the installation such that "protected mode at startup" feature is turned off. Currently, i am using GPO from server to client.

i have tried using the following methods below but to no avail for ALL users

Creating key into 'Destination Computer' registry using adobe customisation wizard.

[HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\10.0\Privileged]

"bProtectedMode"=dword:00000000

And tried this also,

HKLM\Software\Policies\Adobe\Acrobat Reader\10.0\FeatureLockDown\bProtectedMode with a value of 0

I have a situation where I am trying to deploy Reader DC across our enterprise using Microsoft Configuration Manager 2012.  Per our contract with Adobe we are contractually bond to deploy the latest version on all of our Desktops.  The installation, when run on certain systems, wants to install Reader as per-user rather than per-machine.  I have run the installation with verbose logging and can see in the installer log where the issue occurs.  At this point I have tried all I can to resolve the issue and find the source of the problem.

The issue does not occur on all systems, only specific ones.  SCCM 2012 uses the local SYSTEM account to install the application when it is deployed to an endpoint.  This account has full access to the system and should be able to complete the installation as a per-machine installation without issue.  Below is the information from the installer log when the installation runs per-user.  I have tried setting the MSIINSTALLPERUSER="" and ALLUSERS=2 properties at the command line to try to override the setting in the installer.  The results are the same - ALLUSERS property gets deleted.

MSI (s) (D0:D0) [15:30:04:261]: Determined that existing product (either this product or the product being upgraded with a patch) is installed per-user.

MSI (s) (D0:D0) [15:30:04:261]: PROPERTY CHANGE: Deleting ALLUSERS property. Its current value is '1'.

Message was edited by: Troy Smeltzer