Better is the following solution that also returns the distinguished name rather than all OUs: use ADSD.
Our Active Directory System Discovery will be logically scoped to OUs containing machines. No, but it is definitely better than using v_RA_System_System OUName .
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!!
There was a cumulative effect of the schedules and come 1pm the collection action list was backed up with about 3 hours of updates pending.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.As I'm sure you will agree the annoyance of the the old Update Collection Membership and then refresh the console is a blight on our day - but when that little red eggtimer WILL NOT DISAPPEAR it sends my SCCM OCD twitching and I just cannot carry on with my day until I've sorted it...Finally I spotted a few references to AV related issues (which I suspected were responsible for another issue I have with slow PXE boots).