I am having an issue trying to install Adobe Reader 10.1.0 and use the .msp to 10.1.1 with my kbox 1000. I recieve this error in the event log and the reader never gets installed:

Windows Installer installed the product. Product Name: Adobe Reader X (10.1.0). Product Version: 10.1.0. Product Language: 1033. Manufacturer: Adobe Systems Incorporated. Installation success or error status: 1635.

I am using the KBOX 1000 with a zipped package with the following Full command line:

msiexec /i "AcroRead.msi" PATCH="AdbeRdrUpd1011.msp" TRANSFORMS="AcroRead.mst"

I have tried to Use Default and Configure Manually prepend and don't prepend the msiexec. I have verified the software does get downloaded and unzipped on the client machine. I have also noticed if I take out the PATCH="AdbeRdrUpd1011.msp" it will install Acrobat reader 10.1.0 but I would like to push 10.1.0 to 10.1.1 as part of the initial install not as a second MI.

Now if I goto the machine and put the full path in it installs fine:
msiexec /i "C:\ProgramData\Dell\KACE\downloads\4831\AcroRead.msi" PATCH="C:\ProgramData\Dell\KACE\downloads\4831\AdbeRdrUpd1011.msp" TRANSFORM="C:\ProgramData\Dell\KACE\downloads\4831\AcroRead.mst"

Am I missing something? I have even tried on the MI to use .\AcroRead.msi as an example it still fails. with the 1635 cannot find file.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
I got the same problem, and had to do a second MI :-(

Then I deploy the update to all who has 10.1.0 via Smartlabel and use following.

msiexec.exe /Update "AdbeRdrUpd1011.msp" /qn

If u find any solutions to do all of it in one MI please post it here.
Answered 11/23/2011 by: krippe69
Yellow Belt

Please log in to comment
1
I've seen this before...

Try creating a bat file that has the same command.

For your command line in the MI just call the bat.
Answered 11/28/2011 by: dchristian
Red Belt

Please log in to comment
0
Try running your command line interactively on your client machine without the /qn switch so that you can see any generated error messages.
Answered 12/04/2011 by: drpeaper
Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity