This article describes a hotfix rollup package that is available for the Microsoft Systems Management Server (SMS) 2003 client. This update is in the form of an MSI package. It can be used to deploy the new, updated client or to update existing ones by forcing a reinstallation of the client by using a push installation.

The same update is also available as a Client.msp package in hotfix 941395. This is a hotfix rollup package that provides an updated Client.msp for SMS 2003.

The hotfix rollup package resolves the same issues as does hotfix 941395.

For more information about hotfix 941395, click the following article number to view the article in the Microsoft Knowledge Base: Hotfix 941395 updates the existing installation of SMS 2003 SP3 client software. However, the current hotfix rollup package (hotfix 941214) also provides an updated Client.msi package. Therefore, you can deploy the Client.msi package to computers that do not have SMS 2003 SP3 client software installed.

This hotfix rollup package resolves the following problems.

Problem 1

The Wmiprvse.exe process on client computers in the organization may generate high CPU usage while the SMS 2003 SP3 Asset Advisor is performing hardware-inventory operations. The CPU usage may reach 100 percent.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Problem 2

When you schedule advertisements in SMS 2003, you experience the following symptoms:

• Advertisements that have a recurring daily schedule that you create in British Summer Time (BST) run one hour too early after the time changes to Coordinated Universal Time (UTC).
• Advertisements that have a recurring daily schedule that you create in UTC run one hour too late after the time changes to BST.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Problem 3

In a SMS 2003 Service Pack 3 (SP3) environment, a recurring advertisement is configured before the DST changes occur. After the DST time change takes effect, the first instance of this advertisement runs an hour late. However, later instances of this advertisement run at the correct scheduled time.

Problem 4

The hardware inventory process may fail for SMS clients that are running on Windows Vista-based computers. Additionally, Task Manager may display that a Wmiprvse.exe process has more than 500 megabytes (MB) of private working set. This behavior usually occurs on a computer that has more than 100,000 events in the Security log.

The symptoms of hardware failure may vary. Typically, no inventory data is sent to the management point when this problem occurs. Additionally, one of the following messages is logged in the InventoryAgent.log file.

Log message 1Log message 2Log message 3Note This information is logged when some noncritical classes are not listed in the inventory data. The class that is listed in the log information may vary between clients or between instances of hardware inventory that are executed. The 80041013 error code represents a WMI Provider Load Failure (WBEM_E_PROVIDER_LOAD_FAILURE) error.

Problem 5

Some processes have an access violation problem because the AssetAdvisor.dll module allocates insufficient memory. For example, the Wmiprvse.exe process may have the access violation problem.

Problem 6

After you upgrade to SMS 2003 SP3, you run a report that is based on the v_Add_Remove_Programs view. However, the report stops responding. Additionally, the process uses 100 percent of the CPU resources. For example, reports such as the "Computers with specific software registered in Add Remove Programs" report stop responding. Additionally, the process uses 100 percent of the CPU resources.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Problem 7

SMS 2003 should use data that is combined with the ProductID registry entry and the DigitalProductID registry entry to determine sale channel code. Earlier products do not support the DigitalProductID registry entry.

Problem 8

Inventory counts are inaccurate in the License 1A report and in the License 1B report. Multiple components that have the same Microsoft product code (MPC) appear as a single product instead of as individual products.

Problem 9

When Microsoft SQL Enterprise Manager and Books online are installed on the computer, they are incorrectly reported as SQL Server installations in the License Ledger report.

Problem 10

The SMS_InstalledSoftware class incorrectly generates a software code for Windows operating systems by inserting some extra characters.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

How to apply the hotfix rollup package

You must apply this hotfix on the primary site servers and on the secondary site servers. This hotfix automatically replaces the Client.msi file on the site servers. Then, SMS 2003 servers use the new Client.msi file to deploy SMS 2003 client software. When you use the MSI package to update existing clients, use either of the following methods:

• Use SMS software distribution to update the existing Advanced Clients with the Client.msi file.
• Use Client Push Installation to update the existing Advanced Clients with the Client.msi file. To do this, follow these steps:
  1. Start the Client Push Installation Wizard.
  2. On the Client Installation Options page, select the Always install (repair or upgrade existing client) option.
  3. Follow the steps to complete the wizard.
     
     Note When you use the Client Push Installation method, the Advanced Client automatically receives the latest version of the Client.msi file. You do not have to move or copy the Client.msi file.

Notes The installation of this hotfix requires a site reset.

Prerequisites

There are no prerequisites for installing this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix replaces the hotfixes that are described in the following articles in the Microsoft Knowledge Base:

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

For more information on troubleshooting Advanced Client Push Installations see the following article in the Microsoft Knowledge Base:

928282 How to troubleshoot Advanced Client Push Installation Issues in Systems Management Server 2003 and System Center Configuration Manager 2007  (http://kbalertz.com/Feedback.aspx?kbNumber=925282/ ) For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: