locked
Boundaries RRS feed

  • Question

  • I'm reading through an SCCM 2012 book in preparation of migrating from SCCM 2007 to SCCM 2012 R2.  I have also tested standing up an SCCM 2012 R2 infrastructure in a lab which also has SCCM 2007.  In the book it states that you should use IP ranges to avoid boundary overlaps between the old and new environment.

    Testing in my lab doesn't seem to support this statement.  I can have the same boundaries (and boundary groups) and manually push out the client via the SCCM interface to upgrade clients.  What risk do I run by having boundary overlaps?

    Friday, May 2, 2014 12:24 PM

Answers

  • Overlapping boundaries are not supported and will cause issues if you are talking about boundary groups for site assignment.
    Content location boundary/groups are supported and do not cause any issues.

    Torsten Meringer | http://www.mssccmfaq.de

    • Marked as answer by Juke Chou Wednesday, June 4, 2014 2:30 AM
    Friday, May 2, 2014 12:30 PM

All replies

  • Overlapping boundaries are not supported and will cause issues if you are talking about boundary groups for site assignment.
    Content location boundary/groups are supported and do not cause any issues.

    Torsten Meringer | http://www.mssccmfaq.de

    • Marked as answer by Juke Chou Wednesday, June 4, 2014 2:30 AM
    Friday, May 2, 2014 12:30 PM
  • The problems for overlapping boundaries are mainly with site assignment. To prevent these issue it's the best to avoid them and that can be easily done by using IP ranges (as they are easy to cut in pieces).

    I remember writing a blog about that, maybe it helps understanding: http://www.petervanderwoude.nl/post/overlapping-boundaries-and-configmgr-2012/


    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

    Friday, May 2, 2014 12:33 PM
  • I'm referring to overlapping boundaries as far as having my old boundaries in SCCM 2007 still active as well as in 2012. Not the same boundaries within multiple boundary groups in 2012. I'm using AD sites for my boundaries in SCCM 2007 currently.

    Just to add, we have over 2000 client systems all using DHCP.  Using an IP range wouldn't work for me.  How do you go about disabling automatic site assignment on the 2007 side? What impact is there to the SCCM 2007 site by disabling that?

    • Edited by Frentic Friday, May 2, 2014 1:04 PM
    Friday, May 2, 2014 1:00 PM
  • Did you even read my post? The problem is with the auto assignment of the CM07 clients. Disabling auto assignment solves your problem. Just in case you need to install a new CM07 client, make sure to directly assign them to your site via the installation command line.

    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

    Friday, May 2, 2014 1:12 PM
  • Overlapping is overlapping. Even if you are talking about two environments and AD sites vs IP subnets.
    There's no need for site assignment boundaries at all if there's just a single primary site.

    Torsten Meringer | http://www.mssccmfaq.de

    Friday, May 2, 2014 1:15 PM
  • Did you even read my post? The problem is with the auto assignment of the CM07 clients. Disabling auto assignment solves your problem. Just in case you need to install a new CM07 client, make sure to directly assign them to your site via the installation command line.

    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

    I did read your post, I'm just not entirely clear on how to disable automatic site assignment.  We use the client push method in SCCM 2007 and the installation property configured is SMSSITECODE=LHQ so I'm assuming we're fine by having overlapping boundaries since that isn't configured as =AUTO.
    Friday, May 2, 2014 1:21 PM
  • You should indeed be fine, just keep in mind that it's not an official supported scenario. If you're new environment only has one site, just remove the site assignment from the boundary group(s) and your even working on a supported method.

    As Torsten already stated, overlapping boundaries for content locations are supported.


    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

    Friday, May 2, 2014 1:40 PM
  • You should indeed be fine, just keep in mind that it's not an official supported scenario. If you're new environment only has one site, just remove the site assignment from the boundary group(s) and your even working on a supported method.

    As Torsten already stated, overlapping boundaries for content locations are supported.


    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

    If I remove the site assignment on the 2012 side, they will just automatically discover the 2012 site, correct?  I plan on migrating clients to 2012 via just right-click Install Client.

    Thanks for the info, I appreciate it.


    • Edited by Frentic Friday, May 2, 2014 6:31 PM
    Friday, May 2, 2014 6:27 PM
  • Either do like with your old environment and specify the specific site code, or configure your site also as a fallback site (in the Hierarchy settings).


    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

    Friday, May 2, 2014 7:17 PM
  • There is no need for *automatic* site assignment (therefore for site assignment boundary groups) if there's just a single primary site. You can specify the site that initiates the push (= the site the clients will be assigned to) when running the client push installation wizard.

    Torsten Meringer | http://www.mssccmfaq.de

    Friday, May 2, 2014 7:23 PM