Install programs and multiple patches with one command line
I’d like to run the install of Reader 10.1.6 with a single command line. This would require specifying the MSI, the MST, the 10.1.5 accumulated patch and the 10.1.6 security patch, and of course a log file. I’ve tried the following command without success:
msiexec /i "AcroRead.msi" TRANSFORMS="AcroRead.mst" /patch "%~dp0AdbeRdrUpd1015.msp;%~dp0AdbeRdrSecUpd1016.msp" /l* "C:\windows\logs\AcroReader 10.1.6 install.log" /qb-
When I execute the command line, I get the MSIEXEC help screen, indicating the syntax is wrong.
If I remove the 10.1.6 patch from the syntax, the command works fine.
I’ve also tried changing “/patch” to “PATCH=” and still suffered the same failure.
I know in the past I would have to specify the exact path of the patch files, even though they sit in the same folder that the MSI & MST sit.
I know I've done this in the past but I think it was about two years ago I'm not sure how I did it (darn my poor documentation skills!) or if the current version of MSIEXEC no longer supports what I want to accomplish.
Answers (6)
The "/patch" switch no longer functions, at least on a Win7 system with MSIEXEC 5.0. We need to use "PATCH=" or "/update".
In reading the documentation, it looks like you have good syntax other than some items being in a different order which usually does not matter. Can you try the below line and see if that produces the same results?
msiexec /i "AcroRead.msi" PATCH="%~dp0AdbeRdrUpd1015.msp;%~dp0AdbeRdrSecUpd1016.msp" TRANSFORMS="AcroRead.mst" /qb- /L* "C:\windows\logs\AcroReader 10.1.6 install.log"
Comments:
-
Where do we put these msi and msp files? - aussupport 9 years ago
-
Where ever you want. They must reside in the same folder, unless you wish to change the command line to point at the different locations. It'd be best to place the files on a local drive as opposed to a network share. - vjaneczko 9 years ago
I've actually just done this one myself yesterday.
Create an Admin Install Point (AIP) of your Reader MSI:
msiexec /a AcroRead.msi - you'll be prompted for a location to create a network share, chose a local directory.
Then patch the AIP with the 10.1.5 patch, followed by the 10.1.6 patch.
msiexec /p AdbeRdrUpd1015.msp /a <path to your AIP>\AcroRead.msi - follow the prompts.
Then same command line as above but referencing the 10.1.6 patch.
The result will be a patched AIP that you can install 10.1.6 from.
I guess that you've used the Adobe Customization Wizard to create you MST, in which case you'll be good to go.
Hope that helps,
Dunnpy
LocationLocation (geography), one of the five geographic themes, and a specific position or point in physical space →
Yeah, I could setup an admin point but I really want to avoid it - i hate wasting space with uncompressed files. Just wish I knew what I did back then!
Comments:
-
The patched AIP is Adobe's documented and prescribed approach to Reader and patches.
The size difference of the patched AIP compared to the extracted MSI (and associated .cab files etc.) from the installer .exe is 2MB.
Whatever you think though, it's your deployment. - dunnpy 11 years ago
I may know what's happening. I've seen instances in the past where Adobe patches are cumulative (meaning, for example, that 10.0.5 contains all the patches in 10.0.1 through 10.0.4). In other cases, they are incremental (meaning that 10.0.5 expects to see 10.0.4, 10.0.3, etc.). If you mix a cumulative patch with the incrementals it contains, it will generate an error at installation time. The best way I've found to determine whether you're looking at an incremental or cumulative patch is to look at the text on Adobe's download page. If it says that it will update 10.0.1 through 10.0.4, then it's probably a cumulative patch. If it says it will update 10.0.4 (and doesn't mention other versions), it's probably incremental. Try removing the oldest patch in your list and running the command again. You may find that you don't need all of them, only one or two, and you'll still get to the same patch level.
I thought that may be the case but the issue that I'm running into is that the help screen of MSIEXEC is popping up, meaning that it's got bad syntax and can't run properly.
My current solution is to run two command lines; first the command line with the 1015 patch file, then follow it with a second command to install the 1016 security patch. So that tells me the two patches are 'correct'.
MP, that works! I must have fat-fingered something along the way or gotten "/update", "PATCH=" and "/patch" confused. I've tried it a few ways and it looks like the "/patch" switch no longer functions, at least on a Win7 system with MSIEXEC 5.0. We need to use "PATCH=" or "/update".
Thanks again.