3 machines that will not report into KACE
Ran kbot.exe -s 4 0 reports back bad_mac_ip errors.
We have removed/added (via group policy) multiple times, and have attempted to repair the inventory.xml (https://support.quest.com/kb/129683/bad_mac_ip-provisioned-devices-not-populating-inventory)
And we have followed https://support.quest.com/kace-systems-management-appliance/kb/111253/how-to-remove-duplicate-kuid-s-in-the-kace-sma-client for duplicate kuid's but no luck.
We've removed and re-added the PC's to the domain and tried rebuilding one PC with no change.
Any assistance would be appreciated!
Answers (2)
Top Answer
At first: -s is not nessesary anymore, since the runkbot always runs with the right credentials now.
If you are using Windows 10 1903 on some machines, where the BIOS firmware is reporting unusual, you should check this article:
https://support.quest.com/kb/292130/
Also upgrading (server and agent) to 10.0 would solve this issue, if you really ran into this.
Comments:
-
We ended up upgrading the server and agents to 10 and it resolved the issue. - DoubleA585 5 years ago
I had some issues with devices that wouldn't report/inventory and the only way I could get them to work again was to use the 'Server retrust' button in the KACE Agent Toolkit (KAT) which you can download by going to Settings>Support and it should be the first option under troubleshooting tools. This tool can also kapture logs, force inventory, tell you the current agent version, change the SMA host and tell you what SMA host/IP/Port its currently configured for. Give it a try and let us know if it helped or not
