I’ve been using RT for a number of years now, and with the upgrade to 4.4 it seemed reasonable to look at the Asset Management component.
Here’s my situation. We have a number of pieces of software that are licensed across our multi-site organisation. As an example, about a third of our PCs are licensed with a Windows volume licence; the remainder are supplied with Windows at the point of purchase. We do not pre-image our Windows PCs.
I want to be able to track which PCs have our Windows volume licence, and which have one supplied with the PC. (This is for audit, but also it allows me to identify which licence to use if a PC needs to be wiped and reinstalled.)
- Do I create a custom field called something like “Has our Windows volume licence”?
- Do I create an asset called “Our Windows volume licence” and link all the appropriate PCs to that asset? (This is how I’d consider implementing within a relational database.)
- Something else?
Can I then count the number of Windows volume licences?
Another example is use of the subscription version of Office2016, which is licensed per person, not per PC. I can’t see an easy way of handling this within Asset Management. Some users have this but others do not. Maybe I try to continue to track this within Office365 Administration Portal, but it doesn’t give me the information my finance department wants, so I still have to munge it around by hand.
- Do I create a single asset called something like “Office365 ProPlus subscription” and allow multiple users to hold this asset? (Can I even do that?)
- Do I create multiple copies of an “Office365 ProPlus subscription” and assign one per user?
- Something else?
I’m interested to hear how other people have configured and use RT’s Asset Management for these kind of situations.
Finally, I want to be identify assets globally but also by office. It seems that one approach is to create a Catalogue for each office. Is that correct?