Microsoft KB Archive/263410

= SMS: Distribution Manager Orphans Package Share If Share Name Is Changed During Distribution =

Article ID: 263410

Article Last Modified on 10/27/2006

-

APPLIES TO


 * Microsoft Systems Management Server 2.0 Standard Edition
 * Microsoft Systems Management Server 2.0 Service Pack 1
 * Microsoft Systems Management Server 2.0 Service Pack 2

-



This article was previously published under Q263410



SYMPTOMS
When a Microsoft Systems Management Server (SMS) package is created and the package location is specified rather than using the default package share (SMSPKG $), Systems Management Server creates the new share and copies the package into it. If the share name is changed while the package is being run or if a large application is being accessed by a user, a new package share is created. This orphans the old package share and no errors are generated to let the administrator know that the Distribution Point's original package share could not be updated. If you select Update Distribution Points, the problem is not resolved, but the package is copied into the newly specified location.



WORKAROUND
To prevent this issue from occurring, avoid manually renaming the distribution point package shares after the package has been created and moved to the distribution points.



STATUS
Microsoft has confirmed this to be a problem in Systems Management Server version 2.0.

Additional query words: prodsms

Keywords: kbbug kbnofix kbsms200presp3 KB263410

-

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

© Microsoft Corporation. All rights reserved.