Boudnary Settign SCCM 2012 R2 SP1

Without knowing a little bit more about the architecture of your environment it is hard to know what might be causing this issue.

I am assuming that you have a primary site configure as a management point. Are your secondary sites configured as management points as well or simply distribution points? One thing to ensure is that the following option is unselected on the properties page of each of your servers with the distribution point role installed:


The next thing to double-check is the following:

Assuming you have only central Management Point and site server's with the distribution point role at your secondary sites ensure that you create Boundary Groups for each of your sites for the purposes of assigning distribution points at each site boundary to its respective boundary group. Create one Boundary Group for site assignment only and add all of your distribution points to it.

By doing the above you ensure that your distribution points only look at the local distribution server for content, but look at the central management point for site assignment

Hope this helps

Let me know if you have any questions or require a further description.

let me explain more about my infra

i have one PRI server and 10 Sec server 4 DPs
10 sec server also DPs
I have 14 locations which are connected over the WAN to PRI server.
Sub net boundary group has configured for all 14 locations (10sec+4 dp)
Secondary site code is given for site assignment for the location and content server also location server.
For example


Primary server =PRISRV=PRI
Secondary server -1 = SECSRV1=XYZ
Secondary server -2 =SECSRV2=ABC

Boundary one = x.x.x.0
Boundary two =x.x.1.0
Boundary three =x.x.2.0
Boundary four =x.x.3.0

Boundary Group
Boundary one and two for Site XYZ & content location SECSRV1 - connected at location one
Boundary three and four for site ABC & Content location SECSRV2 - connected at location two

Both location connected with MPLS

There is AD site which has the sub net x.x.0.0 (All above sub nets comes with in this sub net, but not in same location)

Some clients get authenticated at AD site where sub net configured as x.x.0.0 and belongs to the same sub net (if you see above - no boundary created as x.x.0.0 in the sccm). hence client will not assigned to the site

Let us say
I configure x.x.0.0 to any of the site - then client which belongs to that sub net picks the content from any of the DPs because all these DPs are in the same sub nets and which will load the MPLS

Fallback source is not enabled in my infrastructure

Hi,

Subnetting in SCCM is notoriously fraught for not behaving how you expect because it only calculates the subnet once. Search "subnets are evil" for more info from Garth Jones a top MVP.

I would seriously consider switching to IP ranges instead given the problems you are seeing. Subnets can be used, but just with great care and in specific environments. It sounds to me like your environment may be happier with IP ranges.

Mike

I read that configuring IP Range boundary will increase the load on Database server and reduce the database performance, Is this true?