/build/static/layout/Breadcrumb_cap_w.png

Scripting Question


KACE SMA v9.0.270 kbots_cache Folder

02/21/2019 486 views

So, I'm trying to run the Dell Command Configure with a script and can't figure out what folder to put the dependencies in.  For example, I originally had the Directory pointing to here: $(KACE_DATA_DIR)\kbots_cache\packages\kbots\cctk, however the log file had error code 267 The directory name is invalid.  Where do I put this file?  I'm trying to run the Dell Command Configure to create a CIR that contains BIOS information. It's almost as if the kagent wants to put it into a directory of it's own like this: C:\ProgramData\Quest\KACE\kbots_cache\packages\kbots\134\cctk

How am I supposed to know what number folder the KAgent is going to create?

1 Comment   [ + ] Show comment

Comments

  • Does $(KACE_DEPENDENCY_DIR) work instead?

All Answers

1

Just to clarify my above comment - here is how I have scripts setup that need to extract files:



Let me know if that helps.


Thanks

Answered 02/21/2019 by: feeldamped
Third Degree Blue Belt

  • Yes that helps. I ended up just installing the Dell Command Configure on the desktop with a managed install. Now I have the CIR created to read the entire BIOS, but how do I scope machines to the CIR?
    • I believe what you need now is to create a label for the machines - I would use a smart label. You can create one using the wizard and look for machines that match the CIR you are looking for.
    • use smart label that machine is dell bios and cir is not null

Don't be a Stranger!

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

Sign up! or login

View more:

Share

 
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