KACE Product Support Question

K1000 Dependency Dir

09/02/2015 5355 views
I used the $(KACE_DEPENDENCY_DIR) in a script, but it failed because it looked for this path
C:\Program Files (x86)\Dell\KACE\Windows6.1-KB3092627-Win7-x64.msu")

I thought that variable was supposed to look in C:\ProgramData\Dell\KACE\kbots_cache\packages\kbots\xxx.
2 Comments   [ + ] Show comments


  • can you post the script?
    • Sure. It's to launch program wusa.exe with parameters /quiet /norestart $(KACE_DEPENDENCY_DIR)\Windows6.1-KB3092627-Win7-x64.msu
  • What works is running wusa with params /quiet /norestart $(KACE_DATA_DIR)\kbots_cache\packages\kbots\289\Windows6.1-KB3092627-Win7-x64.msu, but that obviously takes more work to set up.

All Answers

Try it this way and see if it works
Answered 09/04/2015 by: SMal.tmcc
Red Belt

  • Isn't the top Directory part of the path to the executable, rather than the dependency path? When I did what you suggested, here's what the task looks like:

    On Success

    Launch “$(KACE_DEPENDENCY_DIR)\C:\Windows\System32\wusa.exe” with params “Windows6.1-KB3092627-Win7-x64.msu”

    Is it doing something different for you?
    • Yes normally but this is a trick you can use. My bad was I forgot the " " around the command should be for file:
      • this starts the process running in the kace dep directory instead of the directory the command resides in. that is why you do not need $(KACE_DEPENDENCY_DIR) in front of the msu.
      • OK, I'll check it out. Thanks.
Just do this:

Answered 09/09/2015 by: axie
White Belt

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


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