- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello Folks,
We are having a intergration between AssetTrack and ServiceNow, my attention is on the other classes ESX Servers, Servers, Windows Servers, in alm_asset table which I feel these not supposed to be in this table.
What are your suggestions on following the best practices approach?
- These classes should be removed from alm_asset table ?
- or it's a part of integration so keep them here as these can be used in future and don't touch OOB setup?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
I don't think these should be removed if you are supposed to be tracking them. The Alm Asset table is a collection of different assets but it's there to track the financial and the lifecycle side of these assets - the ESX CMDB is more for counting the assets and associated CI's.
It is confusing at times having multiple tables but that is the way its been built
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
I don't think these should be removed if you are supposed to be tracking them. The Alm Asset table is a collection of different assets but it's there to track the financial and the lifecycle side of these assets - the ESX CMDB is more for counting the assets and associated CI's.
It is confusing at times having multiple tables but that is the way its been built
