I have existing SMS2003 infrastructure in place. I am building a side-by-side SCCM to replace it. I know boundaries have changed in the new SCCM but I have a short scenario and not sure what/if I am doing something wrong. Shortened for question: 1 - Primary Site 2- Secondary Sites Secondary site IP Subnet is 10.55.10.0 As of now I do NOT have this subnet entered in my Primary boundaries but it is in my secondary site boundaries. 1. Should secondary site boundaries ALSO be in the Primary site boundaries? 2. Secondary site is management point (which does show for those clients when viewing the collection) BUT the client doesn't seem to install to secondary site machines. 3. Dodiscoveries configured on secondary sites work separately from the discoveries on the Primary site, in other words do i exclude the secondary site subnet boundary from the discovery subnet listing on the Primary site discovery settings? 4. Do the client installation methods setup for secondary sites work independently from the Primary site (Push, etc)? Curious if the secondary site's server will push the client to the remote sites computers on discovery even when the primary has no boundaries or discoveries configured for the secondary sites subnet? Hope this makes sense. I am trying to get one secondary site up and working correctly before making major changes to my entire infrastructure. I will have approximately 15 secondary sites and only 1 Primary site. Thanks, Jeff

Hi Jeff, No, you should never manually add secondary site boundaries to the parent site as boundaries. They will appear in the Configuration Manager Console in Boundaries, as owned by the secondary site. For #2, I'm not quite sure what you are asking. However, if it is where clients get installed from, they install from the management point at the site that initiated the installation. So if you are using Client Push, and the Client Push Installation Wizard, the installation is initiated from the primary site, so the client installs from the secondary site. For discovery, that's up to you. Unless you want to use the automated client push process from the secondary site, not really sure that you need to do the discovery (at least AD System Discovery) from the secondary site. Some methods, such as AD System Group Discovery only run at primary sites. If you do want to do the discovery from the secondary site, then I'd have separate discovery paths configured between the two sites. If you have the same paths, both sites can discover the same resources (which is fine), but you'll process twice the DDRs. Automated client push only pushes to clients that are assigned to the local site. But you could configure client push for the secondary site also, then do the AD System Discovery at the secondary site. Resources assigned to the secondary site (based on its boundaries) would be pushed from the secondary site. Hope that helps, Wally

Hey guys, I know this is an old thread, but I was hoping for a clarification on point #1. when deploying a secondary site to a location that is already specified as a boundary in the primary site, shoule the boundary be removed from the primary site and added to the secondary site, or just left in the primary site and not added to the secondary site at all. In my situation, we have a primary site in Kansas City with all of our locations listed as boundaries from the AD. One of those sites is Chicago. We just upgraded to a secondary site in Chicago and my first thought was to add the CHI boundary to the new secondary server and leave it as a boundary for the primary server as well. After reading this thread I got a bit confused. what is the proper way to handle this? Much thanks! Carl...

You would want the boundary added to the Configuration Manager site that the boundary really belongs to. So, if I'm reading what you are stating properly, you would remove the Chicago boundary from the primary site and add it as a boundary to the secondary site. You never want a single boundary added to multiple sites.

That's exactly what I was asking. Thanks for the follow-up, Wally. Carl...

Let me 2nd that motion. Thanks CD and Wally, that helped me too.

What if the boundary in question has clients from both domains/sites in the same subnet? "Its not optimum but it happens" As I do in one of my labs.tconners

I have an additional question, I need to assign a single IP Address as a boundary. At the moment I'm using the IP Address Range option and just configuring that 1 ip address. Would this be a problem or am I going about it the wrong way. Explaination as to why I need to do this is, to cut a long story short, we have multiple Primary Site Servers on the same subnet but they manage Secondary Sites in the regions.

Hello - This is possible and I know the clients using this type of boundary to meet their goals. However, my personal view is that if you have lot of boundaries like this then it would be difficult to manage and easy to get boundary overlapping issue. Anoop C Nair

Thanks An00p, we'll only have about 7 of these Boundaries max.