Hello, We have a single AD site that covers two physical locations. The second physical location connects to the head-office via VPN. The subnet for the second office is part of the head office AD-site. There are no domain controllers in the second site. Can we still add a secondary site in the second site? How can we exclude the second site from the head office SCCM site boundary? Or do we just go with IP subnet based boundaries? Will the second site work without a DC? Thanks, Palwinder Singh

Yes, You can configure as a Secondary site. If i correctly understand the complexity of the boundary... You have AD Site where two IPSubnets are configured (one with local and second one with Remote VPN site) Now how to configure the Boundaries for VPN Site secondary site...if that is your question you can configure the IP Subnet ID of VPN connected site. This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hello, Or do we just go with IP subnet based boundaries? Will the second site work without a DC? Yes SCCM can work with IP Subnet Based Boundaries (Without the DC in that location) also... This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, I always use IP address ranges and I never really on AD sites any more. In many cases you perhaps want to differentiate for instance a wireless network or VPN network and set it to be a slow network but they are in the same AD site. I prefer IP address range instead of IP Subnet as it basically is the same funtionality but IP address range doesn't care about the subnet mask, so you will not have any problems with different subnet masks e.t.c. Regards, Jörgen -- My System Center blog ccmexec.com -- Twitter @ccmexec

Thanks PaddyMaddy and Jörgen! We will go with subnet based boundaries :) Regards,Palwinder Singh

Hi, I always use IP address ranges and I never really on AD sites any more. In many cases you perhaps want to differentiate for instance a wireless network or VPN network and set it to be a slow network but they are in the same AD site. I prefer IP address range instead of IP Subnet as it basically is the same funtionality but IP address range doesn't care about the subnet mask, so you will not have any problems with different subnet masks e.t.c. Regards, Jörgen -- My System Center blog ccmexec.com -- Twitter @ccmexec That makes more sense. I will keep that in mind for deployments with multiple IP ranges or lots of subnets.Palwinder Singh