1 of 1 people found this helpful
- you COULD "risk" editing the basic DB-configuration file ... *BUT* - that'd get overwritten when a new service pack / version upgrade would occur and could potentially cause problems.
- If you have LDDA (LANDesk Data Analytics) you can use the Database Doctor to create a new field mapping essentially. Not sure if that's an option for you (it depends on whether you have LDDA).
- There's a way to model tables & attributes yourself (which for a single attribute would be overkill).
- You COULD create (/modify) an inventory scan to include a field of:
COMPUTER - SYSTEM - HOUSE SERVICE TAG = 22.214.171.124
... combine *THAT* with the information from the following article -- How to find and query Custom Data via SQL -- you can find the data attribute link (which you could then mass-insert via direct SQL inject if you felt like it).
There's a few more tricks around it (such as persistence level of that data) ... a good chunk of which depends on your comfort level with both SQL & getting stuck in with the DB directly (hint - make sure you've got backups and operate on a dev database first).
Note that *IF* a device doesn't have data for a certain data-field, then we're not going to display that data field in inventory (removes the clutter in inventory). So you generally will only ever see data fields that HAVE a value .
Does that help a bit?