To troubleshoot the agent there are some basic steps to be taken to gather results and information to be submitted.
Information below must be gathered and the same approach as with a Windows Agent must be followed.
Verify the process is running:
- In Activity Monitor (Launchpad | Applications | Utilities | Activity Monitor), there should be a single process called 'AMPAgent' for the KACE Agent 8.x and bellow or a process called 'konea' for the KACE Agent 9.x and newer running when the agent is idle
- AMPAgent runs as the root user, so all processes will need to be displayed to view it
NOTE: Following command can also be executed:
ps aux | egrep 'AMPAgent|COMMAND' | grep -v grep
Verifying the Agent is listening to the right port:
When netstat -a | grep *.52230 is run, the output should show that the client workstation is listening on port 52230.
Verifying the binary files are in place:
/Library/Application Support/QUEST/KACE/bin
This folder contains the Binaries for agent tasks (Kinventory, Kdeploy, AMPAgent, AMPTools, etc)
Verifying the Agent is registered correctly:
- /Library/LaunchDaemons/com.kace.ampagent.plist contains the path to the working directory and program arguments
Run: defaults read /Library/LaunchDaemons/com.kace.ampagent.plist - /Library/LaunchAgents/com.kace.AdminAlert.plist contains information for the AdminAlert.app, which manages alert pop-ups for the agent. These can be manage installation, script, patch, or messaging alerts.
Run defaults read /Library/LaunchAgents/com.kace.AdminAlert.plist
/Library/StartupItems/AMPAgentBootup contains the information required for the agent to start on boot of the OS
Run defaults read /Library/StartupItems/AMPAgentBootup/StartupParameters.plist
/var/root/Library/Preferences/com.apple.loginwindow LogonHook contains the logon hook that allows execution of tasks before/at the user login
Run defaults read /var/root/Library/Preferences/com.apple.loginwindow LogonHook
Verifying the Agent’s data files:
- /Library/Application Support/QUEST/data contains
- Agent log files (including debugging logs when agent debugging is enabled).
- kuid.txt (contains the agent's KUID).
- Inventory.xml file generated for the agent's inventory.
- Script, patch, and manage installation download directories.
- Review the amp.conf and document the findings in the rest of the files.
- Save the log files from this directory to be submitted when needed.