How do people typically handle a server (in this case, a web server) which may have multiple IP addresses on one network adapter?  Right now, I am able to provision this box using the primary IP/DNS for it but how do you handle the rest of the IPs? Should they be agentless? Then have a relationship setup to the primary IP?
0 Comments   [ + ] Show Comments


Please log in to comment



KACE doesn't track devices specifically by IP address. When the agent is installed, it generates a KUID (KACE GUID) that is essentially attached to the OS install. It uses MAC addres, serial number, etc to attempt to check for duplicate devices, and will typically re-use an existing KUID if it detects those things in its inventory.

That being said, you should only need to provision the server once. After it has collected inventory, it should then be aware of all the IPs associated to the physical (or virtual) adapters installed on the device. It may only show the primary IP on the inventory list, but when you pull up the device details, it should show all of them.

CAVEAT: This is all my own assumptions, based on my understanding of how the KACE Agent works, we don't actually manage our servers with KACE, so I have not seen this scenario first hand.

Answered 07/16/2015 by: BHC-Austin
Fourth Degree Black Belt

  • Thank you for the clarification. What we are experiencing is the KACE is only seeing the first IP of the device in the system details. The other IPs when found during network discovery are appearing to be their own instance, without the agent installed (even though it is).
    • Makes sense. The agent is likely only listening on the AMP port via the primary IP, so network discovery doesn't see the agent via the other IP addresses.
Please log in to comment
Answer this question or Comment on this question for clarity