My way is - 
(1). Install Kbox agent 
I use Kbox share folder to install Kbox agent - \\172.16.46.25\client\agent_provisioning\windows_platform. 
(2). Check amp.conf in agent machine 
It only contains one line: host=kbox64. 
(3). Deploy windows debug mode enable script to my Kbox agent 
Admin (Default) view - Scripting - Run Now - Select windows debug log enable script and my Kbox agent, and then click Run Now - Waiting 1~2 mins. 
(4). Check amp.conf in agent machine 
It contains two lines: debug=true and host=kbox64. So I think this script is deployed successfully to my agent. 
(5). Navigate to Scripting - Run Now Status page 
Run Now Status is always Running. If you go to details page, and move your mouse over question mark, then it says status pending. 
So it seems Kbox agent can not send it status to Kbox server. BTW, I also use CMD to check if there is a ping reply from Kbox server to Kbox agent. I find network works properly. 

C:\Users\Administrator>ping kbox64
Pinging kbox64 [172.16.46.25] with 32 bytes of data:
Reply from 172.16.46.25: bytes=32 time<1ms TTL=64
Reply from 172.16.46.25: bytes=32 time=1ms TTL=64
Reply from 172.16.46.25: bytes=32 time<1ms TTL=64
Reply from 172.16.46.25: bytes=32 time<1ms TTL=64
Ping statistics for 172.16.46.25:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms

2 Comments   [ + ] Show Comments

Comments

  • Does the Inventory record show that the machine has an active AMP connection? If not, try a manual check in from the target system: "runkbot 4 0". You may also need to check for firewall rules on the system, your antivirus package, or your network equipment.
  • After i add server in clientäs hosts, then my problem is gone.
    Thanks grayematter.
Please log in to comment

There are no answers at this time

Answers

Answer this question or Comment on this question for clarity

Share