Jump to content


  • 0
mkhan

SCCM 2012 Boundaries configuration questions

Question

I have asked the same questions in TechNet fourm but I am still waiting for the right answer. I wil be glad if you can help me. I am following up steps in http://www.windows-noob.com/forums/index.php?/topic/4045-system-center-2012-configuration-manager-guides/ to install standalone primary server in my small production environment. I stuck in creating boundaries section.

 

I am in the process of standalone SCCM setup and configuration but I stuck on setting up Boundaries and Boundary groups

I have I have four AD sites and only in one site, I have future plan to place a distribution point but at this moment, I wish to manage all clients from the primary site.

On site A: Primary standalone SCCM; 70 Server + 250 clients

Site B: 5 Servers + 50 clients;

Site C: 3 Servers + 15 clients;

Site D: 3 Servers + 5 Clients;

 

These are linked through the high speed WAN link.

Only one site B, I have future plan to include a DP

 

 

Boundaries in SCCM

Boundary Type Description Group count

10.1.0.1-10.1.31.254 Ip address range domain.local/B/10.1.0.0/19 0

10.1.128.1-10.1.159.254 Ip address range domain.local/C/10.1.128.0/19 0

10.1.2.1-10.1.2.254 Ip address range domain.local/c/10.1.2.0/24 0

10.1.3.1-10.1.3.254 Ip address range domain.local/B/10.1.3.0/24 0

10.1.32.1-10.1.63.254 Ip address range domain.local/A/10.1.32.0/19 0

10.1.4.1-10.1.4.254 IP address range doamin.local/D/10.1.4.0/24 0

10.1.50.1-10.1.50.254 IP address range domain.local/A/10.1.50.0/24 0

10.1.55.1-10.1.55.254 IP address range domain.local/A/10.1.55.0/24 0

10.1.56.1-10.1.56.254 IP address range domain.local/A/10.1.56.0/24 0

10.1.57.1-10.1.57.254 IP address range domain.local/A/10.1.57.0/24 0

10.1.64.1-10.1.95.254 IP address range Domain.local/D/10.1.64.0/19 0

D Active Directory site Domain.local/D 0

C Active Directory Site Domain.local/C 0

B Active Directory Site Domain.local/B 0

A Active Directoyr Site Domain.local/A 0

 

So, my 4 boundariy groups should be

Boundary Group 1 for A: domain.local/A/10.1.32.0/19

Boundary Group 2 for B: domain.local/B/10.1.0.0/19

Boundary Group 3 for C: domain.local/C/10.1.128.0/19

Boundary Group 4 for D: Domain.local/D/10.1.64.0/19

 

Are these correct? or Please suggest, what should by my best approach to create your boundary groups

 

Thanks in advance

Share this post


Link to post
Share on other sites

3 answers to this question

Recommended Posts

  • 0
Only one site B, I have future plan to include a DP

 

Well sites C & D collections will have to be configured to be part of site A DPG(distribution point group) as they will have no DP available to service clients on these sites so they will be serviced via DP Site A across the WAN links. I gather you have a star topology WAN and not MESH?

 

You will have already have 4 boundaries showing up in your Boundary node.

Create 1 boundary group to start with as you only have 1 DP at present and add your DP(site server DP to this)in the references tab and add your 4 Bounadries to it in the general tab.

 

Be much easier now for you to create your second DP at site B instead of having to alter the boundary configuration later on!!

 

Rocket Man

Share this post


Link to post
Share on other sites

  • 0

If I understood you correctly, I have to created on Boundary group with the following

 

 

Name: Primary Boundary Group)

 

Member of this Boundary group a. 10.1.32.1.-10.1.63.254 domain.local/A/10.1.32.0./19

b. 10.1.0.1-10.1.1.31.254 domain.local/B/10.1.0.0/19

c. 10.1.128.1-10.1.159.254 domain.local/C/10.1.128.0/19

d. 10.1.65.1-10.1.95.254 domain.local/D/10.1.64.0/19

On the References tab current DP on site A \\SCCMserver.domain.local

And I don't need to alter or change anything on my primary server's boundary configuration, when in future i will add more DPs on site B or other sites?

Are these correct?

Share this post


Link to post
Share on other sites

  • 0

Yes you will.

You will have to add an other Boundary group with your new siteB DP in it and add your Site B boundary IP subnet to it and remove this from the current Boundary set up!!

This will service only systems at siteB thus the reason as why only siteB subnet Boundary + DP will be associated with it!!

 

The current setup that you have will then service SiteA,SiteC and SiteD considering it is a star Topology WAN infrastructure you have?

 

Probably better to create your second DP at Site B now, will save any alterations later to the boundaries. It may have problems or may not, I never had to change boundaries yet, but I'm sure it would be OK.

 

 

EDIT: Do not forget to add your site specific collections to your Distribution point groups. You will have 2 DPGs' when ever you have your second DP created.

 

This is all from a personal view and my own experience with my own SCCM implementations I have done to date. I am no way an expert at this but may I add I have one SCCM setup with 20 DPs, 20 Boundaries and 20 DPGs and have no problems with systems getting software from the appropriate DP assigned.

 

You will know if your Boundaries are correct when you go to change them when you create your second DP. The systems at this AD site will lose their site code if it is not correct, if you do set it up correctly then they will keep their site code(this is one way of knowing that your boundaries are setup correctly, and the systems do not need to have the client installed for the site code to to be assigned initially).

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.