/build/static/layout/Breadcrumb_cap_w.png

Having an issue with computers renaming themselves thus being removed as an asset.

I have 13 different computers, all domained and named differently but using the same Windows A/D logins.
All 13 computers have had the KACE client installed and have successfully checked in at least once.
But right now I can see in HISTORY that these 13 computers are randomly renaming themselves to another alike computer name.
Attached below is a copy of an example I pulled from the HISTORY LOG..........

I'm also seeing similar issues with other bare bones builds.  This does not seem to happen with any DELL computer, just these, let's call them "OTHER" types of computers.  All of the systems are either Windows 7 or 10.

Does anyone have any idea how to keep my names from changing and losing any asset information.
On the DASHBOARD under INVENTORY and DEVICES, I only see out of these 13 computers, yet all 13 have the agent installed.

Thanks for any help anyone can provide to me.

09/14/2018 15:22:43Reported by AgentDeviceEASTERNTC04ModificationSystem Description'System Description' changed from 'TIME CLOCK12' to 'TIME CLOCK14'.09/14/2018 15:23:46Reported by AgentDeviceEASTERNTC01ModificationSystem Description'System Description' changed from 'TIME CLOCK14' to 'TIME CLOCK11'.09/14/2018 15:24:41Reported by AgentDeviceEASTERNTC03ModificationSystem Description'System Description' changed from 'TIME CLOCK11' to 'TIME CLOCK13'.09/14/2018 15:32:16Reported by AgentDeviceCENTRALTC03ModificationSystem Description'System Description' changed from 'TIME CLOCK13' to 'TIME CLOCK03'.09/14/2018 15:32:59Reported by AgentDeviceCENTRALTC04ModificationSystem Description'System Description' changed from 'TIME CLOCK03' to 'TIME CLOCK04'.09/14/2018 15:33:39Reported by AgentDeviceCENTRALTC05ModificationSystem Description'System Description' changed from 'TIME CLOCK04' to 'TIME CLOCK05'.09/14/2018 15:34:10Reported by AgentDeviceCENTRALTC06ModificationSystem Description'System Description' changed from 'TIME CLOCK05' to 'TIME CLOCK06'.09/14/2018 15:34:30Reported by AgentDeviceCENTRALTC07ModificationSystem Description'System Description' changed from 'TIME CLOCK06' to 'TIME CLOCK07'.09/14/2018 15:35:03Reported by AgentDeviceCENTRALTC02ModificationSystem Description'System Description' changed from 'TIME CLOCK07' to 'TIME CLOCK02'.09/14/2018 15:36:16Reported by AgentDeviceCENTRALTC08ModificationSystem Description'System Description' changed from 'TIME CLOCK02' to 'TIME CLOCK08'.09/14/2018 15:36:36Reported by AgentDeviceCENTRALTC09ModificationSystem Description'System Description' changed from 'TIME CLOCK08' to 'TIME CLOCK09'.09/14/2018 16:01:21Reported by AgentDeviceEASTERNTC02ModificationSystem Description'System Description' changed from 'TIME CLOCK09' to 'TIME CLOCK12'.09/15/2018 03:20:03Reported by AgentDeviceEASTERNTC04ModificationSystem Description'System Description' changed from 'TIME CLOCK12' to 'TIME CLOCK14'.09/15/2018 03:21:20Reported by AgentDeviceEASTERNTC01ModificationSystem Description'System Description' changed from 'TIME CLOCK14' to 'TIME CLOCK11'.09/15/2018 03:23:25Reported by AgentDeviceEASTERNTC03ModificationSystem Description'System Description' changed from 'TIME CLOCK11' to 'TIME CLOCK13'.09/15/2018 03:30:25Reported by AgentDeviceCENTRALTC03ModificationSystem Description'System Description' changed from 'TIME CLOCK13' to 'TIME CLOCK03'.

Asked 6 years ago 607 views
5 Comments   [ + ] Show comments
  • When you are changing them back, Are you doing it in Kace? AD?, or on machine? - TBisel 6 years ago
  • I'm actually not changing a thing. It's happening automatically. These same computers were running just fine on an older 6.0.101864 version. Now that we have upgraded to a new 9.0 VM installation, these computers are acting sooooo weird with their checking in process. All of these re-names are just spontaneously changing. And when the names change, their information in the Inventory Dashboard goes away. Like they never existed. But then a few hours or next day, they reappear. You'd almost have to see it to believe it. - swilczewski 6 years ago
    • Are you saying the agent version was 6.X and the server has been updated to 9.0? Because 6.x agents cannot communicate with 9.0 servers. Might try uninstalling and reinstalling the newest agent bundle on an affected device. - isudothings 6 years ago
      • that will also resolve the possible Duplicated KUID issue, make sure you remove the agent with the all-kuid switch

        AMPTools.exe uninstall all-kuid - Channeler 6 years ago
  • My first guess is that the Kace agent was part of an image that's on all computers. They possibly have the same Kace GUID so Kace thinks there's one machine that's updated whenever any one of the computers is inventoried. - kenwhite 6 years ago
    • this, they have duplicated KUIDs (which should be unique per device), because the Golden Image has the KACE agent installed - Channeler 6 years ago
  • Thanks for the responses everyone. Ok, the KUID could possibly be the reason. All I simply did to these computers was install the new 9.0 agent over the top of an already installed old 6.0 agent. My though was that it would just simply update to the new agent. I'll do a full uninstall on these computers and fresh install of the 9.0 version and see what happens. I'll report back my findings. - swilczewski 6 years ago
  • Channeler.... to use that command (AMPTools.exe uninstall all-kuid) don't I have to have PSTools installed first ? If so, UGH. Guess that's why they call it WORK. LOL. - swilczewski 6 years ago
    • Nope.

      Also check the Inventory.XML file, the BIOS ID field is either missing or duplicated on those devices. - Channeler 6 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