Systems Management Server 2003 (SMS) Service Pack 3 (SP3) introduces new changes to SMS_DEF.MOF, a file that is used heavily in the hardware inventory process. As a result of these changes, SMS is able to collect more useful information from the client, and extend the functionality of previous releases of SMS. A consequence of added functionality is an increased demand on network resources. Additionally, enabling the Asset Intelligence feature included with SMS SP3 will result in additional consumption of network resources. This documentation is intended to help customers understand the change.
It is important to note that the amount of data gathered and transmitted during the first data collection cycle is far greater than subsequent cycles. This is because the first data collection cycle gathers all applicable information about a computer, whereas subsequent cycles only transmit those items that have changed since the last data collection cycle.
Network impact is greatly influenced by the number of computers in a site, and the amount of software installed on each inventoried computer. Care should be taken when enabling additional classes in SMS_DEF.MOF to avoid excessive impact to network bandwidth. One suggested approach would be to add only one new class per data collection cycle to avoid a situation where multiple classes were transmitting large amounts of data during the same data collection cycle.
Asset Intelligence classes added to SMS_DEF.MOF during setup
In Systems Management Server 2003 Service Pack 2 and earlier versions, SMS_DEF.MOF on the installation source (under SMSSETUP\INBOXES\CLIFILES.SRC\HINV) is the same as the one installed on the local disk. In SMS SP3, SMS_DEF.MOF is dynamically changed based on the Asset Intelligence option chosen during installation. Therefore, the size of SMS_DEF.MOF that is installed on the local disk is larger than on the installation source.
The following options describe possible scenarios:
-
If you choose “Do not install Asset Intelligence”, then Asset Intelligence specific classes will be added into SMS_DEF.MOF, but not enabled.
-
If you choose “Install only data collection” or “Install both data collection and reports”, then Asset Intelligence specific classes will be added into SMS_DEF.MOF and enabled. Two Asset Intelligence classes, SMS_SoftwareShortcut and SMS_InstalledExecutable, are not enabled. In this scenario, Asset Intelligence classes that are added to SMS_DEF.MOF and their default status are displayed in the following table.
| Asset Intelligence Class | Default Status |
|---|---|
|
SMS_InstalledSoftware |
Enabled |
|
SMS_InstalledSoftwareMS |
Enabled |
|
SMS_SystemConsoleUsage |
Enabled |
|
SMS_SystemConsoleUser |
Enabled |
|
SMS_AutoStartSoftware |
Enabled |
|
SMS_BrowserHelperObject |
Enabled |
|
Win32_USBDevice |
Enabled |
|
SoftwareLicensingService |
Enabled |
|
SoftwareLicensingProduct |
Enabled |
|
SMS_SoftwareShortcut |
Not Enabled |
|
SMS_InstalledExecutable |
Not Enabled |
| Note |
|---|
| SMS_SoftwareShortcut and SMS_InstalledExecutable generate a large amount of data when initially enabled. These classes are not enabled by default because other classes already provide much information for software installed on clients. Furthermore, enabling these classes does not provide information for any existing reports. To use data gathered by these classes, a custom report must be generated. |
| Note |
|---|
| All Asset Intelligence specific classes are new in SMS SP3. A new provider instance of __Win32Provider, for provider "AAInstProv", provides data for Asset Intelligence classes. |
Additional Changes to SMS_DEF.MOF
Aside from the changes introduced by Asset Intelligence, there are modifications to SMS_DEF.MOF in SMS SP3 that should be noted. The following table lists added or modified classes and provides a brief description of purpose, function, or change. Also noted is whether the class is an existing class that has been modified, or is new for SMS SP3. Classes that are not new in SMS SP3 have been changed to improve functionality.
| Class name | Comment | New in SMS SP3? |
|---|---|---|
|
CCM_LogicalMemoryConfiguration |
Replaces the Win32_LogicalMemoryConfiguration class to better support Vista. Win32_LogicalMemoryConfiguration is removed in SMS SP3 SMS_DEF.MOF |
Yes |
|
SMS_Win32ProviderEx |
This is a new wrapper provider class for SMS SP3. It adds HostingModel to better support Vista. |
Yes |
|
Instance of SMS_Win32ProviderEx, for provider "SMS_CIMV2_EX" |
Changed from “instance of __Win32Provider” for provider "SMS_CIMV2”. In SMS SP3, it adds HostingModel to better support Vista. |
No |
|
Instance of SMS_Win32ProviderEx, for provider "SMS_CIMLD_EX" |
Changed from “instance of __Win32Provider” for provider "SMS_ CIMLD”. In SMS SP3, it adds HostingModel to better support Vista. |
No |
|
SMS_LogicalDisk |
Changed in SMS SP3 to use provider SMS_CIMLD_EX, instead of SMS_CIMLD. |
No |
|
SMS_Processor |
Changed in SMS SP3 to use provider SMS_CIMV2_EX, in place of SMS_CIMV2, and adds the following new properties to collect:
|
No |
|
Win32Reg_AddRemovePrograms64 |
New class to collect Add Remove Programs list information for 64-bit applications. |
Yes |
|
Win32Reg_AddRemovePrograms |
Changed to collect Add Remove Programs list information only for 32-bit applications. |
No |
|
Win32Reg_AdvCliUpdates |
Changed to collect advanced client patch information for SMS SP3 version client. |
No |
Sample inventory size for new classes
All size information has been calculated from the payload that the advanced client sends to the server the first time that inventory is collected. Subsequent inventory collection cycles collect only that data that has changed since the previous data collection cycle. The data sent in later data collection cycles is usually very small.
| Note |
|---|
| These figures have been gathered in a lab environment and are for the purpose of providing an approximation. Actual figures may vary depending largely on the amount of installed software and other variables beyond the scope of this topic. |
The following table lists specific classes and associated data collection sizes. This data suggests that the first inventory cycle will generate about 53k of data, for Asset Intelligence classes, per inventoried computer. This figure is based on the default configuration; enabling SMS_SoftwareShortcut and SMS_InstalledExecutable has a dramatic impact on this estimate. Subsequent inventory cycles should generate about 1k of data per computer for Asset Intelligence classes.
| Note |
|---|
| The provided number of instances during initial inventory is an estimate based on having 40 installed software titles, 7 installed Microsoft software titles, and a single-processor computer. The number of instances on a typical daily inventory is an estimate based on the supposition that the user logs on and off daily, and on a typical day does not install or uninstall software. Every time that software is installed or uninstalled, an instance will be generated for the next inventory cycle. |
| Class | Default | Payload Size per Instance(Bytes) | Instances during initial full inventory | Instances on a typical daily inventory |
|---|---|---|---|---|
|
SMS_InstalledSoftware |
On |
1047 |
40 |
0 |
|
SMS_InstalledSoftwareMS |
On |
290 |
7 |
0 |
|
SMS_SystemConsoleUsage |
On |
330 |
1 |
1 |
|
SMS_SystemConsoleUser |
On |
294 |
1 |
1 |
|
SMS_AutoStartSoftware |
On |
681 |
6 |
0 |
|
SMS_BrowserHelperObject |
On |
589 |
4 |
0 |
|
Win32_USBDevice |
On |
606 |
2 |
0 |
|
SMS_Processor |
On |
496 |
1 |
0 |
|
SMS_InstalledExecutable |
Off |
739 |
500 |
0 |
|
SMS_SoftwareShortcut |
Off |
775 |
50 |
0 |
|
SoftwareLicensingService |
On (Vista only) |
813 |
1 |
0 |
|
SoftwareLicensingProduct |
On (Vista only) |
401 |
1 |
1 |