/build/static/layout/Breadcrumb_cap_w.png

The K1000 "asset - inventory" connection !!!!

Hi guys.

I have a little problem. All my inventoried computers are also in my

computer assets. Our assets are used for cost accounting and some

basic ticketing systems with the service desk.

 Software licence counts are determined by the machines

in the inventory with the software installed on them.

In order to manage our licences , when machines are delivered back to IT, we delete

 them from the inventory  to free any unused license for other users.

My issue is.... When we delete a computer, the asset part of it will remain, which is fine!!!

But when we redeploy that PC to another user, we would like it to reconnect to the

existing asset ID of that Machine in the ASSETS. (This way we don't lose the ticket history of that machine).

The computer name is the same, but the asset creates a new machine with a new asset ID, that

 has the same name as the old asset ID. A duplicate name with different asset ID basically.

Is there any way we could make The k1 connect a redeployed machine with the old asset ID

if the machine name is the same as the one already existing in the assets. The ticket history

is really important !!!


2 Comments   [ + ] Show comments
  • In Assets, Asset Types, Computer what are the settings for Mapped Inventory Field and Matching Asset Field? We use BIOS Serial Number and Name so our assets are named by the serial number of the computer in inventory. When a machine is re-imaged it re-associates with correct asset. - chucksteel 7 years ago
    • What you have is exactly what I need !!
      In my case ....
      Mapped inventory field is.......System name
      Matching Asset field is ...... Name
      I thought this was enough to re-associate the machine to the asset, seeing as the names are the same. As you can see our assets are named by name of machine.
      I have custom built SQL reports for cost accounts that are being generated every month.
      Will changing the "mapped inventory field" not affect them in anyway? - akmagnum 7 years ago
    • I have tried it your way. works....
      but now I can only search within the assets with bios and serial number. This doesn't really work for us. Each machine has a printed label on it with its name, which makes it easier to search for in assets. Needing the serial of every machine to search is a real hassle as not all the machines are online when we need the info. - akmagnum 7 years ago
      • In that case I would recommend adding a field to the computer asset type to store the system name. This can be updated either by importing a spreadsheet of serial numbers and system names or even with a custom service desk rule that updates the assets. It is annoying that you can't search system name from the assets module. - chucksteel 7 years ago
  • It may be if the same name, but a different KUID it may still not connect, we tend to recommend a best practice of linking the Serial Number or Dell Service Tag to the name of the Asset that will definitely work, - Hobbsy 7 years ago
    • I will give it a try - akmagnum 7 years ago
    • I been using Mapped inventory field BIOS Serial Number but recently we started seeing so many machines with out BIOS serial. I am wondering if any of you have similar issues and have you found a workaround? - samuelcolt 7 years ago
      • We don't have a lot of machines where this has happened, but it has been a small issue. I have seen it most prevalently with Intel NUC devices. - chucksteel 7 years ago

Answers (0)

Be the first to answer this question

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