KACE Product Support : K1000 Dependency Dir

K1000 Dependency Dir

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? - SMal.tmcc 9 years ago
- Sure. It's to launch program wusa.exe with parameters /quiet /norestart $(KACE_DEPENDENCY_DIR)\Windows6.1-KB3092627-Win7-x64.msu - tpr 9 years ago
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. - tpr 9 years ago

Answers (2)

Posted by: SMal.tmcc 9 years ago

Try it this way and see if it works

Comments:

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? - tpr 9 years ago
- Yes normally but this is a trick you can use. My bad was I forgot the " " around the command should be for file:
  "c:\windows\system32\wusa.exe" - SMal.tmcc 9 years ago
  - 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. - SMal.tmcc 9 years ago
  - OK, I'll check it out. Thanks. - tpr 9 years ago

Posted by: axie 9 years ago

Just do this:

Answer this question

Posted by:

View more:

KACE Product Support Questions

question