1 of 1 people found this helpful
Did you delete the GUID from the registry? If the agent is installed in the cloned image and you didn't take this step, they will overwrite each other in the DB. If you find this to be the case there are two remedies:
1) Reclone after deleting the GUID (there are two entries in the Registry both called "Common API". Cloned machines will generate a unique GUID when the inventory scanner first runs.
2) Configure Duplicate Device ID dection under Configure .... Services on your Core (inventory tab). Don't use more than two Identity Attributes if you go this route ... Computer.Device.Name and Computer.network.NIC.Address usually work well.
Thanks for your help. I didn't remove the two registry entries before cloning the harddrive. Thats the mistake.
Is it possible to remove the registry-entries and make an inventory scan to generate a new GUID? I don't really want to make a whole image of this machine again after deleting the GUID.
Yes it is.
The keys are in two places:
1 - HKLM\SOFTWARE\INTEL\LANDesk\Common API\UniqueID
2 - HKLM\SOFTWARE\LANDesk\Common API\UniqueID
Running an inventory scan with those deleted will generate a new one.
You should - equally - turn on duplicate device detection on the Core (since that's what this feature is for).
LANDesk EMEA Technical Lead
Thanks to both of you for your help!