Other child sites are unexpectedly removed after you delete a child site from the parent site in Systems Management Server

When you use the SMS Administrator console to delete a child site from a parent site in Microsoft Systems Management Server (SMS) 2003 and in SMS 2.0, other child sites that belong to the same parent site are unexpectedly removed.

This problem may occur because of the timing of events in the SMS site hierarchy. If a change is made to the site control file for the site that you want to delete, and then that change is processed immediately before the deletion of that child site, this problem may occur.

SMS 2003 service pack information

To resolve this problem, obtain the latest service pack for Systems Management Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Systems Management Server 2003 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. 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.

Prerequisites

No prerequisites are required.

Restart requirement

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

Hotfix replacement information

This hotfix does not replace any other hotfixes.

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 tool in Control Panel.

Systems Management Server 2003

Systems Management Server 2003 Service Pack 1

Systems Management Server 2.0 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. 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.

Prerequisites

To apply this hotfix, you must have SMS 2.0 Service Pack 4 (SP4) installed on the computer.

Restart requirement

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

Hotfix replacement information

This hotfix does not replace any other hotfixes.

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 tool in Control Panel.

To work around this problem, wait 24 hours for the SMS site hierarchy to correct itself. The SMS site hierarchy will correct itself when the deleted child site sends a heartbeat control file to the parent site.

For additional information about what occurs when you use the SMS Administrator console to delete a child site, see the "More Information" section.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Systems Management Server 2003 Service Pack 2.

When a child site is deleted from the SMS Administrator console, the child site is deleted from the parent site database. The child site is not removed from the child site server. The child site remains fully operational.

The SMS hierarchy will correct itself within 24 hours when the deleted child site sends a heartbeat site control file to the parent site. When the parent site receives this file from the child site, the deleted child site entry in the parent site database is replaced. After the deleted child site database entry is replaced, the hierarchy will appear as expected in the SMS Administrator console.

Note When the deleted entry in the parent site database is replaced, additional site replication traffic will occur because the child site will replicate all client and software distribution information to its parent site. For more information, click the following article number to view the article in the Microsoft Knowledge Base: