You might be able to get it to work otherwise, but that was my experience and the source of most of my frustrations.
ADOBE ACROBAT 7.0 4 UPDATE
When I was trying to get the Transform file to automatically run the update msi file, I found that I had to be certain that all spaces were removed from the msi file name so I could put it's name in the "Launch Other Applications" section without ANY SPACES OR QUOTES. Msiexec.exe /i "Acrobat Reader 7.1.msi" TRANSFORMS="Adobe Reader 7.0.mst" /qb Īdd Application or File to Launch using the following settings then click on "Add"ĩ - Test the package using a command line similar the the following.
ADOBE ACROBAT 7.0 4 INSTALL
Start the downloaded EXE file for the 7.0.1 update but do not click on "Next"Ĭopy the 7.0.1 update MSI file from C:\Program Files\Adobe\ to the repository (the final directory name may differ)Ģ - Copy and rename the 7.0.1 update MSI file within the repository to "Update7.0.1.msi"Ĥ - Download and install InstallShield Tuner for Adobe Reader 7.0ĥ - Start Tuner and create a new transform "Adobe Reader 7.0.mst" while selecting the "Adobe Reader 7.0.msi" fileĦ - Make any changes within Tuner as appropriateħ - On the "Launch Additional Applications" Section. (Replace ENU with your language code if appropriate) Start the downloaded EXE file for Acrobat 7.0 but do not click on "Next"Ĭopy all of the files in C:\Program Files\Adobe\Acrobat 7.0\Setup Files\RdrBig\ENU to the repository folder. ġ - Create a repository folder for all of the installations files. To create a combined installation of Acrobat 7.0.0 and 7.0.1. Why couldn't adobe put up a 7.0.1 install msi instead of just a patch?Īfter working on this for a couple days, I found the following to work in our environment where we need to deploy both 7.0.0 and the update at the same time. I don't know if this will work, the update msi has something in the temp dir, is that supposed to stay there or go into the acrobat dir? Edit the 7.0 msi from adobe and insert the files from the update msi into it, thus slipstreaming the update into the original install msi. Will the 7.0 msi ever flip out at some point and reinstall itself thus defeating the update msi?Ĥ. I'm not sure what the repercussions of this are. In another GPO have the update msi, just make sure it applies after the 7.0 msi. Will the 7.0 msi ever flip out at some point and reinstall itself thus defeating the update msi?ģ. In the same GPO insert the update msi as just another msi.
I was hoping it would do the first and then do the upgrade, ugh.Ģ.
ADOBE ACROBAT 7.0 4 PATCH
I tried this, while it patches up existing installs great, new installs just install the patch msi, not the 7.0 main msi.
In the same GPO insert the update msi and put it as an update to the 7.0 msi that is already there.
To me it looks like i have 4 options, i'm just not sure which is the best.ġ. I am still fairly new to the whole GPO/MSI push thing.
0 kommentar(er)
