Microsoft KB Archive/263393

{|
 * width="100%"|

SMS: Added Multiple Membership Rules for Collections Not Replicated Completely to Child Sites

 * }

Q263393

-

The information in this article applies to:


 * Microsoft Systems Management Server versions 2.0, 2.0 SP1, 2.0 SP2

-

SYMPTOMS
When you use Systems Management Server (SMS) 2.0 custom collections with multiple membership rules, the membership rules for that collection may not all be replicated to child sites. The collection that you create at the parent site arrives at the child site, but the membership rules are blank or some membership rules are missing. This may cause clients at the child site to be delayed in receiving advertisements, or not to be offered advertisements.

RESOLUTION
This issue was reproduced with 2 direct membership rules set on the parent. Only one of the direct membership rules were displayed on the child primary. Also the workaround documented in the article did not address the issue either. In the case of my customer. He is sending software to the resources in the locked collection at the child site, which does not have all of the correct membership rules so software distribution fails to send out the package to all machines.

WORKAROUND
To resolve this issue create a new collection at the child primary with a different name and use the direct membership rules you have specified on the parents collection. This way you can send softare from the child primary, or send out software from the parent since this collection has the correct memberhip rules.

"-or-" At the parent site, manually force an update on the collection. To do so, right-click the collection, click All Tasks, and then click Update Collection Membership.

STATUS
Microsoft has confirmed this to be a problem in the Microsoft products that are listed at the beginning of this article.

Additional query words:

Keywords : kbsms200bug kbsms200preSP3

Issue type : kbbug

Technology : kbSMSSearch kbSMS200 kbSMS200SP1 kbSMS200SP2