/build/static/layout/Breadcrumb_cap_w.png
11/30/2017 1476 views
Hello ALL,

I trying to deploy Acrobat Pro DC with updates in Distribution but seems i'm having trouble.   I'm using

start /wait msiexec.exe /i AcroPro.msi PATCH=Acrobat2017Upd1701130068.msp TRANSFORMS=AcroPro.mst /quiet.   If I remove the update patch PATCH=Acrobat2017Upd1701130068.msp it will run fine.  I'm running everything in a zip file with the patch on the root.

 

0 Comments   [ + ] Show comments

Comments



Community Chosen Answer

2
And the error is...? What is in the installation log file ( /L*v )? Does the patch installation (even manual one) work after main product's installation with transform?
Answered 12/01/2017 by: rad33k
Second Degree Brown Belt

All Answers

1
One, always, always, ALWAYS use explicit paths for this stuff and two, only a fool would run any installation without creating a log:
start /wait msiexec.exe /i "%~dp0AcroPro.msi" PATCH="%~dp0Acrobat2017Upd1701130068.msp" TRANSFORMS="%~dp0AcroPro.mst" /quiet /l*v %temp%\AcroPro[version_number].log
Also, personally, I create Administrative Installation Points for major apps like this. When a patch is released, I copy the existing AIP to a new AIP, patch the new AIP, then deploy the patched release. That gives me a quick and easy to regress any "bad" updates (of which there have been many over the years, let me tell you!)
Answered 12/01/2017 by: VBScab
Red Belt

0
Thank You both.   I was able to get this working by slitting it and putting start /wait msiexec.exe /p Acrobat2017Upd1701130068.msp /quiet /norestart. 
Answered 12/01/2017 by: scrocafella
Yellow Belt

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share