Upgrading SMS and SMS_def.mof

  • Article

If you have upgraded from SMS 2.0 to SMS 2003, you can compare the SMS_def.mof in SMS\Inboxes\Clifiles.src\Hinv to SMS_def.mof.bak or SMS_def.mof.bk0 in \SMS\data\hinvarchive to see if you have made any customizations that you want to reapply to the SMS 2003 SMS_def.mof. Do not copy SMS_def.mof.bak over SMS_def.mof. You lose the Microsoft changes to SMS_def.mof that are introduced with SMS 2003.

Note

  • If you are upgrading to SMS 2003, carefully compare the SMS 2003 SMS_def.mof to your previous SMS_def.mof. Numerous changes have been made to the SMS 2003 SMS_def.mof to include additional useful classes, to reflect changes in WMI, and to remove less useful classes.

When a Legacy Client receives new hardware inventory rules, it generates a complete hardware inventory instead of a delta inventory of changes only. The SMS site server deletes data for the client for any classes not included in the complete inventory from the client (which also means that the classes were not included in the new SMS_def.mof). The history data for any such classes is not deleted. If you had made customizations to hardware inventory, the data for those customizations is lost when you upgrade to SMS 2003 (and its new SMS_def.mof) until you reimplement those customizations and allow time for the clients to run the next hardware inventory cycle. The Advanced Client does not generate a full inventory when it receives new hardware inventory rules. It always generates a delta inventory.

Note

  • The SMS 2003 SMS_def.mof includes some classes that you might have added as hardware inventory extensions (for example, a list of the installed programs in the Add or Remove Programs icon in Control Panel). If you have made hardware inventory extensions in SMS 2.0, you should review the SMS 2003 SMS_def.mof to see if it includes your extensions. If it does, you do not need to re-implement your extensions.

You can avoid losing the data from your hardware inventory customizations (and one of the two full inventory cycles) by disabling the hardware inventory client agent before beginning the SMS site upgrade. When the upgrade is completed, reimplement your customizations in the SMS 2003 SMS_def.mof, and then enable the Hardware Inventory Client Agent. SMS clients still generate one full hardware inventory because of the Microsoft changes to SMS_def.mof, but the data for your customizations is not temporarily lost, and a second full hardware inventory is not required.

Important

  • If you implemented your SMS 2.0 hardware inventory extensions without changing the SMS_def.mof, be sure to adjust those extensions so that the reporting classes are included in the SMS_def.mof. The data class definition and population can still be included in your customization. For more information, see Chapter 3, "Advanced Inventory Collection."
For More Information

Did you find this information useful? Please send your suggestions and comments about the documentation to smsdocs@microsoft.com.