locked
Boundary Groups and Content Selection RRS feed

  • Question

  • Hoping to get clarification on something...

    Scenario:

    "AD Site 1" contains all subnets from 5 physical locations.  Each physical location has multiple subnets and will have a local Distribution point.

    If I am understanding everything I have read, if I add all 5 Distribution Points to a single Boundary Group that contains the single Boundary of "AD Site 1", the clients will get a list of all 5 DP's when requesting content (since they would all be "Preferred Distribution Points") and select the one physically closest to itself (i.e. the local DP).

    If that truly is the case, how would a client determine which DP was physically closest if the DP and the client are on different subnets in the same facility?

    In the past I have always used individual Boundary Groups containing only the DP and list of subnets for a particular location, or an AD site if it only contained subnets for the physical location.  

    Trying to get clarification is this is truly required or not, or of my first statement above is valid and can guarantee clients wont cross the WAN to another location for content.

    Thanks!


    Friday, April 18, 2014 6:34 PM

Answers

  • This is for 2007 so isn't completely valid for 2012, but the part about determining which is closest is:

    http://technet.microsoft.com/en-us/library/bb932150.aspx

    For your scenario above, it'll be random because there's no information available to the client about which is closest.

    For what you've given above, I would not use an AD site boundary (I rarely use them -- partly for what you've described above) and would instead use IP Address Range boundaries and 5 DP groups (one for each DP).


    Jason | http://blog.configmgrftw.com

    Friday, April 18, 2014 7:55 PM

All replies

  • This is for 2007 so isn't completely valid for 2012, but the part about determining which is closest is:

    http://technet.microsoft.com/en-us/library/bb932150.aspx

    For your scenario above, it'll be random because there's no information available to the client about which is closest.

    For what you've given above, I would not use an AD site boundary (I rarely use them -- partly for what you've described above) and would instead use IP Address Range boundaries and 5 DP groups (one for each DP).


    Jason | http://blog.configmgrftw.com

    Friday, April 18, 2014 7:55 PM
  • Thanks Jason, I expected this would be the case.  I'll stick to the tried and true subnet boundaries. :-)

    Friday, April 18, 2014 8:35 PM
  • tried and true subnet boundaries

    Tried and found lacking and problematic is more accurate IMO. IP Address Ranges FTW.

    Jason | http://blog.configmgrftw.com

    Friday, April 18, 2014 8:44 PM