This document is for Agents on Windows.
This document describes and approach to determining what is wrong with an agent that is not able to check-in. Apart from the steps in this document there may still be issues with the agent that are preventing it from checking-in. However, this approach will also help to rule out the common symptoms and issues surrounding check-in.
In 5.3 an agent establishes a connection with the server based on the host name and port number that you have specified in the network settings of your K1000. If you have installed the agent from the kbox (i.e. using either the auto-Agent update from a previous version or Agent Provisioning) then these settings will be inherited from your k1000 network settings.
You should first check the network settings on your box. They should look like this document "Setting your KBOX Web Server Name"
You can determine if the agent cannot connect with the following tests:
If after looking at that information you suspect that the agent cannot connect then you should check the following:
Note: If anything needs correcting in the amp.conf file then I would just reinstall: uninstall, delete the amp.conf file, reinstall.
It is not the default but if you are now using SSL....
If you cannot get to the secure website of your kbox using the host value shown in amp.conf without a security exception then neither can the agent. Make sure that you have not made any exemptions in the browser -- these exemptions will not be allowed by the agent.
The agent will try https first even if it is configured for http on port 80. If it cannot find an answer on https (443) then it will try http (80). If it gets an error on 443 then it will not try 80. Make sure that no proxy server, etc is responding on 443.
Task priority on the K1000 (ie K1000 is busy doing other things)
On the server side:
When an Agent wants to do something it establishes what is called an AMP connection with the kbox (or uses it's already established connection) on port 52230. An agent that is already connected to the server will show a green light icon beside the machine name in inventory. If you open the detail record for this machine then it will tell you the time that is has been "connected since". Note: this is different then the last time that it checked in/last sync.
An agent that wants to do an inventory will establish an AMP connection and then ask the k1000 to do an inventory. Depending on how busy the K1000 is it may nor may not be able to process that inventory right away. If you know the machine name of the PC that is trying to connect then you can do the following:
If you do not see the machine then:
If this PC has a new install/re-install of the agent then this may not work. Instead you will need to search for the "bootstrap" request of the agent. To search for the bootstrap request do the same as above except the machine name will be [Text Missing]. If you do not see that in the "in progess" list then you can use the drop-down list and choose tasks of type "bootstrap". If you still do not see it then there is a different problem.
If the individual tasks on the other machines take a long time to complete then you may have some other issues with your K1000 / agents. Please call technical support.
On the agent side:
On the agent side you can try to force a bootstrap by going to the binaries directory and running runkbot 4 0. While this runs you should see kinventory.exe run for part of the time. At the end of it you should have a machine in inventory and the kbots 4,5,6 in c:\users\all users\dell\kace\kbots_cache and perhaps other kbots.
If you have come to this point and are still unable to connect then you should try to restart the services on the agent PC, reboot the PC and reboot your kbox (if possible).
If that is unsuccessful then at this point you should call technical support. You should have documented evidence of following the troubleshooting steps above including the debug logs from the PC. Also be prepared for support to want to tether your box (see https://support.software.dell.com/kb/112032 )
K1000 Systems Management Appliance
6.3, 6.2.109330, 6.2.109329, 6.0.101865, 6.0.101864, 6.0.101863, 5.5.x, 5.5.90545, 5.4.76848, 5.4.76847, 5.4.70402, 5.3.53053
Best Practices, Best Practices
Histórico do artigo:
Criado em: 9/2/2013
Última atualização em: 5/26/2015