Cleaning up "Targeted Resources" (Full Version)

All Forums >> [Management Products] >> Microsoft Systems Management Server >> SMS 2003



Message

bdwest -> Cleaning up "Targeted Resources" (9/17/2008 10:30:30 AM)

I was tweaking a Collection query (of course, now I realize I shouldn't have been messing with a live Collection that several advertisements rely on) when my lack of SQL expertise led to the Collection including all systems.  I immediately realized my mistake, changed the query back, and it doesn't appear that anything was installed improperly.  But now whenever I run a report that includes any of the advertisements that point to that Collection, the Targeted Resources column has the number of total systems in that momentary, overly-broad query, not the current query.  This throws my percentages off (% with No Status is in the 80% range), and makes it hard to find real problems with that collection.

So is there any way to clean up after this mistake, to make that Targeted Resources number, and all the other numbers that are based on it, reflect the current reality, not the one-time, mistake-derived status?

Thanks.



jnelson993 -> RE: Cleaning up "Targeted Resources" (9/17/2008 10:55:04 AM)

Have you manually updated the collection membership?



bdwest -> RE: Cleaning up "Targeted Resources" (9/17/2008 11:02:31 AM)

Yep, I did that.  In the Admin Console, the listing and count for that collection are accurate.  But I suspect that the query for the web-based report is looking at the last state, or something similar, to get its number.  In any case, the report is looking at something else besides whatever the Admin Console is for this.



bdwest -> RE: Cleaning up "Targeted Resources" (9/18/2008 9:56:27 AM)

After doing some digging, I realize that the problem is in the artifacts left in the database from that few moments when SMS started trying to roll out the advertisements connected to the collection I temporarily mis-defined.  The view v_ClientAdvertisementStatus still has over 500 records of SMS announcing all the computers it was planning to advertise the program to, records that were "abandoned" when the definition of the collection changed back to its narrower scope.

So does anyone know how to "clean up" the database, preferrably from within SMS, so that the record of attempted advertising (LastState, etc.) would correlate with the current population of a given collection?



Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
0.203125