Modifying SCCM database for service desk reports and database.
I am new to SCCM.When I generate the report using ConfigMgr Report Viewer, example summary of computer; it shows some information. I want to add custom information on it example like warranty period, location code and user name(my own data), is that possible? I want to use the SCCM data and custom data for the service desk implementation to capture all information about a particular asset.I dont prefer creating another database as it will be difficult have to sync between SCCM database and custom database.Is it possible to add additional information to SCCM database only so that making repots is easy.Or should I make another database to store the custom information and draw asset data from SCCM and generate another query for it, but i not sure how to do it? Pl help
August 27th, 2010 8:38am

If you use Dell computers Sherry has a mof edit that will automatically collect Dell warranty info from Dell and pull it into SCCM. For location etc if you just add that info into AD on the comptuer record SCCM can collect it from there. You should be aware that adding custom data into SCCM in any way other than the two already mentioned here is a bad idea. Instead you should add the custom data into another database and join the two for reporting purposes. Custom tables can cause nightmares when you upgrade. John Marcum | http://myitforum.com/cs2/blogs/jmarcum |
Free Windows Admin Tool Kit Click here and download it now
August 27th, 2010 3:12pm

To add to everyones comments: all of the above is true, there are multiple ways to get information. My 2 cents: from a design standpoint, storing information locally on a computer for later retrieval isn't a great place to store that information. The computer could get reimaged, stolen, crash, virus wipes out regkeys, anything... and then your original location for that information is just plain gone. It's not a reliable place to store that information. If you don't like any of the other ideas, like WIR, or the Dell Warranty script + mof edit, if it is static information you need to record, as you mentioned about a separate db, hire (perhaps temporarily, a contractor) someone to setup a database that you manage to input the information about warranty per computer. That contractor then sets up and configures an SRS report to join the information from both your ConfigMgr db, and that standalone DB. In this way, the standalone database is independent of ConfigMgr, and you could be reasonably sure that the information contained inside is accurate. Another option; instead of using a computer's registry to store information, use currently-unused attributes in the Computer object in Active Directory. That could still get wiped: if you have reimage practises that wipe/recreate the computer object for example. But the computer record might be a slightly more reliable place; in addition, there are multiple ways to query AD, that is sometimes a draw to a lot of techs which aren't as familiar with ConfigMgr. Then in ConfigMgr, you can use AD System Discovery to add those additional attributes; and now the information is in ConfigMgr, just the source was AD, not regkeys.Standardize. Simplify. Automate.
August 27th, 2010 3:29pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics