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

Please log in to comment

Answers

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
Third Degree Green Belt

Please log in to comment
2
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

Please log in to comment
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
Senior White Belt

Please log in to comment
Answer this question or Comment on this question for clarity
Nine Simple (but Critical) Tips for Effective Patch Management
This paper reviews nine simple tips that can make patch management simpler, more effective and less expensive.

Share