The package objects in a Systems Management Server 2.0 child site are not synchronized with the package objects in the SMS 2.0 parent site (834123)

CAUSE

This problem occurs because the SMS Distribution Manager starts distributing a package to the child site before the SMS provider has processed all the actions for that package.

In SMS 2.0, when multiple actions are executed on a package in quick succession, one notification per action is entered in the PkgNotification table in the SMS SQL Server database. For example, when you add an additional 100 distribution points to a package, 100 entries for the package are entered in the PkgNotification table in the SQL Server database. When the first notification is received, the SMS SQL Monitor service signals the Distribution Manager to process the action.

When the Distribution Manager starts, it queries for all package objects with a pending action and then processes those actions in the order that the actions were received. When these actions are not processed in the correct order, the child site may incorrectly process the actions that are specified by the parent site, and then the child site may no longer be synchronized with the parent site.

Actions that generate notifications for packages can be one or more of the following:

Add or remove a package
Modify the package properties
Update a package
Add, remove, or update a distribution point
Add, remove, or modify a program
Add, remove, or modify an access account for the package

RESOLUTION

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Systems Management Server 2.0 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this hotfix has the file attributes (or later) 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 tool in Control Panel.

   Date         Time   Version            Size    File name
   --------------------------------------------------------------
   22-Dec-2003  20:21                     11,524  Filemap.ini
   08-Jan-2004  21:56  2.0.6.5           354,229  Smsupdate.exe    
   25-Feb-2003  23:05  2.0.1493.5185   1,634,208  Basesvr.dll      
   25-Feb-2003  23:05  2.0.1493.5185     253,840  Distmgr.dll      
   06-Aug-2000  09:51  2000.80.194.0     274,489  Ntwdblib.dll     
   23-Feb-2003  10:05  2.0.1493.5011     855,312  Preinst.exe

Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

MORE INFORMATION

When the properties of a package are changed, the SMS Provider creates a package change notification record in the PkgNotification table in the SMS database. The SMS SQL Monitor service detects the change and wakes up Distribution Manager. Distribution Manager waits before it bundles all the package change notification records that are found in the PkgNotification table and processes the property changes for all packages that are found. Originally, Distribution Manager waited 5 seconds before it processed the changed packages. With this hotfix, the delay is 10 seconds. This delay includes the default 5-second Notification Delay setting and an additional hard-coded 5-second delay for SQL synchronization purposes.

The hotfix creates two new registry values. With these registry values, Distribution Manager can more accurately detect and process package change notifications. Before the hotfix, package notifications stored the time value in hours and minutes. The old behavior meant that some package change notifications were deleted before they were ever processed. The new behavior stores the notifications time value in hours, minutes, and seconds.

This hotfix adds the Last Notification Time value and the Notification Delay value to the following registry subkey:

HKeyLocalMachine\Software\Microsoft\SMS\Components\SMS_DISTRIBUTION_MANAGER

Value: Last Notification Time (REG_DWORD)
Explanation: This value stores the time when the Distribution Manager processed the last package change notification. This setting must not be changed manually.

Value: Notification Delay (REG_DWORD)
Explanation: This value controls the period of time that the Distribution Manager waits before it processes package change notifications. The value can be between 5 and 300 seconds.

Because the Notification Delay interval can be extended, you can make more package changes, such as adding Distribution Points or creating programs, before Distribution Manager processes the package change notification and replicates these changes to the rest of the SMS hierarchy. With this registry value, you can significantly reduce the number of times the same package is processed when multiple changes must occur.

The package objects in a Systems Management Server 2.0 child site are not synchronized with the package objects in the SMS 2.0 parent site (834123)

SYMPTOMS

CAUSE

RESOLUTION

STATUS

MORE INFORMATION