1 of 1 people found this helpful
A few notes here.
- You cannot apply an MST to an MSP, only to an MSI-based installation; however, you may be able to apply an MSP and MST simultaneously -- I've never built a package to do that though.
- The Reader 10.1.3 MSP can only be used to upgrade Reader 10.1.x systems. To upgrade a Reader v8, v9, or v10.0.x system, you will need to use the EXE-based full installer, available in the Patch Manager catalog.
- Because the Patch Manager package is based on the EXE installer, to build a package from the embedded MSI package, you'll likely have to start from scratch and determine the necessary detection and installed criteria, as well as determine what else might be occurring in the EXE wrapper that you may need to reproduce elsewhere.
As far as your package running successfully (but not installing, apparently) on a 10.1.1 system -- if your package is based on the 10.1.0 base installer, the MSI is probably not executing at all, as the Windows Installer manifest will recognize that product as already updated, and thus the 10.1.0 MSI is NotApplicable to that system.
I believe, to achieve what it seems that your ultimate objective is.. you will need to strip Reader from the machine, install 10.1.0 using the MSI and MST, and then PATCH that 10.1.0 MSI/MST installation to 10.1.3 using the MSP.
There has been some changes to the packages since the original .mst video that is in the support files. That video demonstrates how to use an msi to create your mst and package. The new package files contain an .exe.
I was successful to convert and deploy a package the way your wanting to with a fewsteps outlined below. In this example I am using adobe reader 10.1.2 After some testing it is possible to do this.
The original exe file does need to be extracted via the command as described here:
AdbeRdr1012_en_US.exe -sfx_o"<extraction path>" -sfx_ne
For example if you are wanting to extract to the “C:\adobe_extracted” folder you previously created it would be:
AdbeRdr1012_en_US.exe -sfx_o"C:\adobe_extracted " -sfx_ne
Then after building the mst with the customization wizard pointed at the associated Acroread.msi you can deploy the package.
- You must point the package at the setup.exe from the extraction (not the original) and upload to server.
- You must include all the additional 6 files from the directory where you extracted the exe.
- It should contain ABCPY.INI, AcroRead.msi, adbeRdrUpd1012.msp,Data1.cab,setup.ini, and the created :”yourmstfile.mst”
- The setup.ini file will have all references to the .mst and .msp required for the update
- You do not need a transform rule as the setup.ini contains all the appropriate information.
- The transform deployment was successful on the machine with all requested changes.
Please follow as described here and follow up with any questions. Hope this helps!
Thank you Brendon, that worked perfectly!
I still don't understand why I couldn't use the .MSI installation with the PATCH and TRANSFORM switches like I was trying at first, but I could never get it to work, even though it works fine from the command line. WSUS must do some sort of pre-validation check on the msi that doesn't take the command line patch into account.
This worked great. Using the Adobe Customization Wizard and simply loading all of these files into a PM package was very easy. Thanks for the tip!