/build/static/layout/Breadcrumb_cap_w.png

K2000: Post Install tasks with "start /wait" command not installing

For some reason, if I attach a MSI file with this command, it doesn't install (nor error out):

start /wait msiexec.exe /i "blah blah.msi" /passive

 

Also, if I zip up everthing and add that command into a batch file, and call the batch file for the post install task, same thing - no install.

I was told that using the start /wait command is best practice - can anyone let me know what I'm doing wrong?


0 Comments   [ + ] Show comments

Answers (1)

Answer Summary:
Wasn't the MSI that was the issue. It was the workaround for files bigger than 1.5GB that was the issue.
Posted by: SMal.tmcc 10 years ago
Red Belt
1

I had to reorder the command and put the msi name last.

Start /wait misexec /qn /i "name of msi.msi"


Comments:
  • hmmm thanks - I will try that. I figured it was the order of switches somewhere. - sfigg 10 years ago
    • That's definitely best practice and I haven't had a problem with it myself but was not using the /passive switch. If reordering works for you please report back if you can :) - mpace 10 years ago
  • hmmm it didn't work. It gives me that stupid Windows MSI screen with the list of all available switches. Here is what I used:

    start /wait msiexec /qb /i "Adobe Master Collection CS6.msi" - sfigg 10 years ago
  • hmmm never mind - not the MSI that's the problem. It's the stupid Adobe CS6. I packaged it according to the tutorial, exported/imported package, and thought I had it setup correctly but it's still showing my small dummy file after it copies to C:\KACE, instead of the 8GB zip contents. - sfigg 10 years ago
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