/build/static/layout/Breadcrumb_cap_w.png

Kace's uninstall cmd lines fail

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   [ + ] Show comments

Answers (2)

Posted by: SMal.tmcc 10 years ago
Red Belt
0
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
%SystemRoot%\System32

Comments:
  • 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.

    Thanks! - murbot 10 years ago
    • 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.

      http://www.itninja.com/question/bitlocker-script

      http://www.itninja.com/question/xcopy-not-working-in-kace-script-works-in-command-prompt

      http://www.itninja.com/question/custom-inventory-rule-problems

      vote here for a 64 bit client

      http://kace.uservoice.com/forums/82699-k1000/suggestions/2200437-create-a-native-64bit-windows-client- - SMal.tmcc 10 years ago
Posted by: anonymous_9363 10 years ago
Red Belt
0
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.

Comments:
  • 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. - SMal.tmcc 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