ConfigMgr 1610 brought a few welcomed changes and new features. One of those is boundary group relationships. Boundary Group relationships control fallback and mainly applies to content distribution (i.e. distribution points). There’s now a new tab when looking at boundary groups:
Essentially, it works like this. Assume you have three Boundary Groups – Seattle, Los Angles, and New York. A relationship between these boundary groups can be established to allow clients to get content from another boundary group if their distribution point is offline for a given amount of time. For example, SEA-CLIENT01 is in Seattle and cannot get content from the distribution point (we’ll call it SEA-DP1) in Seattle for 30 minutes. I can make the SEA-CLIENT01 go to the distribution point in LA (called LA-DP1) to get content after 30 minutes, then to New York (called NYC-DP1) after 60 minutes. The transfer to New York will only take place if the distribution point in LA is also not available for 30 minutes.
By clicking the “Add” button from the screenshot above, we can select the boundary group to and a fallback time.
The option for “Never fallback” will prevent the selected boundary group for acting as a fallback. In this example, I am configuring the Log Angles boundary group. If I never want this boundary group to use New York as a fallback location, I select New York, then check the “Never fallback” box.
All content provided on this blog is for information purposes only. Windows Management Experts, Inc makes no representation as to accuracy or completeness of any information on this site. Windows Management Experts, Inc will not be liable for any errors or omission in this information nor for the availability of this information. It is highly recommended that you consult one of our technical consultants, should you need any further assistance.