KBOX 1100 mamagement agent issues since last Microsoft Updates
We have many end nodes NOT reporting back to the Kace appliance. They show connected but they will not inventory. We thought we had just a few PCs with broken agents but upon further investigation the agent no longer appears to not be able to inventory the PC at it s local level so it never update in kace.
On the "broken" PCs the inventory.xml file under c:\programdata\quest\kace is either missing or it is there but it is empty with 0 bytes.
It appears that maybe after the last security update by Microsoft the agents access rights may have been impacted stopping it from running properly on the PCs.
We have made no changes on any of our PCs and these seem to have started to occur around Oct 13 / Oct 14.
We have been on the most current version and agent level for many months.
We have opened a case with Quest but I think this may be affecting more customers.
All feedback is appreciated.
Mark Johnson
Answers (2)
What version of the SMA?
What version of the Agent?
What version of the device OS?
Any AV software? If so, have you tried to disable or exclude the KACE Agent?
The two main Agent log files to review are C:\ProgramData\Quest\KACE\konea.log and C:\ProgramData\Quest\KACE\user\KAgent.log.
Are there any errors reported in these logs?
Have you opened a support ticket?
If you open a support ticket, please run the KAT (Kace Agent Toolkit) to collect all the Agent logs and submit them with the support ticket.
https://support.quest.com/kb/276850/kace-agent-toolkit-kat-now-available-in-the-sma
Model: K1000
Hardware Model: Virtual (VMware/Hyper-V)
Version: 11.1.263
Agent: 11.1.103
We have opened a ticket. Originally thought it was a few systems realized it is affecting many more. The logs look ok but what we see is the inventory file is not being populated so the last inventory and last reboot are not current.
The agent on suspect PCs show connected to the KBOX and we can run scripts so not all functionality is broken.