The SMS_def.mof file consists of a list of classes and attributes in the following format:
[SMS_Report(TRUE),
SMS_Group_Name("Boot Configuration"),
ResID(400),ResDLL("SMS_RXPL.dll"),
SMS_Class_ID("MICROSOFT|BOOT_CONFIGURATION|1.0")]
class Win32_BootConfiguration : SMS_Class_Template
{
[SMS_Report(TRUE)]
string BootDirectory;
[SMS_Report(FALSE)]
string ConfigurationPath;
[SMS_Report(TRUE)]
string LastDrive;
[SMS_Report(TRUE),key]
string Name;
The attributes and classes that are set to TRUE are collected, and those set to FALSE are not. However, there is an exception: if a class is set to TRUE (as it is in the example above) then any attributes with the key property are collected, even if the individual attribute is set to FALSE.
You can use MOF Manager to modify the SMS_def.mof file. If there are attributes and classes you no longer want to collect, set them to FALSE. If you want to add attributes, set them to TRUE.
Important Be very careful when modifying the SMS_def.mof file. It was not designed to be executed with all or most of the attributes set to TRUE. The size of the file can affect the performance of your network. The default SMS hardware inventory MIF file generated by complete hardware inventory is about 100 KB. If you modify the file, first verify the size of a typical client's complete hardware inventory and make sure it is acceptable. Then, test the new file in a test site before distributing it throughout your network.
After you have tested the file, you can replace the default SMS_def.mof by replacing the file in the \SMS\Inboxes\Clifiles.src\Hinv directory on the site server. From there, it is propagated to each client in your site.
Related Topics
How SMS Collects Hardware Inventory
Extending the Inventory Overview