Fixing broken KACE agents
Answers (4)
Comments:
-
Thanks Jon. What would you do though if the agent wasn't running, or connecting to the K1000 at all? We have a lot of devices (internal and external) that don't even have the AMP agent linking to the KACE server. It is pretty much like the AMP.CONF is cleared out or has no data at all. We currently use Kaspersky to push agent replacements on broken machines, but we will be dropping them soon. - zgillette 6 years ago
-
I'm assuming you've verified that network or host-based firewalls aren't blocking agent-traffic. I'd try completely uninstalling including removing any left-over files and directories. (I don't have the commands, but I think you can find them in the links above.) After that then you can re-push the agent. We use Windows Group Policy for this purpose, but you could use PSExec or Kaspersky. - Jon_at_GLS 6 years ago
-
Jon, I tried your script and it worked for about 3 months but there was some kind of update that messed it up. What changes do I need to do that to that batch file to get it to work? - kgarwood 7 months ago
Almost every time I had an issue with an agent it was due to a missing or broken AMP.CONF file. I ended up writing a script to check that the
host=xxxxx.xxxx.xxx
line in the AMP.CONF was correct and if not, replace the file with a correct one, then run the "RUNKBOT.exe 4 0" command. I added this to a GPO and had it as a computer startup script.
This was back in 5.x and 6.x
IDK about any deployment tool but I think this worked for manually forcing the agent to communicate with some of ours...........
first ping both ways from theserver to the KACE SMA and from KACE SMA to the Server. You can go to SETTINGS> SUPPORT > “Run diagnostic utilities” to ping from the appliance.
On the server in a CMD window,go to: C:\Program Files (x86)\Quest\KACE
Run“amptools.exe get” and see if the KACE SMA server shows up
Regardless, run “amptools.exehost=KACESERVERNAME” to force the agent to report to the host.
