I was recently tasked to install Adobe Acrobat 2017 on XenApp 7.1x. The serial number was provided and according to the vendor it is compatible with a multi-user environment such as RDS and Citrix XenApp/XenDesktop.

The install was not performed using any customized MSI to inject EULA or anything, just manually as an administrator accepting the default settings in the GUI.

However, users are now getting prompted to accept the EULA each time and it never sticks, even though I'm roaming their Adobe appdata.

I've tried setting the registry Software\Adobe\Adobe Acrobat\2017\AdobeViewer\EULAAcceptedForBrowser REG_DWORD=1, but that does not seem to work

Trying to get hold of a Adobe support appears to be impossible.

Anyone on the forum who can share how to rectify?

thanks

werner

Hello all,

Via the Adobe Creative Cloud Packager version 1.13.0 build 59 I don't manage to build a working MSI file for Adobe Acrobat. For all the other packages like Photoshop I've no problems at all.

I've made a package with my admin account and so with my user account. Added the MSI in SCCM like always. Mostly it shows up in the Software Center as Installed but it isn't on my client.

Could someone helps me out?

Microsoft has informed me that this app is using the old Intune SDK and needs to be updated. The current version was last update on Feb 8, 2017. Is there a timeline on when the next new update will be? Will it be using the most up to date SDK for Intune?

Hi Adobe, hope you can help us..

Present setup:

Windows 2012 R2 RDS Server (terminal servers)

Adobe Reader XI 11.0.10

(User profile setup, is based on standard Roaming profiles, with a standard group policy cleaning the local profile up during logoff)

Issue:

The main issue is related to the adobe reader application generates som Z@...TMP files within the users profile folder (local temp), and this files can not be deleted until the terminal server have been rebooted.. (in a terminal server/multi user environment, can the terminal servers not be reboot when users logoff, and when the users logon agin will the generates a new profile folder, eg User1.001, User.002, leaving the old folders in a mess)

Question:

At the present time, have we tried Adobe Workaround1 and Workaround2 http://blogs.adobe.com/dmcmahon/tag/acroct-ini on the present setup, but with no result, (but we can also see this description is addressed to earlier Operation Systems)..

We have also looking into Adobe´s Forum sites, where we can see issues related to the same topic but on older operation systems,

eg (Unable to delete temporary files), but we can not find answers from Adobe related to this questions dates sep14..

Q1:

Could you please help us with a workaround for the above mention windows platform (Windows 2012 R2 RDS with Adobe Reader XI or newer)

Q2:

