KACE Product Support

I'm not sure if their is a way to merge the 2 but you could make the new machine checkin with the old Kbox record. First go into the old machine record and click on the K1000 Agent section and record the KACE ID number. Then go into the registry on the new computer at HKLM\Software\Kace and replace InstallId and MachineId with the old Kace ID number and it should start checking in with the old record.

There isn't a merge function per say in the KBOX. They both created separate KUID's because of the hardware change you made. If this is a recent change you can take the KUID from the old machine and update the new machine with it so the KBOX thinks it's the same device and then continues to update the asset history in the same record as before and will keep the asset information of the devices previous life.

We added the Kace ID from the old machine to the new machine by changing the registry key in this location HKLM\Software\Wow6432Node\kace
It didn't work. Showing different Kace ID in inventory.
We are using a 64 OS with a 32 bit agent.
Is there another path that we should try?

Someone (whith more SQL and VBA knowledge than me) should write a script that can detect duplicates based on BIOS serial number, read the ID from the old record, and update the registry of the computer.  If replacing the ID in the registry is all it takes to solve the problem, why hasn't KACE put this out a long time ago?  This has been a thorn in our sides since the day we started using the system five years ago.

It would appear that as of March 2021, with version 10.2.234 of the K1 and Agent version 10.2.108, there is no longer a registry entry for the KUID. Instead, it is found in "\ProgramData\Quest\KACE\kuid.txt".

Be aware that both "\ProgramData" and "Quest" are hidden directories.

The contents of the "kuid.txt" file apparently are case-insensitive. My original had lower-case hex digits, whereas what I got out of the K1 console which I pasted into a new "kuid.txt" file (having renamed the old as a backup) was upper-case.

To find the kuid in the K1, I selected Inventory/Devices/[device of interest - click on it to go into its Device Detail]/Agent/KACE ID. It'll look something like E2DE3349-CA0B-41E2-B73A-9459183A5D49.

After forcing a "runkbot 2 0", "runkbot 4 0", and "runkbot 6 0" from the client machine, it showed up in the K1 inventory as the old machine. Sort of. The K1 seemed confused about which machine was online. So I rebooted the client PC, which seemed to sort out the K1. I make no guarantees that the K1 isn't confused deeper under-the-hood. I then deleted the remaining inventory record for this machine, which hopefully won't affect me or the system adversely.

Thank you both! We'll give it a try and see what happens.