Kace Agent Deployment issues

We have "Scale" Virtualization software at one of our sites. Some of the VM's there are giving us issues with deploying Kace but in a weird way. 

DC1 has Agent and is reporting back.
DC2 not reporting back.
Go to install Agent on DC2, but says its already installed.
Remove and reinstall Agent on DC2.
DC2 now reporting back
DC1 disappears from Kace
rinse repeat.

Any ideas?

4 Comments   [ + ] Show comments
  • Is the agent installed on a VM image or template? It sounds like they have the same KUID (KACE Unique ID), which would happen if the agent was on an image, and the same image was used for multiple computers (or VMs, in this case).
    If so, when you uninstall the agent, also delete the folder C:\ProgramData\Quest\KACE to clear out any leftover data. Then when you reinstall the agent, it will generate a new KUID for that computer, and when it checks into KACE, it will create a new device inventory. - ondrar 2 years ago
  • They were imaged or cloned with the agent or traces of the agent installed.

    Hence they have the same KUID, and are fighting each other to report to the SMA - Channeler 2 years ago
  • Not imaged or cloned. Did an export before and after the install and compared the kace id's and they are different. - TBisel 2 years ago
  • What Do you have for Mapped Inventory Field?

    Go to Asset Types, pick Computer or Workstations (or whatever name you have for them).

    You might want to take some time and check this:

    https://support.quest.com/kace-systems-management-appliance/kb/125175/understanding-and-dealing-with-duplicate-machines-inventory - Channeler 2 years ago

Answers (0)

Be the first to answer this question

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