$(KACE_DEPENDENCY_DIR) Documentation is Wrong for SMA 7.2
Maybe I'm misunderstanding the documentation, or the way the K1000 does things, but seems to me that the KACE SMA 7.2 Administrator Guide has a pretty serious documentation bug. Here is what it says on page 461:
It says that on Mac OS X, the variable $(KACE_DEPENDENCY_DIR) is /Library/Application Support/Dell/KACE/data/packages/kbots/xxx (ignoring the direction of the slashes for Win/Mac differences).
But such a directory does not exist on my Mac:
Had the documentation been correct, I would not have wasted half a day banging my head against a wall.
It says that on Mac OS X, the variable $(KACE_DEPENDENCY_DIR) is /Library/Application Support/Dell/KACE/data/packages/kbots/xxx (ignoring the direction of the slashes for Win/Mac differences).
But such a directory does not exist on my Mac:
LIB-301-01:data acutech$ pwdSo to figure out where the dependency is going, I added a Verify step to my Task 1:
/Library/Application Support/Dell/KACE/data
LIB-301-01:data acutech$ ls
AMP_CONNECTED kagentbootupscript.log
EXIT_CODE_LIST kagentlogonscript.log
InventoryData.Software kbots_cache
KBOT_LOG.txt kinventory.db
KLocalExecutionState.dat konea-k1000.acu.edu.pem
KONEA_STARTED konea-k1000.acu.local.pem
KSWMeterSvc konea.log
_kagent_bootup_event kpatch.out.lastdeploy
_kagent_logon_event kpatch.out.lastdetect
amp.conf kpatch.stdout
amp1.log kpatch1.log
ampagent-6.3.314.osx.all.dmg ksmeter_sample.txt
ampagent-6.4.180.osx.all.dmg ksmeter_summary.txt
cacert.pem kuid.txt
com.kace.KSWMeterSvc.plist mac_profiles.txt
defaults_loginwindow.bak patches
defaults_loginwindow_root.bak scripts
downloads user
inventory.xml version
k2000_deployment_info.conf
LIB-301-01:data acutech$
Create a message window named “Debug” with title “Debug”, message “The Dependency Directory is $(KACE_DEPENDENCY_DIR)” and timeout “60” secondsWhen I ran the script, the pop-up message window said:
The Dependency Directory is /Library/Applications Support/Dell/KACE/data/kbots_cache/packages/kbots/694And sure enough, when I looked in this location instead of the location specified by the official documentation, I found my dependency.
Had the documentation been correct, I would not have wasted half a day banging my head against a wall.
3 Comments
[ + ] Show comments
Answers (0)
Please log in to answer
Be the first to answer this question
1) The bug in the documentation, as above.
2) I had misspelled "DEPENDENCY" (as "DEPENDECY") in my Verify stage, so when I say in the logs that the launched program referred to "$(KACE_DEPENDECY_DIR)" instead of the actual expanded directory name, I thought, "Well that's stupid, not to expand out to the full name", which forced me to rely on the official documentation, which as mentioned above, is faulty.
So half my bad; half Quest's bad. - kentwest 6 years ago