1
edit
Changes
Added info about administrative deployments
</source>
== Acrobat 9 as an administrative deployment ==
Some of the .msp files takes a very long time to install. You might want to make an administrative install, and apply the patches to the administrative install instead.
'''Please note:''' Adobe's update regime is that only quarterly updates can be updated with new quarterly updates. If you have made an administrative install, and apply a non-quarterly update, you cannot apply a new quarterly update to it. More info can be found at Adobe: http://kb2.adobe.com/cps/498/cpsid_49880.html
To make an administrative deployment, run msiexec /a path_to_msi.msi TRANSFORMS="path_to_your_language_id.mst" and choose where you want the administrative deployment to reside.
Then you run msiexec /a path_to_administrative_deployment/acropro.msi /p path_to_quarterly_update.mst for each of the quarterly updates. You might want to snapshot this deployment, before applying non-quarterly updates, so you will not have to redo the whole process on a new quarterly update.
You can use Adobe Customization Wizard (ACW) on the administrative install, and make a wpkg package that installs the administrative install, applying the mst made from ACW.
For upgrades, you can run "msiexec /i <path of msi on AIP> REINSTALL=ALL REINSTALLMODE=vomus".
[[Category: Silent Installers]]
[[Category: Adobe software]]