If the present workaround1 and 2, should be supported on a Windows 2012 R2 platform, can you please help us with a more detailed description for implementing this, (eg. the present workarounds mention C:\Documents and Settings\<user>\Windows that does not exist on a Windows 2012 R2 platform.

We are looking forward to hear from you,

Kind Regards

/Steen Jensen

How do I add a customized tool (.aaui file) automatically into Acrobat 2017 without any user interaction? If this is possible, am I able to set the tools from the customized created tool to the Customized Quick Tools? (This being all without any user interaction.)

Hello,

We are running into an issue with XA7.6 on PVS 7.6 and Server 2012 R2. I can key the master machine, but the provisioned targets are challenging users for the activation key. I downloaded the latest version of the Adobe Application Manager from the Using Adobe Provisioning Toolkit Enterprise Edition link and installed it. After installing the tool (no errors), the adobe_prtk.exe utility doesn't show up any where on the hard drive. I found and older version of the tool and installed that. The adobe_prtk.exe file did show up, but when I tried to run the command-line string with the key and leid to generate the prov.eml file I get an error 14. We opened a ticket with Adobe over a week ago and can't seem to get anyone to call us. When we try to talk to support we get run in circles. It is very frustrating as you might imagine and the client is livid at this point. Any help would be greatly appreciated.

adobe_prtk.exe --tool=VolumeSerialize --generate --serial="<ENTER SERIAL #HERE>" --leid="<ENTER LEID #HERE>" --regsuppress=ss --eulasuppress

Steve

Hello,

In Feb 2017 I was able to successfully build a silent MSI install of Acrobat DC (AcroRdrDC1502320053_en_US) using the Customization Wizard and deploy the app via ManageEngine Desktop Central. My users could access the self server portal and fire up the install - and it would install perfectly - following all my specific customizations.

Now - I want to do the same with the current DC track installer (AcroRdrDC1700920044_en_US)

I expanded the exe archive using the correct command line (per the Enterprise admin guide) and I end up with the 6 key files. I then fire up the Customization Wizard and load up the acroread.MSI file from the new archive I just expanded. Then within the Customization Wizard - I choose Transform->Load Transform to get the settings previously built in Feb 2017. This loads correctly and I save the Package and deploy the files to the specific folder within my DesktopCentral environment

But when a user runs the install from the portal - the end result is not Version 2017.009.20044 - I get the old "unpatched" 2015 version that cam within the archive.

The Setup.ini file looks right - pointing the right patch within and my new transform file that was created:

[Startup]

RequireMSI=3.0

CmdLine=/sall /rs

[Product]

PATCH=AcroRdrDCUpd1700920044.msp

msi=AcroRead.msi

CmdLine=TRANSFORMS="AcroRead.mst"

But - I cannot get this package to actually install the latest patch?

What am I doing wrong here?

Appreciate any insights.

Cheers,

Bruce

I am getting ready to deploy hundreds of copies of Acrobat 17 Pro to our organization, but I can't find any customization wizard. How can I get this? Has one been built yet? I go to ftp://ftp.adobe.com/pub/adobe/acrobat/win/AcrobatDC/misc/ and only see the one for 15.

I'm trying to create a deployment via SCCM of the latest version of Adobe Acrobat Reader DC for our organization, and I'm having some difficulty getting it to work properly.  Here are the steps I've taken:

• Downloaded the executable for version 2017.012.20093 from Adobe's enterprise webpage and the patch for the latest release (2017.012.20098).
• Extracted the executable to a new folder.
• Opened the "AcroRead.msi" in Adobe Customization Wizard DC, customized the installer to my desired settings, and generated a transforms file named "AcroRead.mst" to the extracted folder.
• Removed the "AcroRdrDCUpd1701220093.msp" from the extracted folder and replaced it with "AcroRdrDCUpd1701220098.msp".
• Modified "setup.ini" as follows:
• Copied the files to my SCCM application deployment share, which contains the following files:
• Created a device collection and application in SCCM, distributed the content to my distribution points and deployed it.
• The command line is as follows:
  • msiexec /i "AcroRead.msi" TRANSFORMS="AcroRead.mst" PATCH="\\<Deployment Share File Path>\AcroRdrDCUpd1701220098.msp" /q
• Installation via SCCM is successful, but only on workstations that have a previously installed version of Adobe Acrobat Reader DC.  Deployments to workstations that do not currently have an Adobe Reader program installed fail with the following error message:
• Which translates to:
• This tells me that my application is only installing the patch (AcroRdrDCUpd1701220098.msp) instead of the .msi followed by the .msp.  As such, the installed application does not include the custom settings which I configured for it in the AcroRead.mst.
• I also tried running "setup.exe" from an administrative command prompt on my local machine, but it produced this error message:

I'd really appreciate any help or advice.

Hello,

We are running into an issue with XA7.6 on PVS 7.6 and Server 2012 R2. I can key the master machine, but the provisioned targets are challenging users for the activation key. I downloaded the latest version of the Adobe Application Manager from the Using Adobe Provisioning Toolkit Enterprise Edition link and installed it. After installing the tool (no errors), the adobe_prtk.exe utility doesn't show up any where on the hard drive. I found and older version of the tool and installed that. The adobe_prtk.exe file did show up, but when I tried to run the command-line string with the key and leid to generate the prov.eml file I get an error 14. We opened a ticket with Adobe over a week ago and can't seem to get anyone to call us. When we try to talk to support we get run in circles. It is very frustrating as you might imagine and the client is livid at this point. Any help would be greatly appreciated.

adobe_prtk.exe --tool=VolumeSerialize --generate --serial="<ENTER SERIAL #HERE>" --leid="<ENTER LEID #HERE>" --regsuppress=ss --eulasuppress

Steve

Hello

I am trying to update our deployment of Acrobat Pro Extended 9.0.0 to the latest patch, 9.1.3.

We are not deploying the updates via Group Policy, as our deployment of Acrobat Pro is "on demand", therefore I initially wish to update the administrative installation point.

I feel it important to point out that our software was downloaded from the Adobe Licensing site, and is not copied off any CD/DVD media.

My basic process here is:

Download the patch files for Acrobat Pro Extended for Windows, from Adobe:

• AcroProExUpd910_all_incr.msp (no longer easily found on Update site as downloadable at the time of this post)
• AcrobatUpd911_all_incr.msp
• AcrobatUpd912_all_incr.msp
• AcrobatUpd913_all_incr.msp

Of which, based on the article at http://kb2.adobe.com/cps/498/cpsid_49880.html I understand that:

• 9.1.0 is a quarterly update
• 9.1.1 is a security update
• 9.1.2 is a quarterly update
• 9.1.3 is a security update (assumed, as it came out in the wake of current security fixes)

Therefore, I think I need to update my AIP to 9.1.0, then to 9.1.2 (acceptable according to the release notes for this patch) and then to 9.1.3, thus completing my task.

My problem comes from running the patches on the AIP.  Normally I use a customised installation, but to rule that out, I am ONLY using the downloaded software - no local customisations applied using the Adobe Customisation Wizard.

Patching the 9.0.0 version to 9.1.0 using msiexec /a Acro3D.msi /p AcroProExUpd910_all_incr.mspWORKS!  Setup completes, no errors.

Patching the 9.1.0 version to 9.1.2 using msiexec /a Acro3D.msi /p AcrobatUpd912_all_incr.mspFAILS!  Setup reports a missing file in the Data1.cab, interop.adobepdfmakerx.dll.  Google search reveals unlikely sources to download this missing file.

Patching cannot continue, as 9.1.2 is a pre-requisite to 9.1.3.  I have the same problem with applying 9.1.1, though the above KB article made me ignore trying to get that to work.

Does anyone have any advice where I am going wrong?

Thanks!

UPDATE:

After more digging around, it seems that the 9.1.x updates are only for Pro and Standard, whereas the 9.1 update is explicitally for the Pro Extended product.

All 4 patches will patch an "installed" version of the Acrobat Professional Extended product, however the 9.1.2 update will not patch the administrative installation point, presumably because of the different version (Pro or Standard patch, not Pro Extended patch), resulting in the error of the missing file.

The Adobe Security Bulletin clearly says the patches are available for Standard, Professional and Extended, yet the patches dont seem to work!  This is just nuts!

Hello,

    I have to hand it to Adobe - I've never come across and application that sells 2 separate versions, with a cost difference of over $100, that they intentionally made it nearly impossible to distinguish between one another.

We use SCCM, and from what I can tell, Adobe Acrobat DC Pro & Standard both have the same GUID, version number, and display name.  How in the world are we supposed to accurately track our licenses?  We use ServiceNow's Software Asset Management module, integrated with SCCM, to manage software licenses.  It can't tell a difference, and even I as a human, and a 10 year IT Pro, can't either.

Can someone please tell me how I am to accurately manage my Acrobat DC software licenses?

Thank you

Hi Adobe, hope you can help us..

Present setup:

Windows 2012 R2 RDS Server (terminal servers)

Adobe Reader XI 11.0.10

(User profile setup, is based on standard Roaming profiles, with a standard group policy cleaning the local profile up during logoff)

Issue:

The main issue is related to the adobe reader application generates som Z@...TMP files within the users profile folder (local temp), and this files can not be deleted until the terminal server have been rebooted.. (in a terminal server/multi user environment, can the terminal servers not be reboot when users logoff, and when the users logon agin will the generates a new profile folder, eg User1.001, User.002, leaving the old folders in a mess)

Question:

At the present time, have we tried Adobe Workaround1 and Workaround2 http://blogs.adobe.com/dmcmahon/tag/acroct-ini on the present setup, but with no result, (but we can also see this description is addressed to earlier Operation Systems)..

We have also looking into Adobe´s Forum sites, where we can see issues related to the same topic but on older operation systems,

eg (Unable to delete temporary files), but we can not find answers from Adobe related to this questions dates sep14..

Q1:

Could you please help us with a workaround for the above mention windows platform (Windows 2012 R2 RDS with Adobe Reader XI or newer)

Q2:

If the present workaround1 and 2, should be supported on a Windows 2012 R2 platform, can you please help us with a more detailed description for implementing this, (eg. the present workarounds mention C:\Documents and Settings\<user>\Windows that does not exist on a Windows 2012 R2 platform.

We are looking forward to hear from you,

Kind Regards

/Steen Jensen

Hi All,

I have a requirement to package Adobe Acrobat DC 2015.

The source exe extracts MSI. I have created MST for the extracted file and added serial key and all necessary settings to deploy. Upon installation, on first launch it prompts for Signing option. I am unable to disable the screen after applying some registry sittings specified in the below link:

Online features — Acrobat Customization Wizard DC for Windows

It would be of great help, if someone could assist me in achieving the purpose.

Regards,

Avinash L

The following error is produced in Acrobat when trying to click version history documents in SharePoint 2010. "The URL you have provided could not be reached. Please verify that the URL is correct and that the network location is reachable." The revision of the document is reachable, but through typical HTTP via a web browser...but not through the SharePoint <==> Acrobat X Pro COM object magic that works fine for currently checked out documents. Please see inserted image. Thoughts on a fix?

Is there a way to create a Adobe Acrobat Pro DC package in a .msi format, with the license key information already patched? We use Microsoft Windows Server Group Policy ( Software Installation) to deploy all of our software, and it only runs MSI installer package. With our current setup, we are unable to create logon script to run any .bat or .exe file, so running the License file (AdobeSerialzation.exe) post install, is not an option for us. Unless we manually run it on all of our workstations individually, which is what we would like to avoid.

I have tried to use the Adobe Customization Wizard DC to edit the msi file with the "exception" folder, I was able to find the box for "serial number". But I do no have access to a serial number, the only thing I could access, is a pre-created Licensed File, or the Installation package ( for individual install) that patch the software with the License info automatically. But it does not help us with an Enterprise deploy setup.

Please help.

I am not sure if this is the right place to post this, but the "contact us for help" options just kept sending me to the same page over and over again.

I recently jumped through all the hoops attempting to push Adobe Acrobat Pro DC through our SCCM server and have run into several issues.  For one, it will not actually call the Acrobat Pro installation to put it onto the computer.  It does however show that it is "installed" when you log into the cloud on said PC.  Has anyone had issues with this before?

We are running SCCM version 1511.  Thank you very much.

I'm trying to customize a deployment of Acrobat 2017 Standard.

Specifically, I'd like to remove all cloud storage functionality (like the Dropbox integration) for DLP purposes.

I see lots of documentation surrounding the customization of DC deployments but no mention of Acrobat 2017 Standard (or Pro).

Could someone point me to the appropriate downloads and documentation?

Targets for this install will be Windows 10 1703.

Ideally the customized installer would be in a format that can be installed silently.

Thanks!

All members of group need to share a set of custom stamps and signature endorsements (reasons).  I can't identify any way to export/import stamps and other preference/setup settings.  To complicate matters, group are individuals spread thru several companies and some individuals, all with own licenses (typical project includes Engineer (consulting firm), Contractor, Owner (DOT), Inspectors (CEI), and various manufacturers/fabricators.

Is there a way for the designer to EXPORT the custom stamps as file(s) and then the other members of the group to IMPORT the stamps into their copies of Acrobat Pro 9 (or 8)?

I work in a University environment and we'd rather not force everyone who uses one of our Stand-Alone licenses to create an Adobe ID in order to use Acrobat. Is there a way to create an installer that just asks for the Serial Number? I did some reading that you could disable the cloud functions and that would probably be in the same ballpark, but can't find anything about not having to create and ID.  Ideally, we would like for users to just have the same features they had in 11 without creating an Account, without having cloud functions and without having to do too much work on the back end to make that happen (there are only two of us in the office and we don't have a ton of spare time to figure it out).  Thanks