We have a bunch of machines that are now checking in and being inventoried, but then show that they have no amp connection. We recently upgraded to K1000 5.5. I've run all the patches available. Some of these machines have the new agent and some have 5.4 agent. We manage over 7000 machines. So, I know there could be a lot of variables, but it's unusual for the inventory to be so recent and the AMP connection to be broken.

3 Comments   [ + ] Show Comments


  • Have the machines been rebooted? We had some that didn't check in until reboot.
  • You have all the required ports open on the Firewall right?
  • I assume so since other machines are working. What ports does the agent or ampagent use?
Please log in to comment



AMP Connections can be broken if those machines are not UP when you checked it. Is it possible that those machines are turned off when you checked their AMP connection?

Answered 09/23/2013 by: AbhayR
Fourth Degree Black Belt

  • This happens with computers sitting right next to us when we're testing. It's also happening on lots of computers which indicates that it's not a matter of these computers being turned off, because these schools are using these computers every day.
  • What does the amp.conf look like on one of the broken systems? I had an issue a couple versions back where the amp.conf would destroy itself and leave the machine stranded. I can't think of anything special I did to fix it, but it should at least give us a starting point.
  • Can you paste the logs from amp.log file ?
  • Where are those logs? On the machine not checking in or in K1000? I know the conf file is on the machine not checking in. I will have to ask one of our technicians if they can find one and bring me the conf file.
  • For XP: c:\Documents and Settings\All users\Dell\KACE
    For Win Vista and above : c:\Programdata\Dell\Kace
  • We also have this problem which is an approved bug by dell. we have to disable all provisioned configurations and deployments of kace agents and the amp connection are ok.

    But this bug will not fixed before next release 6.0 somewhere in march 2014.
Please log in to comment
Answer this question or Comment on this question for clarity