I created a custom msi using the adobe application management tool and I am trying to install it via msiexec (as a test so i can create a batch file to use with my k1000) . It seems like it works but an installer window pops up quickly and then nothing happens.

msiexec /i "\\dfs\abc\directory\subdir\Adobe CS5\Adobe CS5.msi" /passive

Any thoughts?
Thanks
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Community Chosen Answer

2
The AAME generated MSI sets a launch condition that checks UILEVEL. If it ain't silent it won't run.
Make a transform that removes this condition, and you should be able to run it like you want. I've done this on multiple adobe packages without problems.
Answered 03/22/2012 by: Ifan
Second Degree Green Belt

  • Forgot to mention;

    Verify that no MS Office applications or browsers are running when you install the package.
  • Yes that is correct if i manually try to run it the installer tells me it has to run /silent
    However msiexec dosent like /silent only /passive or /quiet.
    Can you tell me how to make a transform to remove this UILevel. Sorry this isnt my forte.

    Thanks,
    advkace
  • === Verbose logging started: 03/22/2012 9:31:11 Build type: SHIP UNICODE 5.00.7601.00 Calling process: C:\Windows\system32\msiexec.exe ===
    MSI (c) (88:D0) [09:31:11:958]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

    MSI (c) (88:D0) [09:31:11:958]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

    MSI (c) (88:4C) [09:31:11:969]: Resetting cached policy values
    MSI (c) (88:4C) [09:31:11:969]: Machine policy value 'Debug' is 0
    MSI (c) (88:4C) [09:31:11:969]: ******* RunEngine:
    ******* Product: \\dfs\adv\Workgroups\ADV Common\Helpdesk\Kace packages\Adobe CS5\Build\Adobe CS5.msi
    ******* Action:
    ******* CommandLine: **********
    MSI (c) (88:4C) [09:31:11:969]: Client-side and UI is none or basic: Running entire install on the server.
    MSI (c) (88:4C) [09:31:11:970]: Grabbed execution mutex.
    MSI (c) (88:4C) [09:31:12:016]: Cloaking enabled.
    MSI (c) (88:4C) [09:31:12:016]: Attempting to enable all disabled privileges before calling Install on Server
    MSI (c) (88:4C) [09:31:12:021]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (4C:78) [09:31:12:035]: Running installation inside multi-package transaction \\dfs\adv\Workgroups\ADV Common\Helpdesk\Kace packages\Adobe CS5\Build\Adobe CS5.msi
    MSI (s) (4C:78) [09:31:12:035]: Grabbed execution mutex.
    MSI (s) (4C:B0) [09:31:12:038]: Resetting cached policy values
    MSI (s) (4C:B0) [09:31:12:038]: Machine policy value 'Debug' is 0
    MSI (s) (4C:B0) [09:31:12:038]: ******* RunEngine:
    ******* Product: \\dfs\adv\Workgroups\ADV Common\Helpdesk\Kace packages\Adobe CS5\Build\Adobe CS5.msi
    ******* Action:
    ******* CommandLine: **********
    MSI (s) (4C:B0) [09:31:12:093]: Note: 1: 2203 2: \\dfs\adv\Workgroups\ADV Common\Helpdesk\Kace packages\Adobe CS5\Build\Adobe CS5.msi 3: -2147286960
    MSI (s) (4C:B0) [09:31:12:093]: MainEngineThread is returning 1620
    MSI (s) (4C:78) [09:31:12:096]: User policy value 'DisableRollback' is 0
    MSI (s) (4C:78) [09:31:12:096]: Machine policy value 'DisableRollback' is 0
    MSI (s) (4C:78) [09:31:12:096]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (4C:78) [09:31:12:096]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (4C:78) [09:31:12:096]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (4C:78) [09:31:12:096]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
    MSI (s) (4C:78) [09:31:12:096]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
    MSI (s) (4C:78) [09:31:12:096]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
    MSI (s) (4C:78) [09:31:12:096]: Restoring environment variables
    MSI (c) (88:4C) [09:31:12:099]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
    MSI (c) (88:4C) [09:31:12:100]: MainEngineThread is returning 1620
    === Verbose logging stopped: 03/22/2012 9:31:12 ===
  • ^^ log file from this morning
    I dont like this line "Client-side and UI is none or basic: Running entire install on the server" I dont think its running the msi on the client machine.
  • The error code 1620 means that the MSI file couldn't be opened. It tries to open this; \\dfs\adv\Workgroups\ADV Common\Helpdesk\Kace packages\Adobe CS5\Build\Adobe CS5.msi

    Check that the path is valid and that the privleges are set correctly.

    Are you trying to run this manually via the command line? What happens if copy the package to your local computer and attempt to install it from there?

    For removing the launchcondition you can open the MSI in Orca, find the launchcondition table and remove the UILevel entry in there. Save the changes as a transform and apply it by running msiexec /i "Adobe CS5.msi" TRANSFORMS="YourMSTName.mst" /qb

    Best practice is to not modify the original MSI.
  • Hello - just an update. I removed that long as heck log file as i have now successfully installed from a local and network location using the x86 adobe package i created (Also made a x64 which was successful too), with the proper transform and the /q switch with logging as suggested. So i am using the path and the cmd line from the network test install that was successful and i want to use a .bat file and upload that to our Kace 1000 appliance. However i am not sure about deploying via a .bat file with the command line info inside it. Researching that now.

    Any input is taken gladly!
  • Sorry, have never used KACE, so i can't help you with that.
    I'd recommend powershell over batch scripts any day though.
Please log in to comment

Answers

0
Have you tried using the alternative quiet modes with MSI other than /passive?
/qb - Display progress bar
/qn - Quiet and No user interaction
/q - Quiet

The other option is to test the install manually first without the /passive, /qn, /qb, etc. This will allow you to ensure your MSI is still functional after the changes you made.
Answered 03/21/2012 by: Trinity
Brown Belt

  • Yes i have. cant get /qb to work but the others do sort of the same thing where the installer pops up and goes away with nothing seems to happen. If i run it manually it tells me i have to run it with /silent not in UI mode.
Please log in to comment
0
Hi advcase

If you navigate to the location and run the MSI from there is it successful? As trinity said I would try that as at least that way you can see if the MSI is working before trying to make the MSI Installation Silent.

If it repeats the same behaviour is anything showing up in the event logs?

Spef
Applications Packaging tips comming to www.spefdata.com
Answered 03/21/2012 by: Spef
Orange Senior Belt

Please log in to comment
0
Enable logging (/l) and check if there are errors stopping the installtion process.

Or just try to run it completly without gui -> /qn. if there is a issue with the dialog.
Answered 03/22/2012 by: RaginX
Orange Belt

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