Extremely new to configuration manager and have just set it up in a lab environment, so please bear with me.

If a client falls into the network location of a boundary group, if you assign multiple distribution points to a boundary group, what determines the distribution point that a client uses? especially if these distribution points are members of a group and therefore contain all the content.

Also, if you have multiple management points configured in a single site, and if automatic site assignment is used (you've extended the schema), what management point will the clients connect to? 

Thanks

Jason Sandys answered your question here :

https://social.technet.microsoft.com/Forums/en-US/c24cf39d-2291-4616-815e-2f5927dc02df/multiple-managementdistribution-points-and-client-selection-in-a-highly-available-scenario?forum=configmanagerdeployment

Okay, brilliant.  But with multiple DPs, are they also chosen at random? I wouldn't want all the clients always going to the same DP each time - It wouldn't be very balanced.

It's random. You won't have all your clients selecting the same DP.

Read more about the whole process :

https://sccmguru.wordpress.com/2012/05/08/how-preferred-distribution-points-and-fallback-is-working-in-configuration-manager-2012/

https://technet.microsoft.com/en-us/library/gg712321.aspx#BKMK_ContentSourceLocation

Here's a flowchart from ConfigMgr 2007 that is still applicable to 2012: https://technet.microsoft.com/en-us/library/bb932150.aspx .

After all the criteria have been exhausted and everything is still equal, as noted by Benoit, it's simply and effectively random (or at least nondeterministic meaning that there probably is something simple that the code uses to break the tie but they won't tell you what it is and its subject to change so counting on it would cause problems in the future).

Hi

i agree to Jason's comments. This is Random behavior of client to pickup available DP.

 If a client is not able to locate the Dp which it contact\established connection first it will contact the next available DP

OR the number of maximum possible connections are already reached and then client goes to next available.

It is more of a direct hit for the already stored information in WMI