Acrobat deployment with MST and MSP failing
What should the syntax be to deploy Acrobat from the User Console Library as an Install?
The syntax below along with the SET option for the variable succeeds when run as a batch file and double clicking it on a machine. The PATHTOINSTALL is on a network share accessible by all. It's our long standing SDP. But it fails when I run it from the User Console Library. I zipped up the entire install including the MST I created and the 11.0.10 MSP and uploaded the zip as an "Install" to the User Console Library.
When run with the variable path, it opens the msiexec help window.
%PATHTOINSTALL%\Setup.exe /sPB /rs /msi PATCH=%PATHTOINSTALL%\AcrobatUpd11010.msp TRANSFORMS=%PATHTOINSTALL%\AcroPro.mst
When run with the full path typed out, it returns "Error applying transforms. Verify that the specified transform paths are valid.
Kace 6.2
Thanks
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
vjaneczko
9 years ago
If %PATHTOINSTALL% contains any spaces, you'll need quotation marks around the msp, like so:
PATCH="%PATHTOINSTALL%\AcrobatUpd11010.msp"
Interestingly enough, you don't need to specify the path to the transform, just the patch file - even if everything is in the same folder. Frustrating but true.
Comments:
-
Thanks for the reply.
The install works if I call it from a batch file without using Kace so I don't think spaces are an issue. I've got that method working both with and without the variable. Something is failing when Kace deploys it though.
I always remove spaces from paths as a rule. Just easier to not worry about them, but even still I did try with quotes, but still no good when deployed from Kace.
I tried this morning with the syntax below (with and without quotes) and watched the Program Data\Dell\Kace\Downloads\64710 folder as the files were uncompressed. Everthing is there, but it gives this error now.
SYNTAX: msiexec.exe /i acrostan.msi PATCH=AcrobatUpd11010.msp TRANSFORMS=AcroStan-XI-DK.mst /qb
ERROR: This patch package could not be opened. Verify that the patch package exists and that you can access it, or contact the app vendor to verify that this is a valid Windows Installer patch package.
I'm testing various syntax options and will report back when I find one that works. I'm open to suggestions of course. :-) - murbot 9 years ago-
I don't know anything about Kace, but SCCM produces the same problem with attempting to run an install with a MST & an MSP from a task sequence, but it'll work fine if run from the Software Center. What we had to do was to separate the patch from the main install, then define the main MSI as a dependency of the patch. - vjaneczko 9 years ago
-
Yeah. If you mean that I could try first creating an AIP to apply the MSP, and then run a second command to apply the MST to that new AIP, I just tried it a moment ago and get errors every which way but loose. Groan...
I mapped Y: to a network location, even granted SYSTEM full access due to one error. My account has full access to this network location.
I ran:
msiexec /a Y:\AcroStd11.0.10AIP\AcroStan.msi
It runs for a few minutes and creates a Program Files dir and updates some other things, but then stops with "Error 2202.Database Y:\AcroStd11.0.10AIP\AcroStan.msi. Cannot open database file. System error -2147287008
So far, I'm unable to deploy from Kace with any command line that will update the install with the MSP and configure it with the MST. I also can't create an updated admin install with any of Adobe's suggested command lines.
I've tried deploying with msiexec commands and also with the setup.exe /msi switch, but no luck no matter which way. Adobe has also been such a PITA. But I digress. Still searching.... - murbot 9 years ago
Posted by:
EdT
9 years ago
Since you double posted on this topic, in case you did not see the other replies, you don't create an Adobe AIP.
Just use the AAMEE from Adobe - their tool for customising pretty much any of their current packages for enterprise deployment. Once you get this tool, the rest is easy peasy.
Comments:
-
I don't see how related but different questions constitute a double post. One question (this page) regarded syntax when deploying from the User Console Library (and led to a related question about the AIP), and the other inquired about applying future updates after using AIP to deploy. If others want to chime and there's an agreement that I double posted, I'll be glad to accept responsibility and apologize. I'm not being snarky. I just don't see a double post. :-) It was 2 questions about completely different methods to deploy same product. If future readers search for one method or the other, it's easier to read imo. But I'll defer to the majority.
I noted on the other post that I did get the deployment go through so I'm good with the deployment, but I am interested in the AAMEE for future use, but get the message "a valid installer could not be found". I tried moving the install files to a local folder on the C: drive as well as the destination folder, and searched online for other solutions but still get the error. There's gotta be some simple step I'm missing or doing wrong.
Any ideas how to resolve this error?
Locate the Product Installation Folder: C:\INSTALLS\AdobeAcrobatXI
Package Name: AcroStanAAMEE1
Save To: C:\INSTALLS\AdobeAcrobatXIStdAAMEE - murbot 9 years ago
