I've gone through and removed all update schedules from our collections (yes - it was a lengthy monotonous task) and all is well.
If you are having problems with collections taking a long time to refresh membership, it is very possible that you have incremental updates or collection membership evaluation schedule set of happen frequently on a large number of collections.
(Pre-installed collections update once per day by default.) A collection is also automatically updated whenever a collection is modified or a linked collection is deleted.
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.
So now you have 1600 collections set at incremental updates, what do you do?
You could manually change each and every collection...
It seems the actual problem here was down to the sheer volume of collections running updates.
I think I'm going to have to run the client removal tool on these machines and try again.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!!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.These are the ramblings of a 30 something (going on 60) year old disgruntled IT Professional.This is gradually evolving into a Windows SCCM blog but there's a bit of "me stuff" in here too as I like to write so have a look at some of my work. I've had a problem with the old girl recently - our SCCM 2007 environment had been chugging along nicely until a few weeks ago. 500 collections with update schedules running pretty evenly throughout the day.you will need to set the This website and its content is copyright of ITHierarchy Inc - © ITHierarchy Inc 2013-2015. Any redistribution or reproduction of part or all of the contents in any form is prohibited other than the following: You may not, except with our express written permission, distribute or commercially exploit the content.Nor may you transmit it or store it in any other website or other form of electronic retrieval system.New machines are getting thrown into the default collection, but anytime I try to move them into a user created collection they refuse to move and I just get an hourglass on the bottom right of the destination collection. I've also tried modifying the rules to make these computers memebers and that refuses to work too. Essentially right now I cannot move any computer to any collection, but the All Systems/All Clients collection are picking up new computers no problems. Which I could update to and see if its sorted, but they do specify many issues can carry accross in the upgrade so it's best to get them sorted first. Now the hourglass just wont go away, have had it there for over a week. SCCM has a habit of doing some decent logging, what about the log files on the server and viewing them with cmtrace when you try and add to a collection i've troubleshot several problems with the existing sccm at work and have used the logfiles many times to work out whats going on (or what was not) hasn't been any changes to account rights on sccm itself, or any of the service / network accounts your system uses? I went to google it yesterday and came across the fact there's a new SCCM version (current branch). So I'm doing this and they are not moving and the hourglass appears.