KACE Product Support

I'm not sure I understand your question... Are all of your clients having issues with AMP? If so, you need to make sure they can communicate to the KBOX on port 52230. You cannot force an inventory without an AMP connection, because the AMP connection is the "heartbeat" between the client and KBOX - without it, the server cannot tell the client to perform an inventory.

AMP is the heart beat that puts a green light next to machines in inventory, indicating that they are online and connected to the server. It is an outbound connection from the agent to the KBOX on port 52230. If that connection isn't there, then the server isn't able to tell machines to do inventory, run a script, etc. If there is no green light, but the machine is on the network and should see the kbox, check to make sure that firewalls are allowing outbound 52230 from the agent and inbound 52230 to the KBOX.

No not all clients have this issue. It is this one particular machine on which i need to update the inventory. The last time the machine got updated was about 2 hrs back.
I am testing managed Installation and i just installed an application on this test machine. i am waiting for this application to pop up in the software list. In order for the software list to get updated , this machine has to be updated. At this moment it is not connected via amp.
How do I force it to get connected via AMP so that I can force an inventory on this machine. ?

You can't force an AMP connection, it is automatically done by the agent when it is running. Make sure port 52230 is not being blocked somehow... For instance, is this a remote client on a VPN? Does the client have a firewall?

Sethi,

If you look in c:\program files\kace\kbox, there is a file called smmp.log. That is the AMP log. If you look at the end of that file, you should see the latest attempts to connect and we should see some sort of error message. If you post that here, we should be able to help.

Chris...

I think i am all set. The machine in question is now connected to the AMP. The machine needed a couple of restarts to establish the connection.

Here are some of the logs at the time it was not able to connect...

[Mon Dec 14 08:36:11 2009] Header: msgid (116); msgType (0)
[Mon Dec 14 08:36:11 2009] Payload: plugid (6); payloadLen (20)
[Mon Dec 14 08:36:33 2009] Header: msgid (117); msgType (0)
[Mon Dec 14 08:36:33 2009] Payload: plugid (6); payloadLen (20)
[Mon Dec 14 09:35:53 2009] Client socket failed read (9)
[Mon Dec 14 09:35:53 2009] Adding server retry for 08EC65CD-9AA5-4C8E-A659-114DD39C37D6 into queue. Sleeping for 10 seconds
[Mon Dec 14 09:36:13 2009] Error connecting to server: couldn't connect to host
[Mon Dec 14 09:36:13 2009] Adding server retry for 08EC65CD-9AA5-4C8E-A659-114DD39C37D6 into queue. Sleeping for 10 seconds

I believe I'm having the same problem. Here's my SMMP log information. I'm not receiving the inventory for this client. I've opened up the incoming and outgoing ports.

[Wed Jun 02 07:29:03 2010] Shutting down agent daemon
[Wed Jun 02 07:29:11 2010] Closing Net Listener ...
[Wed Jun 02 07:29:43 2010] Config: debug: false
[Wed Jun 02 07:29:43 2010] Config: config: SMMP.conf
[Wed Jun 02 07:29:43 2010] Config: log: SMMP.log
[Wed Jun 02 07:29:43 2010] Config: host: kbox
[Wed Jun 02 07:29:43 2010] Config: port: 52230
[Wed Jun 02 07:29:43 2010] Config: rto: 20
[Wed Jun 02 07:29:43 2010] Config: wto: 20
[Wed Jun 02 07:29:43 2010] Config: crto: 10
[Wed Jun 02 07:29:43 2010] Config: ssl: false
[Wed Jun 02 07:29:43 2010] Config: krash: false
[Wed Jun 02 07:29:43 2010] Config: pl: pluginDesktopAlerts,pluginKbotRunNow,pluginPatching,pluginWeb,pluginRunProcess
[Wed Jun 02 07:29:43 2010] Machine ID: ED5FA73D-179A-4E8E-AE25-93EB84A3B2F2
[Wed Jun 02 07:29:43 2010] Creating Agent Listner...
[Wed Jun 02 07:29:43 2010] Creating scheduler...
[Wed Jun 02 07:29:43 2010] Creating connection...
[Wed Jun 02 07:29:43 2010] Connection established...

Also, here's the log from provisioning.

STEP 1: CONNECT TCP/SSH - SUCCESSFUL

[06/01/10 01:27:25 PM] Executing remote communications:

Initializing RPC
Connecting to ADMIN$
Copying service file
Disconnecting ADMIN$
Connecting to IPC$

STEP 2: AUTHENTICATION - SUCCESSFUL

Creating service
Opening pipe to service
Sending commands
Sending login credentials
[MSGCODE: 000] Begin agent_provision.bat processing.
[MSGCODE: 005] Installing .NET
...[MSGCODE: 011] .NET 1.1 is installed
[MSGCODE: 015] Executing KInstallerSetupSilent.msi
Return code (MSI_ERROR_LEVEL) from MSI execution: [0]
MSI Info: [ERROR_SUCCESS] The action completed successfully.
[MSGCODE: 001] KBOX Agent is installed.
.[MSGCODE: 091] AMP is connected.
[MSGCODE: 093] KUID file detected.
[MSGCODE: 094] kuid: Error: no KUID in registry
[MSGCODE: 100] agent_provision.bat exiting.
exit code: 0Removing service
Connecting to ADMIN$
Deleting service file
Disconnecting ADMIN$

STEP 3: PUSH SCRIPT\PROVISIONING - SUCCESSFUL

End of remote communications.

[06/01/10 01:27:25 PM] End provisioning run.

STEP 4: AMP CONNECTION - WAITING...


STEP 5: CLIENT SYNC - WAITING...