/build/static/layout/Breadcrumb_cap_w.png

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,


0 Comments   [ + ] Show comments

Answers (9)

Posted by: Roonerspism 13 years ago
Second Degree Brown Belt
0
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
Posted by: GillySpy 13 years ago
7th Degree Black Belt
0
A blank KUID is a problem that should never happen. You should call support. If you generate a manual inventory on that machine does it show a KUID? Do you have something preventing inventory gathering like corrupt WMI? What agent version?
Posted by: afzal 13 years ago
Fourth Degree Green Belt
0
Gerald, Both records are from the same machine. You can view that Kbox is fetching the same serial no. I dont know why it is creating 2nd entry.
Posted by: GillySpy 13 years ago
7th Degree Black Belt
0
The more recent entry is the one with a KUID so I guess it fixed itself. Was this a machine that was re-imaged? A new machine?
Posted by: afzal 13 years ago
Fourth Degree Green Belt
0
Gerald,
No, machine is not reimaged, it was working fine with single entry then suddenly Kbox has started creating these duplicates. Have you noticed the Database ID, the computer record which dont have KACE ID has a greater (26) Database ID, and i think it is the most recent entry

Regards,
Posted by: GillySpy 13 years ago
7th Degree Black Belt
0
The database ID shows when the inventory record was first created. The last check in time shows that record 9 is the most recently updated. So if it had something wrong it fixed itself perhaps.

What agent version? Do you have debug logs from that time? I recommend to call support with that info.
Posted by: afzal 13 years ago
Fourth Degree Green Belt
0
OK, just last thing if you could help me ! Now Kbox is generating Service Desk Emails of closed Tickets when i am deleting duplicate machines from inventory. Is there any way to prevent it.
Posted by: afzal 13 years ago
Fourth Degree Green Belt
0
Gerald,

Thanks for your help , I have found the post with your comments.


Regards,
Posted by: GillySpy 13 years ago
7th Degree Black Belt
0
Excellent
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
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