Sccm update collection membership not updating
I've since added an exception to Trend File scanning for the PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\inboxes folder and I've noticed a considerable improvement - I'll post back after a week or so to let you know how it's going.It seems the actual problem here was down to the sheer volume of collections running updates.This could generally happend if you have an unoptimized query , querying big tables like 'software files.' There are multiple ways to look at it including with sql enabled logging. you have some experience with SQL you could try looking if the Query is a long runner. It is sometimes useful, however, to update a collection outside of the normal schedule, a process referred to as "forcing an update." You can force an update to all collections at once or to any individual collection at any point in time.When you update a collection, Configuration Manager 2007 reevaluates the resources in the site against the membership rules that are defined for the collection.Microsoft is conducting an online survey to understand your opinion of the Technet Web site.If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.
The sample scripts are provided AS IS without warranty of any kind.For more information about security permissions, see Classes and Instances for Object Security in Configuration Manager.The Update Collection Membership activity is used to initiate collection evaluation.Finally I spotted a few references to AV related issues (which I suspected were responsible for another issue I have with slow PXE boots).Sure enough, when I killed off all the Trend related services from Windows Task Manager and did another update and refresh of the collection - IT WORKED!!
Applies To: System Center Configuration Manager 2007, System Center Configuration Manager 2007 R2, System Center Configuration Manager 2007 R3, System Center Configuration Manager 2007 SP1, System Center Configuration Manager 2007 SP2 Collections that are based on direct-membership rules need to be manually updated by the Configuration Manager administrator (in the same manner as each resource was originally added to the collection when it was created).