Hi

My company has currently set new UAC security settings but we have an issue where we are not able to update Adobe products because UAC stops it, UAC also does not prompt for elevation it just out right blocks updates.

We really need a way to either allow the updater to run/install past the UAC restrictions OR find a way to distribute adobe updates via WSUS if it's possible

Thanks

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!

The uninstallation of Adobe Acrobat Pro 2017 (msiexec.exe / x {AC76BA86-1033-FFFF-7760-0E1108756300} / l * v "C: \ Windows \ Logs \ Adobe Acrobat Pro 17-Uninstall.log" / qn) interrupted with the graphical error message "Installation error".

In the "Adobe Acrobat Pro 17-Uninstall.log" is the last action:
MSI (s) (C8: 60) [12: 27: 36: 323]: Invoking remote custom action. DLL: C: \ Windows \ Installer \ MSI53CE.tmp, Entrypoint: RemoveDrvFileAndContMenuReg
PrintInf logging :: szCmdLn64: "C: \ Program Files (x86) \ Adobe \ Acrobat 2017 \ Acrobat \ Xtras \ AdobePDF \ PrintINF64.exe" "Uninstall" "C: \ Program Files (x86) \ Adobe \ Acrobat 2017 \ Acrobat \ Xtras \ AdobePDF \ AdobePDF.inf "
PrintInf logging :: szCmdLn: Uninstall 128 C: \ Program Files (x86) \ Adobe \ Acrobat 2017 \ Acrobat \ Xtras \ AdobePDF \ AdobePDF.inf

After clicking "OK" the deinstallation completed.

The transform used for installation was created in the Adobe Wizard 2015 DC (1502020039).

Morning,

We require the full installation including updates for Adobe Reader 9.5 to distribute to all users in our company.  I have installed Adobe reader 9.5.0 on my PC then all the updates available however If possible can you please send me an install that ncludes these updates so i only have one setup to run.

many thanks Amanda

I've been banging my head on this problem for a few days now, and can't seem to find a resolution.  I'm moderately familiar with packaging and scripting installs, so there is a possibility my issue lies with my understanding of patching MSI files with MSP's.

I'm trying to create a custom installation of Acrobat Reader DC 2017 using the Acrobat Customization Wizard DC.  The downloads I'm starting off with are:

AcroRdrDC1701220093_en_US.exe
Which contains:

     abcpy.ini

     AcroRdrDCUpd1701220093.msp

     AcroRead.msi

     Data1.cab

     list.txt

     setup.exe

     setup.ini

CustWiz1502020039_en_US_DC.exe

Step 1:  Extract files from AcroRdrDC1701220093_en_US.exe using 7zip to a folder called Reader

Step 2:  Install Acrobat Customization Wizard DC

Step 3:  Launch ACW, load AcroRead.msi from Reader folder

Step 4:  Modify the settings, including a few custom HKLM and HKCU registry keys I got from here:

                    Services integration

Step 5:  Save transform file as "AcroRead.mst" to the Reader folder

Step 6:  From a virtual machine, run the installation files like this:

                    msiexec -i AcroRead.msi TRANSFORMS=AcroRead.mst /quiet

Step 7:  Launch Acrobat Reader DC

What I found was some of the settings in the ACW did not propagate to the installation .  Mostly, none of the custom HKCU settings replicated to the user's registry.  I found a bug report with Acrobat Reader DC 2015 where the registry keys weren't migrating over properly at launch of Reader

                    [Acrobat Reader DC] HKCU registry keys are not replicated for each user as for Adobe Reader

Supposedly a fix was released in the 2017 branch of Reader.

What I discovered above is that in step 2, I was creating a transform file using the 2015 version of Acrobat Reader DC, but using the 2017 version of the ACW.  This might have been where some of my problems were coming from, so my next goal was to patch the MSI using the AcroRdrDCUpd1701220093.msp, and then re-create the transform file from scratch.  This is where I'm getting a little lost.

I read that an 'Administrative Installation' needs to be created, and then patched.  So I ran the command msiexec /a acroread.msi /p AcroRdrDCUpd1701220093.msp and then installed to a different folder called "Administrative Installations\Adobe Reader DC".  I then ran msiexec -i acroread.msi TRANSFORMS=acroread.mst /quiet from the original READER folder (because the MSI seems to have been updated) and I get all sorts of missing files errors.

All I'm trying to do is configure a transform file from the latest version of Acrobat Reader DC (2017) and then install the package, including the transform, to a virtual workstation for testing.  Can someone point out what I'm doing wrong?  Tnx.

Hi there,

I would like to upgrade old acro DC version to 1501020056.

