can acrobat std DC be deployed via the userconfig.xml as opposed to globally?

Report · Nov 09, 2015

Hi,

I am sequencing Acrobat Standard DC and have followed the app-v deployment guide App-V Deployment: Acrobat DC — Enterprise Administration Guide but our VDI environment is user-based and not machine-based so deploying globally will not work.

Is there any way I can deploy using the userconfig.xml and ensure the license is activated?

Report · Nov 09, 2015

I don't think so. Installs are per machine and not per user.

On the other hand, my App-V knowledge is limited so I'll forward this question to an expert for the Final Answer.

Ben

Report · Nov 10, 2015

As Ben suggested user specific deployment is not supported. For your scenario and activation need, there is a workaround which should make it work -

To publish globally we write scripts in the Machine scripts section in the deploymentconfig.xml. To resolve your case create the same script extension points (as done under MachineScripts) by adding the script calls inside UserScripts section in the Userconfig.xml (for script details please refer to Post Sequencing section: http://www.stage.adobe.com/devnet-docs/acrobatetk/tools/AdminGuide/appvacrobatDC.html#post-sequencin...)

However, this is untested and supported scenario and hence there could be certain functionalities that might not work.

Report · Nov 10, 2015

Hi binnysach,

I don't think that will work as any scripts run from here will be run in the user context (so not elevated as all our users have basic rights) but I will try it. However to get to this point I need to create the prov.xml from the APTEE and incorporate this into the sequence.

I have run the elevated command (see below - I have blocked out the serial number but I used it with and without hyphens with the same result) to generate the XML file but I am getting Return Code 32 which relates to "Invalid SLConfig path". Can you tell me what this means please and how to get around it? I am running this on a machine connected to the internet.

adobe_prtk.exe --tool=VolumeSerialize --generate --serial=<myserialnumber> --regsuppress=ss

Report · Nov 10, 2015

Please generate prov.xml via given command -

adobe_prtk.exe --generate --tool=VolumeSerialize --leid=

Refer to the given link for LEID details - https://www.adobe.com/devnet-docs/acrobatetk/tools/AdminGuide/identify.html

Thanks,

binny

Report · Nov 11, 2015

Hi binny,

I have run that command with the --serial=<myserialnumber> and LEID parameters but I now get Return Code 14.

The oobelib log file ends with "Failed to validate the serial number" but I know the serial number works when I do a manual install of DC. Could it be that the serial number I have been supplied with is incompatible with the APTEE/enterprise deployment method or perhaps something is blocked when attempting authentication? Below is the log file contents (serial number crossed out). The LEID is for the Classic version but I have also tried it for Continuous and ETLA with the same results:

11/11/15 09:30:28:217 | [INFO] | | | | PCDService | | | 5644 | PCD Service in non-threaded mode
11/11/15 09:30:28:217 | [INFO] | | | | DispatchClientLib | | | 5644 | Dispatch table loaded from path: C:\Apps\AdobeStd_DC\APTEE\dispatchtable.xml
11/11/15 09:30:28:217 | [INFO] | | | | DispatchClientLib | | | 5644 | (re)load Local Dispatch Table status-[0].
11/11/15 09:30:28:217 | [INFO] | | | | DispatchClientLib | | | 5644 | Scope : [2]
11/11/15 09:30:28:217 | [INFO] | | | | DispatchClientLib | | | 5644 | Setting scope to GM
11/11/15 09:30:28:342 | [ERROR] | | | | OPMWrapper | | | 5644 | Failed in getting value for key in OPMGetValueForKey
11/11/15 09:30:28:342 | [INFO] | | | | OOBELib | | | 5644 | Failed to get Proxy username in OPM DB
11/11/15 09:30:28:358 | [INFO] | | | | AXFBLicensing | | | 5644 | Failed to load axlibv7.dll, trying again
11/11/15 09:30:28:358 | [INFO] | | | | AXFBLicensing | | | 5644 | Failed to load axlibv7.dll, trying again with axlib in ACF
11/11/15 09:30:28:358 | [INFO] | | | | AXFBLicensing | | | 5644 | Failed to load axlibv7.dll from ACF
11/11/15 09:30:28:358 | [INFO] | | | | OOBELib | | | 5644 | Received Params for Online Validation : Driver : V7{}AcrobatESR-12-Win-GM, Caller : 3
11/11/15 09:30:28:358 | [INFO] | | | | OOBELib | | | 5644 | received LEID : V7{}AcrobatESR-12-Win-GM
11/11/15 09:30:28:358 | [INFO] | | | | OOBELib | | | 5644 | Supported Locales : ALL
11/11/15 09:30:28:358 | [INFO] | | | | OOBELib | | | 1984 | OOBELib ValidateSerialOnline
11/11/15 09:30:28:358 | [INFO] | | | | DispatchClientLib | | | 1984 | Scope : [2]
11/11/15 09:30:28:358 | [INFO] | | | | DispatchClientLib | | | 1984 | Setting scope to GM
11/11/15 09:30:28:358 | [INFO] | | | | OOBELib | | | 1984 | Validate using Driver LEID : V7{}AcrobatESR-12-Win-GM, App LEID : <blank>, SN : XXXXXXXXXXXXXXXXXXXXXXX
11/11/15 09:30:28:373 | [ERROR] | | | | OOBELib | | | 1984 | Failed to get system default proxy in setProxyCredentialsForIALSession
11/11/15 09:30:28:373 | [INFO] | | | | OOBELib | | | 1984 | Failed to set proxy credentials for IAL session while validating serial number
11/11/15 09:30:28:373 | [INFO] | | | | OOBELib | | | 1984 | IALClient IAL_SetCaller-[0] took-[0.00]ms.
11/11/15 09:30:28:373 | [INFO] | | | | DispatchClientLib | | | 1984 | EndPoint requested: [AES]
11/11/15 09:30:28:373 | [INFO] | | | | DispatchClientLib | | | 1984 | Length of the URL: [51]
11/11/15 09:30:28:373 | [INFO] | | | | DispatchClientLib | | | 1984 | Returning from getEndpointAddr: [0]
11/11/15 09:30:28:373 | [INFO] | | | | DispatchClientLib | | | 1984 | EndPoint requested: [AES]
11/11/15 09:30:28:373 | [INFO] | | | | DispatchClientLib | | | 1984 | Length of the URL: [51]
11/11/15 09:30:28:373 | [INFO] | | | | DispatchClientLib | | | 1984 | URL found [https://lm.licenses.adobe.com/aes/aes/v1/serialInfo]
11/11/15 09:30:28:373 | [INFO] | | | | DispatchClientLib | | | 1984 | Returning from getEndpointAddr: [0]
11/11/15 09:30:28:389 | [INFO] | | | | OOBELib | | | 1984 | HTTPCommunicationAgent::processMessage is https://lm.licenses.adobe.com/aes/aes/v1/serialInfo (extURL=)
11/11/15 09:30:49:460 | [ERROR] | | | | OOBELib | | | 1068 | windows error: 12002
11/11/15 09:30:49:460 | [INFO] | | | | OOBELib | | | 1984 | HTTPCommunicationAgent- Return Code:[163] response size-[0] time taken-[21062.15]ms.
11/11/15 09:30:49:460 | [INFO] | | | | OOBELib | | | 1984 | Validate Serial status-[419] took-[21067.91]ms.
11/11/15 09:30:49:460 | [INFO] | | | | OOBELib | | | 1984 | IALClient IAL_SetCaller-[0] took-[0.00]ms.
11/11/15 09:30:49:460 | [ERROR] | | | | OOBELib | | | 1984 | OOBELib IAL Communication Error Win HTTP Failure
11/11/15 09:30:49:460 | [ERROR] | | | | OOBELib | | | 1984 | OOBELib IAL ValidateSerial call has failed : 419
11/11/15 09:30:49:460 | [ERROR] | | | | OOBELib | | | 1984 | Using Driver/ALL combination for offline/invalid SNs scenario
11/11/15 09:30:49:460 | [ERROR] | | | | OOBELib | | | 1984 | SN validated for AAMEE mode
11/11/15 09:30:49:460 | [INFO] | | | | OOBELib | | | 1984 | OOBELib stat = 257
11/11/15 09:30:49:616 | [ERROR] | | | | Adobe PRTK | | | 5644 | Failed to validate the serial number

Report · Nov 13, 2015

OK, I have managed to get a prov.xml (generated from Adobe based on my serial number) and incorporated this along with the publish.ps1, unpublish.ps1, adobe_prtk.exe and dispatchtable.xml into the sequence.

Can you please confirm the correct argument for the publishing script command - in particular the note "Publish script takes Volume Serialize as an optional argument to volume serialize the product. Otherwise, Acrobat is deployed in trial mode on the client machine." Does that mean the correct powershell argument should include -Volume Serialize as well? The current argument I am using is below but DC is running in trial mode after deployment:

-f "[{AppVPackageRoot}]\..\Scripts\Publish.ps1" 6308aa96-5345-4f7d-8680-787929fcb8d6 "[{AppVPackageRoot}]\Acrobat\Acrobat.exe" -ChannelName 2015 -Serialize

(Channel Name is 2015 as I am using Classic)

Report · Nov 16, 2015

Hi Douglas,

Here sharing you the details of steps which we followed to deploy package via user scripts. This has worked for us and thus suggested the same to you.

Created the package per the instruction given @ http://www.stage.adobe.com/devnet-docs/acrobatetk/tools/AdminGuide/appvacrobatDC.html#creating-an-ap...
Post sequencing, we added the following scripts to the UserConfig.xml (the scripts not to be added in the DeploymentConfig.xml)
1. Uncomment and add the scripts under UserScripts section

<Path>powershell.exe</Path>

<Arguments>-f "[{AppVPackageRoot}]\..\Scripts\Publish.ps1" <Package GUID copied from PackageID> "[{AppVPackageRoot}]\Acrobat\Acrobat.exe" -ChannelName “2015” -Serialize</Arguments>

</PublishPackage>

<Path>powershell.exe</Path>

<Arguments>-f "[{AppVPackageRoot}]\..\Scripts\Unpublish.ps1" -ChannelName “2015”</Arguments>

</UnpublishPackage>

3. We thereafter deployed the package locally using the following commands from PowerShell console launched in Administrative mode.

Enabled Scripts –
1. Set-ExecutionPolicy RemoteSigned – Force
2. Set-AppvClinetConfiguration –EnablePackageScripts 1
Added the package via
1. Add-AppvClientPackage –Path [Path_to_AppV_Package]
Published the same via
1. Publish-AppvClientPackage –Name [Package Name] –DynamicUserConfigurationPath [Path to UserConfig.XML]

4. Launch the Acrobat after publishing. Log in with Adobe ID and it launches as serialized product.

Please walk through and see what is the deviation that you did due to which Acrobat launches in trial.

Thanks,

binny

Report · Nov 16, 2015

Hi binny,

Thanks for the info - the deviation is in the deployment method.

Your method is fine if the end-user is an administrator deploying the sequence locally but unfortunately the users we deploy to are not admins and deployment is via VDI.

Launching PowerShell has to be done as an admin so therefore deploying to the userconfig XML will not filter through to the standard (non-admin) user.

Report · Nov 17, 2015

OK I now have a licensed app on VDI - this was achieved by using the AddPackage script command in the DeploymentConfig.XML and dropping the UserConfig XML when importing the sequence.

The only issue now remaining is when I try to create PDF's from DOCX/XLSX (works fine for TXT files) - I get the following error. Is this to do with (the lack of) interaction with Office 2013 or is it due to having a virtualised Adobe PDF Printer inside the sequence?

COM Integration Mode is set to

</COM>

Object Interaction is set to

Report · Nov 18, 2015

One need install the supplementary App-V MSI Downloads on the user’s machine which contain Acrobat’s integration points for applications such as:

MS Office Integration - Context Menu and In-App Acrobat Ribbons.
Mails Integration - MS Outlook and Lotus Notes will start showing Acrobat Features.
Adobe PDF Printer - Allows the user to print any file to Adobe PDF.
Web Capture - Allows the user to be able to convert a webpage to Adobe PDF inside the Browser.
Registers necessary fonts on the client which will be used by the virtual application.

The same can be downloaded from http://www.stage.adobe.com/devnet-docs/acrobatetk/tools/AdminGuide/appvacrobatDC.html#msi-downloads

Please note this MSI has been designed specifically with machine based deployment. This has not been validated and tried with the user specific deployment.

Report · Nov 19, 2015

Hi binny,

Your link doesn't work but if you mean the App-V kits under "MSI Downloads" from App-V Deployment: Acrobat DC — Enterprise Administration Guide then installing these did not make any difference even on a machine-based deployment.

I have read elsewhere that the reason for the creation failure from Office apps is due to Acrobat needing its print driver to perform this function which is not supported in App-V. Can you please confirm or clarify the situation with this?

Report · Nov 22, 2015

Oops. Mistakenly, provided stage link. Yes the link you mentioned is correct.

Right, as mentioned to make PDF Maker/printer work you would need the App-V MSI as mentioned above needs to be installed on the client machine.

Report · Jul 05, 2016

"Please note this MSI has been designed specifically with machine based deployment. This has not been validated and tried with the user specific deployment."

I tried it. Still not installing the "Adobe PDF" printer.

Should I set a different installation path other than the default "c:\program files (x86)\adobe\acrobat 2015\"? It clearly does not match the actual location of the AppV package installation.

No additional documentation is provided in regards to this supplementary MSI's.

Report · Sep 21, 2016

Hi

I am also struggling with this. I can get the scripts / serializing to work but only under certain conditions, which won't suit our environment. ideally I would like to publish to users of Citrix Published Desktop (RDS) I have followed the instructions from Adobe and can confirm it works when the package is published Globally and using the DeploymentConfig.xml file and Adobe Publish1.ps script. This is not suitable as all users on that server will see the Adobe functions as the application interactions are enabled globally.

I have also had partial success using the Userconfig.xml and Publish1.ps. As users are not administrators the script to serialise Adobe fails. If add the App-V package and publish it using an administrator, users are then able to use the package if published to them.

I have tried to use <AddPackage> path to publish1.ps within the deploymentconfig.xml file but again this fails to work when ran as a standard user.

This forum seems to be related to a VDI environment but I would have thought the principles are the same. I am interested to know who you got it working... Any help appreciated...

Your Quote

"OK I now have a licensed app on VDI - this was achieved by using the AddPackage script command in the DeploymentConfig.XML and dropping the UserConfig XML when importing the sequence"

David

Report · Sep 21, 2016

Sorry for the confusion.... I re-read this topic and realised my mistake. After loading the deploymentconfig.xml correctly (I originally did it under the user assigned configuration in App-V Mgmt Console) it now works. I will expect some issues later but just relieved to get this far..

Adobe Community

can acrobat std DC be deployed via the userconfig.xml as opposed to globally?

1 Correct answer