houston.sports.fan Posted March 22, 2010 Report post Posted March 22, 2010 Here is my situation - I have a SCCM environment with 7000+ clients. We turned on AD System Group Discovery for some testing early on in our deployment. I need to turn it off now, however, because it is causing some clients to "think" they are part of another SCCM site. i.e. COMPUTER-A is in AD Site "Russia", but because it is in a AD Group that is in a New York OU, it is technically assigned to "North America" SCCM Site. This is causing havic in our software deployments, because the client will choose a DP that is on the other side of the world because it believes that is its SCCM Site. It does not affect small packages, but when we pushed Office 2007 roughly 100+ machines were coming back to Houston all the way from Dubai. It was not pretty. Anyway, I turned off AD System Group Discovery and set the "Delete Aged Discovery Data" task to 30 days so it would slowly begin deleting. But it is not deleting this data, and we have about 5,383 clients that still have this agent data. From what I can tell, the task has done nothing and it's been on for well over a month. My questions - why is the data not being deleted? Is there a script I can push to these clients to delete this data quickly? Or is there a quick way to make sure this data is out of my database? I don't want this agent data at all now, I need it all flushed. Thanks all! Josh Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted March 22, 2010 Report post Posted March 22, 2010 have you checked what data is now in active directly in the systems management container, look with adsiedit, perhaps that is sending your clients astray ? if you setup protected distribution points you wouldn't be having this proble Quote Share this post Link to post Share on other sites More sharing options...
