I'm having trouble deploying Acrobat Pro X in a K2000 scripted install.

I have a batch file that calls 2 .msi files and 1 .msp (for the most recent update)

set wd=%~dp0

start /wait msiexec.exe /i "%wd%AcrobatProX32-Bit.msi" /qn
start /wait msiexec.exe /i "%wd%AcroPro.msi" EULA_ACCEPT=YES /qb
start /wait msiexec.exe /p "%wd%AcrobatUpd1011.msp" /qn

I used the Adobe Application Manager Enterprise Edition to create an install for just the Acrobat Pro portion of CS6.  This is the silent installer AcrobatProX32-Bit.msi

This installs without problems.

Then I transform the AcroPro.msi file with a .mst file specified in Setup.ini

This is where I run into problems.  The AcroPro.msi will start to install and then hang with 2 seconds remaining in the install. When it hangs, the postinstallation tasks that follow Acrobat start to install and Adobe never gets a chance to finish installing.  This also prevents some of the other tasks from installing correctly.

 

I've tried adding a quick 5 minute wait batch file using:

timeout /t 300 /nobreak

Acrobat just waits for this file to finish and the next task starts.

This batch file installs Acrobat correctly on it's own, it just freaks out in scripted installs for some reason.

In my scripted install, I've got this as the first piece of software that installs.  Everything before that is Windows settings stuff.  The only tasks that install before it are:

Disabling UAC, Enabling Remote Registry, Disabling Guest, IE8 Customizations, .NET 1.1 install, Creating local accounts, Making BIOS changes, Disabling Windows Firewall, and Enabling Remote Desktop.

My next step is creating a script that is just the Acrobat Install and a 5 minute wait after it to see if it still hangs.

 

Any suggestions on how I can get Acrobat to play nice in the K2000?

0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

1

You will have to install all patchs one by one.. you can not install 10.1.1 directly on top of 10.0.0

Answered 03/08/2013 by: jagadeish
Red Belt

  • So what you can do is put all of the updates along with a batch file that runs through and applies each update into one zip file and attach the zip as your postinstall application payload with the command line being the name of the included batch file.
  • The patches aren't the issue.
    The batch file isn't even finishing with the second .msi before I run into problems.
    Part of the way through the install of the second .msi, the postinstall tasks set to run after Acrobat installs are running and preventing the Acrobat task from finishing.
    This is occurring before the file even gets to the .msp install line
  • What is the difference between first and second MSI's?
    • Both MSIs were created by the "Adobe Application Manager Enterprise Edition"
      We have a volume license for CS6, but all most people need from it is Acrobat.
      So I have used the Application Manager to create an installer for just Acrobat from the CS6 install files. That is the AcrobatProX32-Bit.msi.

      The AcroPro.msi is created by the Adobe Application Manager Enterprise Edition as a separate installation with instructions to run it separately from the MSI that the Adobe Application Manager Enterprise Edition creates.
Please log in to comment
Answer this question or Comment on this question for clarity

Share