Quantcast
Channel: Adobe Community: Message List - Enterprise Deployment (Acrobat and Reader)
Viewing all 6853 articles
Browse latest View live
↧

Re: Reader DC not set as default after using customization wizard and SCCM. Windows 10 Entx64

November 8, 2015, 12:16 pm
$
0
0

sourabsharma wrote:

 

Please use parameter "OWNERSHIP_STATE=2" in your command to install . It will set Reader as default PDF handler for all existing users on machine.

New Command to install will be : msiexec /i "AcroRead.msi" /q TRANSFORMS="AcroRead.mst" OWNERSHIP_STATE=2  /L* "%temp%\Acrobat Reader DC install.log".

Yes i tried that as per Custom transform file from Acrobat Wizard not applying to Acrobat DC installation

 

I agree, it seems to be a windows 10 issue - although the file handler was updated immediately when installed for the current user without requiring logoff/restart

↧
Search

Re: Custom transform file from Acrobat Wizard not applying to Acrobat DC installation

November 8, 2015, 12:17 pm
$
0
0

Yes, Windows 10 Enterprise x64 build 10240

I have emailed the systeminfo, Transform and setup file used - let me know if you need them zipped before sending

↧
↧

Re: No Pages Selected RDS Server 2012r2

November 8, 2015, 4:11 pm
$
0
0

We are having issues with all pdf readers here on our RDS 2012r2 servers. I solved the printing issue by logging on as local administrator in the servers and loading the printers as system printers. But there still is an issue where occasionally and randomly, people cannot open pdf's from server shares. Clicking on Open in the reader does not show any server shares. I think its an issue with how server 2012r2 has shares set up but not sure

↧

Re: Custom transform file from Acrobat Wizard not applying to Acrobat DC installation

November 9, 2015, 2:28 am
$
0
0

Sorry I didn't get the files. Please send them directly to my email.

Also, on Windows 10, current logged in user will get the updated pdf handler, already created users will receive it after log off and new users will have to set it explicitly via Product preference or File-> Open With.

↧

burning adobe pro file with paths to dvd

November 9, 2015, 7:06 am
$
0
0

Good morning folks,

 

I'm attempting to burn a PDF file to disk created in Acrobat XI (ver 11.0.13), that references files in a folder on the root of the disk.  I am unable to change the file path so that when it's on a disk and given to someone else, that they are able to open the referenced file from clicking on a bookmark.  I have been able to do this in the past, but I'm thinking it may have been before we upgraded our Acrobat.

 

Any help would be appreciated.

 

Shane

↧
↧

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

November 9, 2015, 9:10 am
↧

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

November 9, 2015, 9:54 am
$
0
0

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

↧

Re: Custom transform file from Acrobat Wizard not applying to Acrobat DC installation

November 9, 2015, 12:28 pm
$
0
0

Mohd Amish wrote:

 

Also, on Windows 10, current logged in user will get the updated pdf handler, already created users will receive it after log off and new users will have to set it explicitly via Product preference or File-> Open With.

 

Hmmmm in this case it looks like it wont be resolvable at all then, as this is for a base image - every user will be newly created.

Is this an issue with how winodws 10 handles defaults, or is it by design (which would be.... annoying)

 

I have resent the files anyway

↧
Search

customisation wizard - invalid installer package

November 10, 2015, 1:05 am
$
0
0

I been having big problems using the customization wizard on OS X. I been successful using it with Acrobat DC but as soon as I try to use it with Reader DC I get “invalid installer package” whatever installer pkg I choose. I have gotten a distribution version, with permission from You, Adobe, to distribute, AcroRdrDC_1500920069_MUI. This version doesent help either. There is no custwiz.log created even. I have verified all the installers functionality by manual installs. When using customization wiz, I have done it on clean OS, clean VM. Tried fresh version of the wizard itself. Besides the version mention above I have tried offline installer, universal as well as English for OS X 10.10. Please advice and or point me to a valid installer.

Thx

/jens

↧
↧

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

November 10, 2015, 2:08 am
$
0
0

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 -sequencing-steps)

 

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

↧

Re: Custom transform file from Acrobat Wizard not applying to Acrobat DC installation

November 10, 2015, 5:54 am
$
0
0

Yes. This is how OS handle defaults in Windows 10. In latest Windows 10 Update (TH2), Microsoft forces Edge to be the default pdf handler for the current user as well.

Relevant folks are following it up and I will update the thread when we have some information.