So i download exe on ftp, i extract exe with winrar, i extract program with msiexec /a AcroRead.msi

I have AcroRead.msi in my extract folder with all folders. Now if i launch msiexec /a AcroRead.msi /p AcroRdrDCUpd1501020056.msp or with the acro.msi in the extracted folders, i got the legendary : The upgrade patch cannont be installed by windows blablabla.

So what's the problem this time ? I use msi and msp they havent been extracted............... Same thing with msp from ftp......

Anybody have a solution ??

Thanks a lot

Hi,

we used the Adobe - Acrobat : For Windows : Acrobat Customization Wizard DC (incl. license key) to create a MST file.

Then we installed Acrobat 2017 on a "Windows10 Master" and deployed this to 100 virtual machines.

Then If I start Acrobat 2017 on a thin client I receive 2 dialogs:

- missing registration

- missing default PDF standard environment

Are there any experiences out there with the combination of Acrobat 2017 and VDI?

We have an Internal Adobe update server configured for Create Cloud applications.  We've now purchased an enterprise license for Adobe Acrobat Pro DC, and would like to configure to auto update via our server.

Hi there,

I would like to upgrade old acro DC version to 1501020056.

So i download exe on ftp, i extract exe with winrar, i extract program with msiexec /a AcroRead.msi

I have AcroRead.msi in my extract folder with all folders. Now if i launch msiexec /a AcroRead.msi /p AcroRdrDCUpd1501020056.msp or with the acro.msi in the extracted folders, i got the legendary : The upgrade patch cannont be installed by windows blablabla.

So what's the problem this time ? I use msi and msp they havent been extracted............... Same thing with msp from ftp......

Anybody have a solution ??

Thanks a lot

Sehr geehrter Supporter!

Bei der Installation des „Acrobat Pro DC“ habe ich bemerkt, dass die „Adobe Creative Cloud“ auch mit geliefert ist:

Fragen:

1. 1. Müssen wir unbedingt Adobe Creative Cloud mit verteilen?

Hat diese Komponent eine bestimmte Funktion bei der Verwendung von Acrobat Pro?

Kann  man einen Package nur „Adobe Acrobat Pro DC“ ohne „Adobe Creative Cloud“ herunterladen? Oder gibt es die Möglichkeit bei der Verteilung die Adobe Cloud mit Commandline/switch abzuschalten?

Wir haben bei der andere Adobe Produkte „Adobe Creative Cloud“ auch mitgeliefert. Kann es der Falls sein, dass zwischen unterschiedlichen Creative Cloud Versionen einen Konflikt besteht?

1. 2. In „Verzeichnis „…\Setup\APRO15.0\Adobe Acrobat“ sind die Updaten von
   1. a.    Acrobat X (AcrobatUpd10116.msp ~ 108 MB)) und
   2. b.    Acrobat XI (AcrobatUpd11012.msp~ 236 MB) vorhanden.

Brauchen wir die beiden mit zu installieren? Kann ich sie von package löschen?

