The following list describes other specific events that will cause a hardware inventory resynchronization:

• The inventory delta contains updates for a database record that doesn't exist.
• The inventory delta itself contains bad or corrupted data.
• The client has attached to a new SMS site.
• The client has upgraded from SMS 2.0 to SMS 2003.
• Disabling hardware or software inventory and then re-enabling it.
• When you attach a child site to a parent site, software inventory is resynchronized from the child site.

The resynchronization doesn't change the hardware inventory schedule. The next inventory cycle will start at the scheduled time.

For more information about resynchronization for hardware inventory, see Chapter 3, "Understanding SMS Features," in the Microsoft Systems Management Server 2003 Concepts, Planning, and Deployment Guide.

When you modify the SMS_def.mof file, additional action might be necessary, depending on the type of modification and whether you are running the Legacy or the Advanced Client. When the SMS_def.mof is updated, it is one of these types of modifications:

• An extension to an existing class in WMI
• An additional class supported by an existing WMI provider
• An additional class not supported by an existing WMI provider

Legacy Clients automatically recognize changes to the SMS_def.mof and compile a new version locally on the client, but if you need a new WMI provider, you must install it and register it. If you configure the MOF file to automatically register the new provider, it will be re-registered every time the MOF file is compiled.

For security and performance reasons, Advanced Clients do not download and compile their own SMS_def.mof files. Instead, they receive policies that contain the inventory configuration from their authenticated management points. You must force the Advanced Clients to download and recompile the MOF file.

For both Legacy and Advanced Clients, you can send an SMS package to install the new provider on each client. You can also use package distribution to register the new provider, or you can configure the MOF file to automatically register it.

The following table summarizes what actions are required for each type of modification on each client.

Run the Mofcomp.exe command on the client computer to recompile the MOF file. For more information about running Mofcomp.exe, see Chapter 3, "Advanced Inventory Collection," in the Microsoft Systems Management Server 2003 Operations Guide. For more information about registering a provider, see the Platform SDK: Windows Management Instrumentation.