I'm hoping someone can set me straight, I have 5 branch offices that have packages and boot images pushed out to them. They boot from the local DP/WDS server, and run through the TS. However, when they get to the software installation steps, they pull those across the WAN. These TSs are taking forever because of the speed of the WAN. Is there something I am missing to keep those machines contacting their local DP? Also, what would make them use the local DP for images, but the remote DP for software packages? And, does it have something to do with the computers be placed in the default computers OU?Best, Jacob I'm a PC.

Content location is mostly about boundaries: http://technet.microsoft.com/en-us/library/bb932150.aspxJason | http://blog.configmgrftw.com

What I don't understand is why the image is being applied from the local distribution point, but the software install packages are pulling across the WAN. The boundaries for the DP are correct. What steps can I take to figure out why packages aren't pulling from the same DP? They are also out on that branch DP with the images. Doesn't make sense.Best, Jacob I'm a PC.

Hi Did you check LocationServices log file? What did it say about your DP? I strongly concur with Jason to check the boundaries. Also check whether software packages are successfully installed at your respective DP.Cheers | Navdeep Sidhu

Hi Did you check LocationServices log file? What did it say about your DP? I strongly concur with Jason to check the boundaries. Also check whether software packages are successfully installed at your respective DP.Cheers | Navdeep Sidhu

The solution was completely SCCM irrelevant. I took everyone's advice and ensured my boundaries were correct, read through the smsts log files to make sure they correct DP was being hit, and read through the location services log. The problem ended up being an IPv6 routing issue. IPv6 was routing back to the main office, therefore so were the packages. Thanks for your help once again.Best, Jacob I'm a PC.

The solution was completely SCCM irrelevant. I took everyone's advice and ensured my boundaries were correct, read through the smsts log files to make sure they correct DP was being hit, and read through the location services log. The problem ended up being an IPv6 routing issue. IPv6 was routing back to the main office, therefore so were the packages. Thanks for your help once again.Best, Jacob I'm a PC.