Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

PENDING Deploying SCCM Secondary Site for remote sites

  • Thread starter Thread starter Joe13
  • Start date Start date
  • Replies Replies 10
  • Views Views 2K

Joe13

Member
Messages
12
Reaction score
0
Points
1
Hi gents,

We have multiple small sites around the country. I need the PCs updated when I do head office. Currently they get SCEP definition updates from HO and it works, but I won't be able to push large files.

My goal is not to install a full secondary site, just a distribution / software update point.

Whenever I configure the boundaries the location log file on remote site PC still shows the HO as DP.
 
I currently have 1 main site of SCCM, 1 default boundary group. If I create a secondary boundary group, should I remove that boundary from the primary boundary group and only add it in the new boundary group, or should it be in both boundary groups?

Also what options should be completed on the References tab.
 

Attachments

  • Untitled picture.png
    Untitled picture.png
    20.1 KB · Views: 1
I know if I create a secondary site it will be available from the drop down, will I select that site there for the secondary boundary group?
 
You can use DP for each site and you need just to configure the boundary groups correctly (for each AD Site or Range IP Address).
 
yeah, definitely you just need DP and like Youssef said create boundaries based on ip range.
 
I currently have 1 main site of SCCM, 1 default boundary group. If I create a secondary boundary group, should I remove that boundary from the primary boundary group and only add it in the new boundary group, or should it be in both boundary groups?

Also what options should be completed on the References tab.
you can have more than 1 DP in a boundary group in case the local DP is not responsive. However, if its a remote site with a slow link, there is really no use of that.
 
you can have more than 1 DP in a boundary group in case the local DP is not responsive. However, if its a remote site with a slow link, there is really no use of that.
So if I create a remote site and setup a DP there I will be wasting my time? They have slow links, I need to get updates to them.
 
sorry, didnt make myself clear. my point was that you can have multiple DPs in one Boundary. What i was trying to say is if you have your primary DP in site A and you include the DP in site B within that boundary; and when the DP in Site A is down, all of your computers in Site A will try to connect to your Site B DP. When that happened, it will severe your WAN link.

So, have two boundaries and for each boundary just add their own respective DP.
 
I eventually got time to work on this again.

I've created a secondary DP - on the boundary group what should I select here? On the site assignment I only have the option to select my Primary site. Should this be ticked and selected?

SCCM.png
 
Here I have my primary boundary group and the one I just created which includes the sites IP range.

Should this site IP range be removed from the primary boundary group?
boundary.png
 
Back
Top