Agent not communicating with KACE, konea file log states "Waiting for module.conf to be created".
Answers (2)
I would restart the Quest KACE One Agent service. If that doesn't work, I'd stop the three Quest services, then delete all the directories and files in the Quest directory except the amp.conf. As long as the host is correct. Restart the three services. The amp.conf should repopulate the rest of the content after it connects to the server including all the deleted files.
You are getting that error because the amp.conf file doesn't exist or doesn't have all the needed information. I had the same issue and I noticed that we were installing the kace agent as a standard user and it wasn't creating my amp.conf file at all.
Make sure that the account that you are installing the Kace agent with is a local or domain admin of the computer. Elevated permissions are necessary to write files to the "C:\programdata\quest\kace" folder.
To test I ended up copying the amp.conf settings from one computer that was working opening notepad as admin on the non-working machine pasting the settings in and save as amp.conf (make sure to select all files and not .txt)
then I restarted the Quest KACE One Agent service and in a few minutes the computer was reporting in KACE as expected.
Now I just have to go through and fix my install process.
