Microsoft KB Archive/829817

= Package Updates Are Not Installed on Clients =

Article ID: 829817

Article Last Modified on 10/27/2006

-

APPLIES TO


 * Microsoft Systems Management Server 2003

-





SYMPTOMS
When you use the Distribute Software Updates (DSU) wizard in the Microsoft Systems Management Server (SMS) 2003 Administrator console to update a package, the updates are not installed when the package is advertised to the SMS clients.



CAUSE
This problem may occur if all the following conditions are true:
 * Your environment contains SMS 2.0 sites and SMS 2003 sites in the same hierarchy.
 * You first create the package on an SMS 2.0 site that has the Software Update Services Feature Pack installed.
 * You then use the DSU wizard in a remote SMS 2003 Administrator console to update the package.
 * You then use the DSU wizard on the SMS 2.0 site to update the package again before you advertise the package to SMS clients.

SMS 2.0 site servers do not have specific folders and files that the SMS 2003 DSU wizard uses to create or modify packages. This problem applies to SMS 2.0 sites where the Software Update Services Feature Pack is installed or not.



RESOLUTION
To resolve this problem, use the SMS 2.0 Administrator console to manage all the packages in your hierarchy until you have upgraded all the sites to SMS 2003. In a mixed-version hierarchy, Microsoft recommends that you always use the SMS 2003 software update management feature to manage the software updates for both the SMS 2003 and the SMS 2.0 sites.



WORKAROUND
To work around this problem, follow these steps:
 * 1) Create a new shared folder on the SMS 2.0 site server and name the share SMS_SUIAgent.
 * 2) Grant &quot;Read,&quot; &quot;Read and Execute,&quot; and &quot;List folder contents&quot; permissions to the SMS Admins group on the SMS_SUIAgent share that you created in Step 1.
 * 3) Copy all the files and folders from the SMS_SUIAgent share SMS 2003 site server to the newly created folder on the SMS 2.0 site server.

Note Whenever you apply upgrades to the SMS 2003 site, such as a new International Client Pack (ICP) or a Service Pack, you must repeat these steps.



Interoperability of SMS 2.0 Features with SMS 2003 Features
You cannot use the SMS 2003 version of the Distribute Software Updates wizard to manage software update packages created by the SMS 2.0 Software Update Services Feature Pack tools. The following issues apply in a mixed-version hierarchy where the SMS 2.0 SUS Feature Pack tools are installed:

In an SMS 2.0 site, packages created with the SMS 2.0 version of the Feature Pack tools might not behave correctly after an SMS 2003 site starts to distribute software update packages to the SMS 2.0 site. To resolve this issue, use one of the following methods:  In the SMS 2.0 site, remove all the software update packages that the DSU Wizard created in the SMS 2.0 site. Upgrade the SMS 2.0 site to SMS 2003. Upgrade the SMS 2.0 software update packages to SMS 2003 software update packages. Follow these steps to upgrade an SMS 2.0 package to an SMS 2003 software update package:  Start the SMS 2003 SMS Administrator console. Connect to the SMS 2.0 site.</li> Right-click the Packages node, point to All Tasks, and then click Distribute Software Updates.</li> On the Specify a Software Update Type page, click the type of software update for this package.</li> On the Create an Update Package page, click the name of the package that you want to upgrade, and then click Next.</li> If you do not want to make any additional changes to the package, click Next through the rest of the wizard, and then click Finish.</li></ol>

The wizard copies SMS 2003 Software Update Management client component files to the SMS 2.0 package source folder and updates all the assigned distribution points.

Although the SMS 2003 version of the DSU wizard has features that do not exist in the SMS 2.0 version of the wizard, the upgraded package retains the SMS 2.0 Feature Pack settings until you modify them.</li> Software update status messages have changed slightly between SMS 2.0 and SMS 2003. Review any custom queries or collections to make sure that they refer to the correct status message text of SMS 2003.</li> SMS 2.0 clients ignore some new SMS 2003 Software Update Management settings, such as persistent notification icons and scheduled installation.</li> If an SMS 2.0 site is using the Software Update Services Feature Pack tools, make sure that advertisements for software updates from the SMS 2.0 site and from an upper level SMS 2003 site do not overlap. For example, make sure that the SMS 2.0 site and the SMS 2003 site do not advertise duplicate software updates or duplicate inventory tool updates to clients.</li></ul>

<div class="status_section">

STATUS
This behavior is by design.

Keywords: kbsmsadmin kbinterop kbsoftwaredist kbmisctools kbnofix kbbug KB829817

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.