Duplicate machine Problem Again
Now i am experiencing another strange duplicate computer problem in version 5.2, duplicates are appearing without any change in computer properties, previously we were experiencing duplicates after changing the computer name or reimaging the computer. To avoid this I have mapped BIOS Serial Number to the custom asset field BIOS. I understand this would create a duplicate entry of a computer one time but after deleting that duplicate it keeps on creating a duplicate record of my Laptop, I have deleted the duplicate many times but it Kbox creates it again. I have forced the inventory several time to check if duplicate is appearing at the inventory update. But noticed that inventory update is not causing duplicate, it appears suddenly.
Any help will be highly appreciated.
Regards,
Any help will be highly appreciated.
Regards,
0 Comments
[ + ] Show comments
Answers (9)
Please log in to answer
Posted by:
Roonerspism
13 years ago
Afzal,
What happens if you delete both machine objects and assets? Does it only create one? Does it create two?
We map our bios serial numbers to the serial field in our environment for purposes of de-duplication during re-imaging and find it works very well so far. So well in fact that we run our naming from the K1 box via scripting etc.
I have had the same issue in the past though, and found that a re-installation of the Kbox agent on the machine seemed to fix the problem in about 80% of the cases. It seems that it doesnt always pick up the bios serial number accurately on machines. Ie, we have toshiba's here that every so often would inventory a machine with all 000's as the serial number, updating to the latest version seemed to fix this problem.
Cheers
What happens if you delete both machine objects and assets? Does it only create one? Does it create two?
We map our bios serial numbers to the serial field in our environment for purposes of de-duplication during re-imaging and find it works very well so far. So well in fact that we run our naming from the K1 box via scripting etc.
I have had the same issue in the past though, and found that a re-installation of the Kbox agent on the machine seemed to fix the problem in about 80% of the cases. It seems that it doesnt always pick up the bios serial number accurately on machines. Ie, we have toshiba's here that every so often would inventory a machine with all 000's as the serial number, updating to the latest version seemed to fix this problem.
Cheers
Posted by:
GillySpy
13 years ago
Posted by:
afzal
13 years ago
Posted by:
GillySpy
13 years ago
Posted by:
afzal
13 years ago
Posted by:
GillySpy
13 years ago
Posted by:
afzal
13 years ago
Posted by:
afzal
13 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.