I've created and tested a new primary and everything seemed to be working fine until this week when I started migrating DP's. I'm removing the boundaries from the old primary, removing the DP from the old primary, reinstalling OS, and adding to new primary, but not just as a DP, but as a Secondary Site Server and Proxy Management Point - I also create a boundary at the secondary site server level and make the DP protected. I'm using a script that I apply to each office OU start script to move the clients over as I do one office at a time. Clients are pointing to the correct MP and show the correct site code. Now when I deploy software or try to image a machine, client side logs show that it is pulling packages from the primary instead of the local DP/Secondary site server. Any ideas about what I missed? It has been a few years since I created secondary site servers, and I do not remember having this kind of issue, I have not had to diagnose SCCM issues in a long time either, so reccomendations for what logs to look at would also be helpful. Later, Lee

Have you specified the boundaries in the secondary site as IP ranges? That's what I would do.Kent Agerlund | My blogs: blog.coretech.dk/kea and SCUG.dk/ | Twitter: @Agerlund | Linkedin: Kent Agerlund

I think I see the issue (noticed when adding the IP subnets to replace AD based boundary) - boundaries do not appear to be replicating up the chain to primary and central - any ideas what might cause this?Later, Lee