/build/static/layout/Breadcrumb_cap_w.png

KACE Product Support Question


Asset database got corrupted, how to fix data?

01/11/2017 1041 views
Our asset database got corrupted. The issue has since been fixed, but there are entries that have incorrect data. We mainly use it to track user laptops, which we assign a company asset tag to (e.g. 103465). Each asset entry also contains the Dell service tag, user, and some other information. However, after the corruption happened, there are some entries that have different company asset tags, but the same Dell service tag. Likewise, there are some entries with different Dell service tags, but the same asset tag. Also, some of the assets have the incorrect user assigned. 

How can we fix this? Can I semi-automate or automate an audit of the Kace data and make sure it matches what users physically have? I would want to know the user, the asset tag and the Dell service tag. (We also have some Mac users, but they are so few that I would be willing to manually audit these entries.)

In the past, someone did a mail merge using an Access database to send out emails to users and track responses, but I'm not an Access expert, and we have Kace, so I'm hoping there's a solution here. Thanks!
0 Comments   [ + ] Show comments

Comments


All Answers

1
There is no real way to automate this, but your issue got me thinking......

If we can aasume that the Dell service Tag information reported in by the KACE agent is correct....

How about setting up a simple service Desk queue, with a drop down to email the user. You could then configure a ticket rule to email the user, tell them in the email you believe they are the owner of machine x and ask them to click on the link which takes them to the ticket in the end user portal and provide their company Asset Tag into the form and also confirm the machine name they are using.

You will then have the user email address, machine name and company Asset tag within the HD_TICKET database, so you could then either manually update the asset record, or alternatively create a ticket rule to update the Asset table with the correct information??
Answered 03/16/2017 by: Hobbsy
Red Belt

  • Thanks @Hobbsy, appreciate the idea! The original issue has evolved and is different from what I stated in my initial question. The issue hadn't been fixed (as I thought it was), and it's due to: the way our KBOX was initially configured (by a staff member no longer here) to match Inventory and Assets, and how we're imaging computers (creates duplicate KUIDs). (Thanks to @chucksteel for solving the the mystery over at http://www.itninja.com/question/laptop-service-tags-being-incorrectly-changed-by-kace)

    I'm not sure how I can "close" this question, but this question doesn't need an answer anymore.
    • I think if you just give the answer a thumbs up that gives it the green light and people see it as resolved. Glad you got it sorted!!
    • I think if you just give the answer a thumbs up that gives it the green light and people see it as resolved. Glad you got it sorted!!

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