Microsoft KB Archive/248150

From BetaArchive Wiki
Knowledge Base

Article ID: 248150

Article Last Modified on 10/27/2006


  • Microsoft Systems Management Server 2.0 Standard Edition
  • Microsoft Systems Management Server 2.0 Service Pack 1

This article was previously published under Q248150


When you use Systems Management Server (SMS) in a three-tier hierarchy, package status as viewed at the middle-tier site may be inaccurate for the third-level child site.


This behavior occurs when you create a package at the central site in a three-tier hierarchy. When you view the package status from the middle-tier site's Administrator console, it indicates that the package has not been received. However, the information is correctly presented at the central site.


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

236325 How to Obtain the Latest Systems Management Server 2.0 Service Pack


Microsoft has confirmed this to be a problem in Systems Management Server version 2.0 This problem was first corrected in Systems Management Server version 2.0 Service Pack 2..


A three-tier hierarchy is shown in the following example:

   CEN (central site)
   MID (middle tier)
   BOT (third tier - this is usually a secondary site)

In this situation, the package status for a package created at CEN for deployment to site BOT is not accurate when viewed from the Administrator console at the MID site.

Additional query words: prodsms

Keywords: kbbug kbenv kbfix kbpackage kbserver kbsms200sp2fix kbsmsadmin kbsoftwaredist KB248150