We have lots of Service Manager customers that have comprehensive CMDBs where they store all kind of object types and relationships. When defining your very own classes you know that every class should have a key property. Often this is property is called something like “ID” and will contain an auto incrementing value, e.g. “Car1”, “Car2” etc. so that you don’t have to take care about setting a unique value for every instance. Default classes also have key properties, but not always a real ID. The windows computer class uses the computer principal name as a key property. This can be confusing when you re-install computers or re-use computer names – this is especially confusing when accounting comes into play. So why not having an auto incrementing ID property there too to uniquely identify assets over time?
SCSMfaq.ch – Marcel Zehner


Search
Blog Sponsors
Calendar
Categories
- Automation with Opalis (16)
- Change Requests (3)
- Classes and Relations (32)
- Connectors (4)
- General (28)
- Incidents (4)
- Layout (10)
- LB and DR (3)
- Managing Objects (29)
- Non Technical (32)
- Notification (7)
- Preview (3)
- Quick Info (1)
- Release Records (1)
- Reporting (12)
- Service Level Management (2)
- Service Requests (7)
- Speaker (6)
- Tasks (3)
- Troubleshooting (5)
- Views (6)
- Web Portal (5)
- Workflows (11)
RSS
@scsmfaq Tweets
- RT @maarten_goet: I must say, the @SCU_DACH lineup of speakers is one of best I've seen. The best & brightest people from #SysCtr #HyperV &… 17 hours ago
- #itnetx Company Event tonight. #cool 1 day ago
- RT @SCU_DACH: NOW: Early Bird Registration for System Center Universe 2013 DACH #SCU_DACH http: systemcenteruniverse.ch Join our Universe! #S… 1 day ago
- RT @SCU_DACH: Web site available! Register now for #SCU_DACH and be one of the first 50 registered attendees to get a gift http://t.co/qaE6… 1 day ago
- RT @radtravis: Join the #MVP Pro Speaker Series on #SCSM NOW! blogs.technet.com/b/servicemanag… 2 days ago
Blogroll


