Some of my Mgd Installs/uninstalls were failing after I upgraded to v6. I have them set to override default installation and don't prepend msiexec and that fails with the cmd line below.
msiexec -i CiscoJabberSetup.exe -qn

BUT!! When I change it to below, it succeeds. Any idea if this is a bug or something I'm doing wrong?
%SystemRoot%\System32\msiexec -i CiscoJabberSetup.exe -qn

NOTE: when I unchecked the don't prepend msiexec box, and left all else the same, it did succeed on one test. But entering the path like above seems the most reliable method.
0 Comments   [ - ] Hide Comments


Please log in to comment

Answer this question or Comment on this question for clarity


I bet the problem lies with 64bit machines.  When you call it the top way, the Kace client is 32bit so it then calls the 32bit msiexec.exe from the windows\syswow64 directory vs the system native 64bit version found at %SystemRoot%\System32
Answered 10/10/2014 by: SMal.tmcc
Red Belt

  • Cool. I'm enjoy v6 so far, sans a few things like this and the incredibly small field for entering the command line.

    I haven't updated to 6.2 yet so maybe it's improved there. No biggie I suppose.

    • this is a problem that is still there, been dealing with it awhile that is why I gave the answer I did, 99 percent sure that was the problem.




      vote here for a 64 bit client

Please log in to comment
It's a rule of mine that ALL files are called with full paths. It sits alongside my other rule, i.e. always assume the worst will happen and code accordingly. My rules make scripts longer, true, but so much more robust.
Answered 10/13/2014 by: VBScab
Red Belt

  • I wrote in Basic and batches in early DOS days so I have a habit of using the full path or .\ path when making calls.
Please log in to comment