During my deployment testing we have discovered all devices in AD. Now I'm setting up the secondary servers and thier associated boundaries under the parent. How can I get the most current data discovered so that each new boundary setup will have the correct sytems discovered/associated with that secondary's/boundary. What we have done to date for auto push is to remove items with issues from the all systems collection, uncheck delta, select update as soon as possible and then put delta back on. This causes a full rediscoery of all AD items and freshes the SCCM database? The other option I have is to just try to deploy systems with issues using the manual push via the parent rather than let auto push it. So which makes sense?Also, this isn't realistic as I'm deploying accross the world in different time zones. Shouldn't the auto push and discovery work together to update the SCCM database and poush clients in the boundary even after the discovery (i.e so it doesn't have to be a new system in AD How long must we wait for data to be refreshed? Note: we use a IP range for boundaries. jeff parker

Here's a great post on the auto-client push process: http://myitforum.com/cs2/blogs/jgilbert/archive/2007/02/22/sms-2003-client-push-installation-method-explained.aspx. Note that you do not need to uncheck delta to run a discovery cycle as there is no way to force a delta discovery. Also remember that just because the database has the most crrent info doesn't mean that your collections do; collections are not a real-time reflection of the data in DB. You must update the membership (which reruns the queries used to populate a collections membership) and thus updates the data displayed by a collection.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

Here's a great post on the auto-client push process: http://myitforum.com/cs2/blogs/jgilbert/archive/2007/02/22/sms-2003-client-push-installation-method-explained.aspx. Note that you do not need to uncheck delta to run a discovery cycle as there is no way to force a delta discovery. Also remember that just because the database has the most crrent info doesn't mean that your collections do; collections are not a real-time reflection of the data in DB. You must update the membership (which reruns the queries used to populate a collections membership) and thus updates the data displayed by a collection.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys