Re-creating Assets and Inventory on K1 6.3

I would like to rebuild my inventory and assets.  I seem to have machines that are not creating assets and or have assets with no inventory.
if i delete assets and inventory, will machines that check in populate both an asset and an inventory.
Nothing is tied to the assets but the machine name (Dell Service Tag).
How will this impact my tickets as far as the machines that were listed in the affected machine field?
A nice re-sink with AD would be nice as this is what we are currently using to keep track of inventory of PC's, Tablets, and Laptops only.  Any suggestions and help would be great.
Note: I currently have a GPO for agent provisioning and sometimes we install / repair manually.

1 Comment   [ + ] Show comment
  • I'm also in this bloated boat. I've inherited this appliance and the software list is insane including versions of software no longer installed on any of the hardware. I'm not so much concerned with the device inventory. We only have 300 devices, but would it do any harm to clear out the Software Inventory? Would the devices repopulate it automatically upon checkin? Does the same apply to the Software catalog? - nmarsden 5 years ago
    • I periodically go through and delete software titles that aren't installed. Sort the page by install count so you can select pages at a time with install count of 0, then delete those. It takes some time but it's the only way to clean things up as far as I know. - chucksteel 5 years ago

Answers (1)

Answer Summary:
Posted by: chucksteel 5 years ago
Red Belt

Top Answer

"How will this impact my tickets as far as the machines that were listed in the affected machine field?"

The tickets will lose their association with the tickets because it is based on the machine ID from the database. When machines check in they should get a new ID.

Why do you want to rebuild your inventory?

  • Thats what i thought as i have had to remove a user/tech and all of his tickets went unassigned.
    I have inherited this appliance and there just seems to be so much inconsistency between assets and inventory of machines. As I created some VM's for image building is when I noticed that an inventory would get created but not an asset. I also have inventory and no asset.
    I guess ill just have to start with assets and match with AD, maybe just delete inventory??? which is not so critical as it gets updated on check???
    Then I have to work on Amp Agents not working as well. - wessdf 5 years ago
    • If KACE can't match an asset based on the criteria then it should be creating one. When you edit the computer asset type what are the settings for Mapped Inventory Field and Matching Asset Field? - chucksteel 5 years ago
      • Login User and Name respectively. Im thinking of changing this now that I have looked at it lol. I am very new to Kace.
        Looking over help articles now lol. - wessdf 5 years ago
      • That's an interesting configuration and would lead to assets that change frequently for some machines. We use BIOS Serial Number and Name so that assets are named for the machine serial numbers and machine names can change without breaking the relationship. Our receiving folks can also upload asset data before machines get inventoried and KACE will automatically match them up when they do get into the system. - chucksteel 5 years ago
      • Hmmm, now that im looking around I think that's what we should be using as the current Assets have been Service Tags (Which is the Naming we use in AD). I wonder if when we updated our appliance this got changed to Login User. And would maybe explain why im missing Assets / Inventory.
        Thanks chuck for shedding some light on this. - wessdf 5 years ago
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