1. 3. In „AcrobatPro_20170703\Setup\APRO15.0\Adobe Acrobat“  sind
   1. a.    WindowsInstaller-KB893803-v2-x86 (Windows Installer 3.1 Redistributable (v2), und
   2. b.    vc_runtimeMinimum_x64.msi  (Visual C++ 2015 Redistributable ...) vorhanden

Haben sie bestimmte Funktionen?

Sollen wir mit installieren ?

1. 4. im Adobe-Server steht 2 neuen Updaten:

AcrobatDCUpd1502320056.msp, und

AcrobatDCUpd1502320070.msp

Die sind nicht in Package „AcrobatPro_20170703“ vorhanden?

Können Sie bitte die Fragen abklären!

Danke für die Unterstützungen

I am trying to customize Adobe Reader DC to remove any other versions of Acrobat found on the machine. The option is grayed out. How do I select this option or make this operation happen?

Thanks,

We are using Acrobat Pro DC on several computers in our company (both Windows 7 and 10).  We also use FileMaker (versions 14 and 15) which has container fields that we place pdf files into.  FileMaker displays the pdfs in the container fields using a combination of Internet Explorer and the default pdf viewer (Acrobat in our case).  Last week after the Windows and Adobe updates we started getting this error:

"There is a problem with Adobe Acrobat/Reader.  If it is running please exit and try again (9:9)."

and FileMaker crashes after hitting OK in the error message box. 

I fixed a Windows 7 PC by disabling the Adobe Reader add-on in Internet Explorer.  However, the Adobe Reader add-on does not show up in any of the Add-on lists when I go to Manage Add-Ons in Internet Explorer 11 on a Windows 10 PC.  I uninstalled Acrobat, ran a registry cleaner, then reinstalled an older version of Acrobat DC and the pdfs in container fields show up in FileMaker until Acrobat updates and the error message comes back.

I contacted FileMaker tech support and they said it sounded like an Adobe issue, so they weren't much help.

Has anyone else had this FileMaker / Adobe issue?  It sounds similar to the problems described in another thread https://forums.adobe.com/thread/2221850

OK. First off, as a sys admin i'm VERY annoyed w/Adobe these days.  Acrobat DC deployment in our new Windows 10 images has been a complete and utter nightmare with the way adobe tries to do licensing but yet has a full guide on licensing? WTF???  ok, rant aside here is the issue I have had now since day 1 of trying to embed my Acrobat DC Standard (classic, aka 2015) into our windows 10 imaging.

I have created a customized msp file using the Acrobat Customization Wizard.  In it, i have used our CCE serial number and enabled Offline Exception.

I then install said package in my windows 10 images with my default admin user who's profile is then used for all new profiles.  After making all of my changes to the images, i then will sysprep my image and then capture it in .wim form and then deploy via Windows Deployment Services and Server 2012 R2. 

Once the image is deployed, we notice after about a few logins or so; acrobat will ask the user to Sign In and at that point is useless since you can't do anything until you sign in.  This should not be breaking since i've enabled offline exception in the msp that we used in the install. i installed acrobat via the setup.exe and /sALL flags.

However, if I deploy my image and have acrobat dc installed via one of my firstlogon unattend commands; the licensing survives.  WHY IS SYSPREP BREAKING LICENSING?

WHY DOES ADOBE MAKE LICENSING SO DANG HARD for us??? 

I've been banging my head on this problem for a few days now, and can't seem to find a resolution.  I'm moderately familiar with packaging and scripting installs, so there is a possibility my issue lies with my understanding of patching MSI files with MSP's.

I'm trying to create a custom installation of Acrobat Reader DC 2017 using the Acrobat Customization Wizard DC.  The downloads I'm starting off with are:

AcroRdrDC1701220093_en_US.exe
Which contains:

     abcpy.ini

     AcroRdrDCUpd1701220093.msp

     AcroRead.msi

     Data1.cab

     list.txt

     setup.exe

     setup.ini

CustWiz1502020039_en_US_DC.exe

Step 1:  Extract files from AcroRdrDC1701220093_en_US.exe using 7zip to a folder called Reader

Step 2:  Install Acrobat Customization Wizard DC

Step 3:  Launch ACW, load AcroRead.msi from Reader folder

Step 4:  Modify the settings, including a few custom HKLM and HKCU registry keys I got from here:

                    Services integration

Step 5:  Save transform file as "AcroRead.mst" to the Reader folder

Step 6:  From a virtual machine, run the installation files like this:

                    msiexec -i AcroRead.msi TRANSFORMS=AcroRead.mst /quiet

Step 7:  Launch Acrobat Reader DC

What I found was some of the settings in the ACW did not propagate to the installation .  Mostly, none of the custom HKCU settings replicated to the user's registry.  I found a bug report with Acrobat Reader DC 2015 where the registry keys weren't migrating over properly at launch of Reader

                    [Acrobat Reader DC] HKCU registry keys are not replicated for each user as for Adobe Reader

Supposedly a fix was released in the 2017 branch of Reader.

What I discovered above is that in step 2, I was creating a transform file using the 2015 version of Acrobat Reader DC, but using the 2017 version of the ACW.  This might have been where some of my problems were coming from, so my next goal was to patch the MSI using the AcroRdrDCUpd1701220093.msp, and then re-create the transform file from scratch.  This is where I'm getting a little lost.

I read that an 'Administrative Installation' needs to be created, and then patched.  So I ran the command msiexec /a acroread.msi /p AcroRdrDCUpd1701220093.msp and then installed to a different folder called "Administrative Installations\Adobe Reader DC".  I then ran msiexec -i acroread.msi TRANSFORMS=acroread.mst /quiet from the original READER folder (because the MSI seems to have been updated) and I get all sorts of missing files errors.

All I'm trying to do is configure a transform file from the latest version of Acrobat Reader DC (2017) and then install the package, including the transform, to a virtual workstation for testing.  Can someone point out what I'm doing wrong?  Tnx.

Hi there,

I would like to upgrade old acro DC version to 1501020056.

So i download exe on ftp, i extract exe with winrar, i extract program with msiexec /a AcroRead.msi

I have AcroRead.msi in my extract folder with all folders. Now if i launch msiexec /a AcroRead.msi /p AcroRdrDCUpd1501020056.msp or with the acro.msi in the extracted folders, i got the legendary : The upgrade patch cannont be installed by windows blablabla.

So what's the problem this time ? I use msi and msp they havent been extracted............... Same thing with msp from ftp......

Anybody have a solution ??

Thanks a lot

I am just rolling out Acrobat Pro DC. I had installed it on our 2008R2 Terminal Server but it kept asking users to Sign-in every two days. I spoke with Acrobat Support and we created a Custom installation using the Wizard however this won't install on Terminal Server. I keep getting Error:28000

Is there something new about installing on Terminal Servers?

Sehr geehrter Supporter!

Bei der Installation des „Acrobat Pro DC“ habe ich bemerkt, dass die „Adobe Creative Cloud“ auch mit geliefert ist:

Fragen:

1. 1. Müssen wir unbedingt Adobe Creative Cloud mit verteilen?

Hat diese Komponent eine bestimmte Funktion bei der Verwendung von Acrobat Pro?

Kann  man einen Package nur „Adobe Acrobat Pro DC“ ohne „Adobe Creative Cloud“ herunterladen? Oder gibt es die Möglichkeit bei der Verteilung die Adobe Cloud mit Commandline/switch abzuschalten?

Wir haben bei der andere Adobe Produkte „Adobe Creative Cloud“ auch mitgeliefert. Kann es der Falls sein, dass zwischen unterschiedlichen Creative Cloud Versionen einen Konflikt besteht?

1. 2. In „Verzeichnis „…\Setup\APRO15.0\Adobe Acrobat“ sind die Updaten von
   1. a.    Acrobat X (AcrobatUpd10116.msp ~ 108 MB)) und
   2. b.    Acrobat XI (AcrobatUpd11012.msp~ 236 MB) vorhanden.

