This article has been archived. It is offered "as is" and will no longer be updated.
Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
In Microsoft Systems Management Server (SMS) version 2.0, the SMS site where the software distribution package is created is named the package source site. Additionaly, the package source site is always the site that replicates the package definition and package contents to all child sites. This replication occurs with direct child sites and with non-direct child sites. This replication model may have scalability problems for an SMS central site if the following conditions are true:
The SMS central site is in a large environment that has thousands of child sites.
The SMS central site is in a large environment that has centrally-created packages in a multiple-tier hierarchy.
The package replication model changes after you apply the hotfix that is described in this article. Before you apply the hotfix that is described in this article, a child primary site cannot replicate package definition and contents for packages where it is not the source site.
Note An example of the package definition is the package comment and the program data. An example of the package contents is a group of programs such as Microsoft Office XP Professional.
Important In this article, the new replication model is the replication model that exists after you apply the hotfix that is described in this article.
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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
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, contact 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.
You must have SMS 2.0 Service Pack 5 (SP5) installed to apply this hotfix.
You do not have to restart your computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
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 -------------------------------------------------------- 03-Dec-2003 17:36 2.0.1493.5175 253,328 Distmgr.dll 03-Dec-2003 17:36 2000.80.194.0 274,489 Ntwdblib.dll 03-Dec-2003 17:36 2.0.1493.5011 855,312 Preinst.exe
To work around the replication model that exists before you apply the hotfix that is described in this article, you must decentralize package creation. For example, to decentralize package creation, each child primary site must be the source site for its direct children.
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.The new replication model makes it possible for child primary sites to replicate package definition and package content that was created at other SMS sites. In this new replication model, the source site only replicates package definition and package content to its direct children. If those direct children are child primary sites, those direct children replicate to their children. To use the new package replication model, you must apply the hotfix that is described in this article on all sites that have or will have child sites and start the new replication model on all those sites. To start the new package replication model, you must set the value in the following registry key to 1:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Components\SMS_DISTRIBUTION_MANAGER\Package Replication Model
The default value of this registry key is 0. A value of 0 makes the SMS package replication model the same as a site without the hotfix that is descirbed in this article. You must stop and restart the SMS Executive service or the SMS Distribution Manager component for the change to take affect.
Detailed behavior changes
When you create or modify a new package (package, program, and distribution point), the source site only replicates the package definition changes to its direct child sites. After the direct child sites receive the replicated package definition, the direct child sites replicate the package definition data to its direct child sites. This process repeats until the package definition data reaches the last level of the site hierarchy.
An SMS process occurs when a site detects that a new distribution point (DP) is added for the first time for a package at a child site. When this new DP is detected, SMS determines if the site that is requesting the package content is a direct child site. The source site and any primary child site only send out the compressed package content if the site that is requesting the package content is a direct child site.
Warning This new replication model does not work reliably unless the SMS administrator deploys the package contect correctly. The SMS administrator must make sure to deploy the package content to all the middle-level child primary sites before adding DPs for third-level secondary sites. Otherwise, the package content never reaches the secondary sites.
When a site detects that a new site has been added to the site hierarchy, it replicates package definition data to that new site. This replication occurs only if the new site is a direct child site. Otherwise, the current site ignores and deletes the notification file (.sha).