Quantcast
Channel: Configuration Manager 2007 Software Distribution forum
Viewing all articles
Browse latest Browse all 629

Creating a Distribution Point Hierarchy -- Is it possible?

$
0
0

 

Hello all,

 

 

So, here is the scenario:

 

I have one primary site and 2 secondary sites.  Envision the primary in the north half of a geographic location, one secondary in the south half of the geographic location , and another secondary in the east half of the geographic location.  Routers exists at the south secondary and the east secondary sites that connect back to the main hub at the primary site location.

 

Now, the logical thinking here was to created stand-alone distribution points in remote locations across the geographic location and add them accordingly as site systems in their respective geographic locations as per SCCM site design.  For example, the primary site would push packages to the remote locations to the north and to the secondary sites.  The secondary sites would then push the packages to the remote distibrution points that had been added to the site's site systems node in its site settings.  The secondary sites have been configured as proxy management points.

 

However, when pushing a package out, all the north DP's received the pacakge, the others failed.  Upon moving one of the site systems from the south secondary site, site servers node to the primary site, site servers node and pushing the package again, it received the package.

 

My question is do all distribution points have to be added as distribution points under the primary or can they be added as distribution points under the secondary sites in their respective site settings?  If they can, can someone please point me in the right direction to create this.  The idea here is to minimize network traffic across the entire geographic location.  We'd prefer not to engage all DPs at one time.

 

Thanks in advance!

 

-Matt


Viewing all articles
Browse latest Browse all 629

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>