Brauchen wir die beiden mit zu installieren? Kann ich sie von package löschen?

1. 3. In „AcrobatPro_20170703\Setup\APRO15.0\Adobe Acrobat“  sind
   1. a.    WindowsInstaller-KB893803-v2-x86 (Windows Installer 3.1 Redistributable (v2), und
   2. b.    vc_runtimeMinimum_x64.msi  (Visual C++ 2015 Redistributable ...) vorhanden

Haben sie bestimmte Funktionen?

Sollen wir mit installieren ?

1. 4. im Adobe-Server steht 2 neuen Updaten:

AcrobatDCUpd1502320056.msp, und

AcrobatDCUpd1502320070.msp

Die sind nicht in Package „AcrobatPro_20170703“ vorhanden?

Können Sie bitte die Fragen abklären!

Danke für die Unterstützungen

Hi,

we used the Adobe - Acrobat : For Windows : Acrobat Customization Wizard DC (incl. license key) to create a MST file.

Then we installed Acrobat 2017 on a "Windows10 Master" and deployed this to 100 virtual machines.

Then If I start Acrobat 2017 on a thin client I receive 2 dialogs:

- missing registration

- missing default PDF standard environment

Are there any experiences out there with the combination of Acrobat 2017 and VDI?

We're looking to upgrade from Reader 9.x to Reader XI.  A bunch of us in IT have been running Reader X without issue for some time so we didn't anticipate any problems with XI. I tested the upgrade process on a machine with 9.x and although it worked fine, none of our add-ins worked.  I performed the following on a machine with XI with no positive results:

• Performed repair or 'modify' installations of the applications in question that load add-ins/plug-ins into Adobe
• I verified the .API files were in in the proper location
  • One plugin (caseMap) goes into reader\plug_ins
  • Another plugin (Interwoven) goes into reader\plug_ins\Interwoven
• Verified protected mode was disabled via registry
  • reg add "HKEY_USERS\DefUser\Software\Adobe\Acrobat Reader\11.0\Privileged" /v bProtectedMode /t reg_dword /d 0 /f

Again: Going from 9.x to X we don't have a problem, and usually adding the .API file is all that's necessary to get the plug-in working again.  But when going from 9.x to XI or X to XI, the plug-ins no longer work.

Has something drastically changed between X and XI that would make these add-ins cease to function?

I've reached out to the vendors & am awaiting responses.  In the mean time, is there anything I failed to check or something else I can do?

My Enterprise PC does not allow regular user to have write access to C:\ProgramData folder. I ran ProcMon and found that the error is due to an ACCESS_DENIED to CreateFile(). The process is requesting write access to a temp file in C:\ProgramData\Adobe\SLStore. Can Adobe patch the program to work with only READ access to C:\ProgramData? Or change the write access path to some folders in C:\Users\%USERNAME%\AppData?