KACE hasn't worked on our Macs in a while...
I haven't been relying on KACE for our school's Macs for several months, but now that the school year is back into full swing, I've turned my attention back to fixing the inventory problems we've had. This situation does appear to bring ability to use KACE for Macs to a complete halt. Where I do see in KACE Inventory that some Macs are still showing connected at times, none have had a successful Inventory in many months. I have a student computer to test with and I've made multiple attempts to get it to report back to KACE, to no avail. I have completely removed the KACE agent folder and all KACE-related LaunchD items, rebooted, and done a complete re-install of the Mac Provisioning package. I've also done some digging into the KACE/data directory and I do see that the inventory.xml file is current and getting fully updated. It seems it's not reporting back to the server, however. When running any flavor of runkbot, the final lines of the output echo "FAILED to get kuid!" and "Failed to build the upload url." I do know that in previous versions there was a file in KACE/data called "kuid.txt" which does not appear now in that directory. I've even attempted to create this file to see if it would change anything, but it has not.
So, if anyone can please guide me in the right direction, I'd love to get these Macs checking back into KACE Inventory.
Thanks!
6 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
atoss
5 years ago
Ok, got to the bottom of it. Apparently, there was a problem with our agent logo. I noticed that the only reference to a download failure when I ran 2 0, was with a client-logo.bmp. So, I uploaded a new logo to the appliance and, voila!, suddenly all Macs are checking in and updating their inventory now. So, there you have it. KACE was 100% broken for all Macs because of a stinkin' logo!
https://kace.url/adminui/kbot_list.php?SHOWALL=1
That will show the hidden scripts that are run when you use the runkbot 4 0, etc. The first number is the script ID (4) and the second number specifies the version (0 means current). - chucksteel 5 years ago
Well, you're looking for errors. Start at the bottom of the log and go back in time. Or, open the log in the Console app and then restart the KACE agent with:
sudo /Library/Application\ Support/Quest/KACE/bin/AMPctl restart
Watch the log to see what happens and look for errors pertaining to reaching the appliance. Run the inventory script and watch the log when that happens. - chucksteel 5 years ago
Things are working... sort of. I'm now able to inventory new devices (or devices I've reinstalled the agent on). However... it looks like only running "runkbot 1 0" has any effect. "runkbot 2 0" doesn't do the inventory. Nor does the "Force Inventory" option on the Device info page.
Per the earlier guidance on this, I've been looking through the hidden scripts. I see that ScriptID 1 is "K1000 Bootstrap," which is the mechanism for new devices. Where ScriptID 2 is "Mac/Linux Cl/Inventory + Agent Update" used for simple inventory updates.
So, I'm glad that bootstrapping works, but it does seem like the other script is the one that should be used for devices already listed in KACE.
Any thoughts? - atoss 5 years ago