Environment: 1 Primary (USA), 60 Secondary sites+DP+ProxyMP. I've deployed clients via the secondary site's client push (they were discovered by the secondary site as well, via AD system discovery). The clients install fine, but they do not pick up their proxy MP. Instead, they report back to my primary USA site. When trying to push packages to these clients, they do not locate their local DP and remain in the "waiting for content" state indefinately. I have several secondary sites in this condition...other secondary sites and their client operate as they should. All configurations are identical, boundaries have been verified to be correct, there is no difference between the locations that work correctly and those that don't. Reviewing the client logs (ClientLocation & LocationServices), a working site queries AD and finds its proxy management point, while a non-working site/client queries AD and returns the MP at my primary site. AD records are identical between working and non-working sites/clients (other than site name, of course). Ideas? Questions? Please help.

Can these non-working clients actually contact the primary site mp?Secondary site clients find their proxy mp by asking the primary site mp where it is, that is the initial and only contact a "secondary site client" ever makes with the primary site mp.All other communication comes from the secondary site mp.Check firewall config for the non failing sites and compare with these of the failing sites."Everyone is an expert at something" Kim Oppalfens Configmgr expert for lack of any other expertise. http://www.scug.be/blogs/sccm

Thanks for the reply...yes, the clients at the secondary site can contact the primary MP. They operate as if the secondary site/proxyMP was simply unavailable, and they attempt to pull packages from the primary site over the WAN instead of locating their local MP/DP. I've worked on a couple of these sites this weekend, and if I tear them down and rebuild them, it all starts working again. Odd stuff.