On our KBox 1000 I've discovered that $(KBOX_DEPENDENCY_DIR) is not expanding correctly. According to http://www.kace.com/support/kb/index.php?action=artikel&cat=5&id=560&artlang=en this should expand to


which $(KACE_INSTALL) should expand to

C:\Program Files\KACE\KBOX

so that my final $(KBOX_DEPENDENCY_DIR) should be

C:\Program Files\KACE\KBOX\packages\kbots\xxx

Instead, I'm getting

C:\Program Files\KACE\KBOX\\packages\kbots\xxx (double backslashes after KBOX).

Anyone else seen behavior like this? As you can imagine, this tends to break scripts (but, believe it or not, only sometimes -- just to add more frustration!)

0 Comments   [ + ] Show Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


You could remove "\" from this statement. $(KACE_INSTALL)packages\kbots\xxx Generally directory property value comes with end slash. Jeeoo Santro
Answered 03/08/2012 by: zipsantro
Purple Belt

Please log in to comment
Yes indeed. I could also use the entire string directly (it's easy enough to figure out what the folder number is for the final bit of the path).

What I'm really asking is if anyone else has seen this (i.e.: Do I have a server configuration issue or is this reproducible for others?) and if there is a way to fix the $(KACE_DEPENDENCY_DIR) so that it works properly.

Thanks for the suggestion, though!
Answered 03/08/2012 by: kngunn
Yellow Belt

  • I can say that I've seen it before, but don't remember what came of it. I probably abandoned whatever I was attempting to do. This might be completely off base, but it might be something with quotes? Regardless, moral of the story is you're not going crazy.
Please log in to comment
Answer this question or Comment on this question for clarity