Boundary design headaches. Multiple Preferred.

[omniblue]

Currently we use AD Sites and Services for Content Boundaries. My organization's immediate problem is we have rather large sites that at the time did meet the requirements for SCCM deployment, but due to issues raised post deployment a revise warranted.

 

The problem we are facing is preferred distribution points where Clients will have more then one Preferred DP due to matching multiple boundaries, overlap. The current implementation is having a single DP associated with each Office Building, A single AD Site covering an entire office building is used. The associated subnet with that site is (10.10.0.0/16). No problems. Post deployment I am tasked with setting up DPs for certain ITOfficeRooms (think IT imaging stations) that would only be configured for a single subnet 10.10.10.0/24 boundary. This ITOfficeRoom DP could not be used for ANYTHING else besides the 10.10.10.0/24 subnet. For the 10.10.10.0/24 range, no content should be received the 10.10.0.0/16 (OfficeBuilding) DP as preferred, fallback is allowed/necessary.

 

If I simply added a subnet content boundary 10.10.10.0/24 and added the ITOfficeRooms DP to that Boundary, any clients in the 10.10.10.0/24 would have two Preferred DPs. ITOfficeRooms DPs from 10.10.10.0/24 and the OfficeBuilding DP from the AD Site and Services associated with the 10.10.0.0/16 subnet. With two preferred subnets the clients receive their content from either at random, design bust. THe whole purpose of the additional DP is to speed up content delivery. Solving this problem is proving more difficult. Powers that be do not want to stop using AD Sites and Services for the 10.10.0.0/16 range.

 

One option that came to mind was creating another AD Site for each ITOfficeRoom, but this will only work if SCCM treats AD Sites and Services the same exact way AD Sites and Services handles subnets with Domain Controllers assignment. This being the most defined subnet takes precedence. For example:

 

Two configured boundaries and their associated DPs:

• "OfficeBuilding" Content Boundary is associated with AD Site "OfficeBuilding". This AD Site is configured with a 10.10.0.0/16 subnet, This Content boundary is assigned the DP, SCCMDP01.
• "ITOfficeRoom" Content Boundary is associated with AD Site "ITOfficeRoom". This AD Site is configured with a 10.10.10.0/24 subnet, This Content boundary is assigned the DP, SCCMDP02.

Would a client with the IP address of 10.10.10.100 only receive SCCMDP02 as a preferred distribution point? Much like how AD Sites and Services would handle domain controller assignment? My concern is the link to AD Sites and Services is really just pulling the subnets and using them much like creating the same subnet boundaries in SCCM itself, where the client would then receive both as preferred.