/build/static/layout/Breadcrumb_cap_w.png

K1000 Agents are not checking in to Kace Server

Agents status is showing disconnected in the Inventory, but agent machines are up and dell kace service is running fine in the services.

What could be the reasons for Agent machines not checking in to the Kace Box (Last Sync is 5 days)

2 Comments   [ + ] Show comments
  • Check the client config file and make sure the correct Kbox server is set and that the client can reach the server. - Jbr32 10 years ago
  • Client Config file (amp.conf) is fine and service is also running - anonymous_102124 10 years ago

Answers (2)

Posted by: jknox 10 years ago
Red Belt
4
I agree with chucksteel and Jbr32.  The easiest way to set the hostname would be to open an elevated command prompt and navigate to C:\Program Files (x86)\Dell\KACE and run:

amptools.exe host=yourhostname.fqdn.com

That will stop the agent service, make the hostname change, and then restart the service.

That should give the client machine an AMP connection if it is able to reach the K1000.  To force an inventory update, run this from the same location as above:  runkbot 4 0

Past that, follow normal check in troubleshooting: https://www.kace.com/support/resources/kb/solutiondetail?sol=112029
Posted by: chucksteel 10 years ago
Red Belt
1
Check the amp.conf file to make sure that your host is set correctly. The file is located at c:\ProgramData\Dell\KACE. I occasionally find machines where the file is blank for an unknown reason. I also have to kick the service on machines if they have been on for an extended period.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