To add on to this - on a more strategic level - with any kind of custom data, there's always only ever two possible places of data entry.
1 - The Console direct (thus directly throwing this data into the DB)
2 - The client somehow (and the information would be fed in via inventory as custom data).
Now, it's generally CONSIDERABLY preferable to come up with a process that works for you that holds this data on the client. Direct data-entry via Console while certainly possible is very much NOT preferred.
Why?
Simple - data resilience.
======
If your database should go down the pan, and you find out that the guy who's supposed to have been making backups wasn't (i.e. - "worst case scenario" ) - what do you do?
If your data is only ever directly entered in the DB, you'd be pretty much screwed. You'd have no access to your passwords, and thus would've locked yourself out.
=======
Compare this with having the data on the client (or the drive) and getting it to the Core. If the database should go up in flames - no problem - just set up a new DB, and the data will come in as custom data again.
If the client should go up in flames, again - no problem - you've got all the data in the database anyway.
=======
So whatever process you decide on, I would certainly recommend of holding the data on the client side for resilience ... it's not always possible (I know), but that's the more secure option.
Paul Hoffmann
LANDesk EMEA Technical Lead