I'm not understanding the AMP connection.

I have systems that have been connected and inventoried, but then for some period of time are no longer connected although they are valid clients on the domain. Attempting to force an inventory gives the following error message:

This machine is not currently connected via AMP, and therefore can not be forced to submit inventory.

I'm having problems with about 1 in 10 machines not being able to connect via AMP although I can push the agent to them successfully.

I've looked for documentation on this, especially the doc on Problems with Checking In. Following the directions there haven't helped me resolve the issue.

Can someone explain how this is supposed to work?
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Which version of the agent are you using? My first thought would be to check out the amp.conf file. It should be in c:\program files\dell\kace\. Does it have a host=yourkboxname line in it?

Another thought, is the agent service running?

Casey
Answered 02/17/2012 by: cmccracken
Orange Senior Belt

Please log in to comment
0
I'm running version 5.3.44367 of the agent. The amp.conf file for most systems does show the proper host information. My personal system which was connected 2 hours ago (but is not now) has an amp.conf with only the following information in it: splashtext=Dell KACE Systems Management Appliance is verifying your PC Configuration and managing software updates. Please Wait... However this is the same info it held when it was connected. Some working systems have about a dozen lines with others having only four. The host information in working and non-amp connected systems is the same.

The agent service is running and the ampagent.exe process is running.

My config files are in c:\program data\dell\kace. Executables and .dlls are in the program files folder.

Darrell
Answered 02/17/2012 by: depoteet
Orange Belt

Please log in to comment
0
Hey Darrell,

I had some systems that would lose most of their amp.conf.

You can reset the config with the command line:

amptools.exe -resetconf host=yourhost

I'll recheck my tickets to see if we found any reasons why.

Casey
Answered 02/17/2012 by: cmccracken
Orange Senior Belt

Please log in to comment
0
The same documents you are referring to go through a myriad of tests to narrow down the issue. Without that information I don't even know where to start specifically, but in general:
1) prove the agent has connectivity
2) look in the kbox logs (access and/or kmsgroutput) to see the request
3) license limits and current node count
4) compare it to other similar agents -- reduce as many variables as possible including location (subnet, etc)
6) turn on debugging and look for errors in the client logs
Answered 02/17/2012 by: GillySpy
Seventh Degree Black Belt

Please log in to comment
0
Don't forget DNS.

I've seen agents drop off when DNS stops resolving...
Answered 02/17/2012 by: dchristian
Red Belt

Please log in to comment
0
Casey,

That worked on my system, restoring my amp.conf and subsequently my connection. Thanks for the help. There are a number of other systems with different issues, but with all the help here I'll attempt to work through them this weekend.

Darrell
Answered 02/17/2012 by: depoteet
Orange Belt

  • Could you explain how you restored the amp.conf. "restoring my amp.conf and subsequently my connection"
    Tim
  • Hey Tim,

    In my case I used the amp tools to do it. I ran amptools.exe -resetconf host=yourhost against the system from the command line.

    You can use psexec to run it on remote systems if necessary.

    Casey
Please log in to comment
Answer this question or Comment on this question for clarity