I'm trying to deploy a piece of software that uses a setup exe and InstallShield command options, and I'm using an alternate download location because there are some large dependencies, cabs, etc. which are too big to upload to the Kace server.  The InstallShield options require double-quotes because some of the paths, names, etc. have spaces.  An example is: /f2"d:\folder name\setup.log".  This program installs silently from a command line with all the recommended switches, but no luck yet with a Kace managed install.  I can see in the kdeploy log that the MD5 hash matches, and the setup.exe file is downloaded from my alternate download location into c:\programdata\dell\kace\downloads\715.  After that, I see the following preceding my list of setup parameters:


folowed by, for example:

/t"(pathname with spaces.. )"

So, I'm wondering if that first double-quote that's passed by the system is then causing the other double-quotes to be read incorrectly.  Is there any documentation on allowable syntax in the "installation command" field?

Any info is appreciated.


0 Comments   [ - ] Hide Comments


Please log in to comment

Answer this question or Comment on this question for clarity




Well, I got that working by running the program from a network share, so please disregard that request.

I've got a different problem, which is that Kace shows a program to be installed, and consequently running an update (managed install) to that software package never even gets queue'd.  Perhaps the fault of the software designer not displaying a difference between versions.  Which leads me to wonder how Kace determines whether a program is up-to-date, and how I might change that info to allow Kace to run the update.

Suggestions are appreciated.


Answered 04/11/2013 by: John365
White Belt

Please log in to comment