↧

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

November 10, 2015, 7:59 am
$
0
0

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

↧

Re: How do I keep updates enabled but disable DC update prompt?

November 10, 2015, 8:14 am
$
0
0

Thank you for the help! Problem solved. I marked LeoAdobeX's response as the correct answer.

↧
↧

Re: customisation wizard - invalid installer package

November 10, 2015, 8:58 am
$
0
0

Unlike the Windows version of the Adobe Customization Wizard DC, the Mac version of the Adobe Customization Wizard DC does not consume Acrobat Reader DC packages for customizing.  It is still possible to add these customizations via creating PLIST files.

↧

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

November 10, 2015, 9:35 am
↧
Search

Re: customisation wizard - invalid installer package

November 11, 2015, 1:28 am
$
0
0

Big thanks for your reply Steve!

But this article: Feature lockdown — Customization Wizard DC for Mac seems to be of a different point of view "

  1. Create a plist file named com.adobe.Acrobat.Pro.plist or com.adobe.Reader.plist.
  2. Check Enable Feature Lockdown.
  3. Browse to the plist file you created.
  4. Choose OK.

That, to me, indicates that the wizard could be used with reader

cheers

/jens

↧

Re: customisation wizard - invalid installer package

November 11, 2015, 1:35 am
$
0
0

ok, seems like it works like a charm with just putting a com.adobe.Reader.plist in the system library. Still that article lead me in the wrong direction, hope that nobody else has to go through that.

↧
↧

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

November 11, 2015, 1:47 am
$
0
0

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:202 | [INFO] |  |  |  | Adobe PRTK |  |  | 5644 | __OOBELIB_LOG_FILE__
11/11/15 09:30:28:202 | [INFO] |  |  |  | Adobe PRTK |  |  | 5644 | *** Adobe PRTK tool START ***
11/11/15 09:30:28:202 | [INFO] |  |  |  | Adobe PRTK |  |  | 5644 | Adobe PRTK tool VolumeSerialize invoked
11/11/15 09:30:28:217 | [ERROR] |  |  |  | Adobe PRTK |  |  | 5644 | .
11/11/15 09:30:28:217 | [INFO] |  |  |  | Adobe PRTK |  |  | 5644 | creating  .\prov.xml
11/11/15 09:30:28:217 | [INFO] |  |  |  | OOBELib |  |  | 5644 | *************OOBELib Session Starts*************
11/11/15 09:30:28:217 | [INFO] |  |  |  | OOBELib |  |  | 5644 | Version 9.0.0.26,7.0

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

11/11/15 09:30:49:616 | [INFO] |  |  |  | Adobe PRTK |  |  | 5644 | Return code 14
11/11/15 09:30:49:616 | [INFO] |  |  |  | Adobe PRTK |  |  | 5644 | *** Adobe PRTK tool END ***

↧

How to patch Acrobat Standard DC

November 12, 2015, 10:27 am
$
0
0

Trying to follow same exact steps to update Acrobat Standard DC that I've used with Acrobat Standard X and not having success. Was hoping someone could weigh in, tell me what I'm doing wrong.

 

I've downloaded the "base" installer (Acrobat_2015_Web_WWMUI.exe) from the Adobe Licensing website. I extract it, and am left with bunch of different files, including the AcroPro.msi file, which is version 15.006.30033 according to Orca and the Adobe Customization Wizard.

 

I then downloaded the latest quarterly patch (Classic Track - Acrobat2015Upd1500630094.msp) from the Adobe Downloads site.

 

From a command prompt, I ran the following:

 

msiexec /a d:\adobe\acropro.msi /update Acrobat2015Upd1500630094.msp

 

After a minute or so the update completes. I check the version of the AcroPro.msi file and it now reports 15.006.30094.

 

I deploy using Group Policy, but here is where the installation fails. There is an error message in the Windows Application log stating, "Product: Adobe Acrobat DC -- Error 1334.The file 'dropboxstorage.api' cannot be installed because the file cannot be found in cabinet file 'Data1.cab'. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package."

 

I remember a while back having this problem (missing files in the Data1.cab) and it being the result of my trying to apply the quarterly patch to an already patched MSI, rather than applying the quarterly patch to the base MSI file. But as far as I can tell, that's not happening here - I'm applying the patch to the base MSI.

 

Thoughts?

↧

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

November 13, 2015, 6:41 am
$
0
0

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 VolumeSerialize 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)

↧
Viewing all 6853 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>