Boundary groups automatically created - 2 SCCMs on same subnet

[Jaekt]

Hi,

I have 1 site thats running SCCM 2007 with IP ranged boundaries and a site with SCCM 2012 running on same IP ranged boundaries.

The problem is that the SCCM 2012 site automatically creates boundary groups and boundaries of the old SCCM, pointing the clients to the wrong distribution points.

 

Is there any fix for this, to avoid clients being pointed to the wrong DPs.

 

I have tried setting deny read in AD, on the System Management container, for both SCCM server objects, but they are still created.

[Jorgen Nilsson]

Hi,

In a mixed environment between SCCM 2007 and 2012 you should only used Boundary groups in SCCM 2012 configured for "Content Location" these boundaries are nog overlapping and cannot be read by the SCCM 2007 client.

Make sure that you don't use an boundary groups with the setting "Use this boundary group for site assignment.", these boundary groups can conflict with a boundary in SCCM 2007.

A boundary in SCCM 2012 is not published anyware, and is not really used or published until it is added to a boundary group.

Regards,
Jörgen

[Jaekt]

Hi Jörgen, thanks for the reply.

The SCCM 2012 Boundary Groups are not configured for Automatic Site Assignment.

I did however find the reason.

There was a migration configured earlier, where it was set to share DPs from old SCCM.

By going to Administration -> Migration -> Source Hierarchy -> Rightclick old site (sccm 07 site) -> Configure -> Deselect "Enable distribution-point sharing for this source site".

 

Dunno why it was set to share DPs, but its fixed now

 

Thanks again!