locked
Advice required: Side-by-side migration from SCCM 2007 to SCCM 2012 - How to configure overlapping site assignment boundaries RRS feed

  • Question

  • Hi all,

    I have an SCCM2007 environment which uses AD site boundaries for client site assignment (sitecode C01).

    (2 AD sites, each AD site has a single subnet)

    I have installed a SCCM2012 environment (sitecode X01) alongside SCCM2007.

    The intention is for the SCCM2012 environment to be "green fields" - i.e. nothing is to be brought over from SCCM2007.

    SCCM 2007 should continue to function and server SCCM2007 client needs until they have been migrated to SCCM2012.

    I need some advice on how to configure the SCCM2012 boundaries so that they do not interfere with SCCM2007/SCCM2007 clients


    I have read the following articles on SCCM 2012 boundaries:

    http://technet.microsoft.com/en-us/library/gg712679.aspx

    http://technet.microsoft.com/en-us/library/hh427326.aspx

    http://www.petervanderwoude.nl/post/overlapping-boundaries-and-configmgr-2012/

    .

    And also I have read and heard multiple times on these forums/interweb: "DO NOT USE OVERLAPPING BOUNDARIES FOR SITE ASSIGNMENT"

    My question is - how can overlapping boundaries be avoided when migrating in the way I am proposing?

    Is the following possible?


    1) Stop SCCM automatic client push from SCCM2007 site

    2) Leave SCCM2007 boundaries as-is

    3) Configure SCM2012 boundaries to use same AD boundaries as SCCM 2007 (I know "Don't do it"! - I just want to know the effect of doing this)

    4) Configure SCCM2012 system discovery to point to the same AD OU's  as SCCM 2007 system discovery

    5) Configure SCCM2012 client deploymen to use the following properties (using SMSSITECODE=X01 RESETKEYINFORMATION=TRUE)

    6) Right-click install SCCM 2012 client on SCCM 2007 once it has been discovered in SCCM 2012

    .

    Would doing the above achieve rhe following:

    1) SCCM2007 clients can be upgraded to SCCM2012 client

    2) The above clients will be assigned to the SCCM2012 site X01

    .

    Apologies for all the questions but I am trying to get my head around how to get this done.

    Thanks!





    Monday, December 10, 2012 11:47 PM

All replies

  • as soon as your 2012 environment is setup with the correct boundaries, I would remove them from the 2007 environment
    Tuesday, December 11, 2012 9:13 AM
  • For step 2, Remove the boundaries. Why keep them?

    For step 3, use IP Ranges. You are begging for trouble with AD Boundaries.


    http://www.enhansoft.com/

    Tuesday, December 11, 2012 1:40 PM
  • Transitioning all current SCCM 2007 clients to SCCM 2012 will be staged.

    (This allows for testing of the SCCM 2012 client upgrade, as well as giving me a chance to build up the rest of the SCCM 2012 configuration since I am going a green-fields implementation (e.g. setup Software Updates, DP's, Asset Intelligence etc)

    During the transition to SCCM 2012 (in stages), I still want the un-transitioned SCCM 2007 clients to be continue to be managed by SCCM 2007.

    If I removed the boundaries in Step 2, then won't all SCCM 2007 clients go into an Unmanaged state?

    (P.S. Please feel free to shoot my theory's down - because I am actually learning a lot by being told why my reasoning makes no sense :) )

    Tuesday, December 11, 2012 9:00 PM
  • <Shot down... >

    Removing the boundaries from CM07 will not stop CM07 clients from being managed. It will only stop new clients from being assigned to the CM07 site and CM07 clients will treat all advertisement if they where on a "slow network", which is not a big deal, if you adverts are setup using best practices.


    http://www.enhansoft.com/

    Tuesday, December 11, 2012 10:15 PM
  • I have migrated a dosen of customers to 2012 by now, at not once had any problem With overlapping boundaries when 2007 and 2012 co-exists during migration. Its designed that way. So I cannot say I agree that 2007 Client might Connect to a 2012 Site, it will simple not allow it because of the Version requirement.

    So I would go Ahead step by step as you listed. Regarding this RESETKEYINFORMATION=TRUE, that is only when a client has the wrong Configuration Manager trusted root key and cannot contact a trusted management point.

    Hope this helps.


    Nicolai

    Monday, December 17, 2012 1:37 PM
  • Site assignment boundaries are not always required, in the migrations I have done I usually don't use them. Here is a blog post with a lot more detail - http://blog.danovich.com.au/2013/06/18/site-assignment-boundaries-are-not-required-in-sccm-2012/

    My Microsoft Core Infrastructure & Systems Management blog - blog.danovich.com.au

    Thursday, June 20, 2013 9:38 AM
  • Site assignment boundaries are not always required, in the migrations I have done I usually don't use them. Here is a blog post with a lot more detail - http://blog.danovich.com.au/2013/06/18/site-assignment-boundaries-are-not-required-in-sccm-2012/


    I don't understand the connection between "no site assignment boundary groups" and the statement "Advertisements for software updates or deployments might need to be configured to support slow network boundaries" in your blog. Fast/slow is determined using boundary groups for content location, not site assignment if I am not mistaken.


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

    Thursday, June 20, 2013 10:14 AM
  • Site assignment boundaries are not always required, in the migrations I have done I usually don't use them. Here is a blog post with a lot more detail - http://blog.danovich.com.au/2013/06/18/site-assignment-boundaries-are-not-required-in-sccm-2012/



    I don't understand the connection between "no site assignment boundary groups" and the statement "Advertisements for software updates or deployments might need to be configured to support slow network boundaries" in your blog. Fast/slow is determined using boundary groups for content location, not site assignment if I am not mistaken.


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

    Torsten, I have removed that bullet point from that post.  I probably didn't explain my point too well - I should have elaborated, but the concept I was getting at was that if a client isn't in a site assignment boundary and isn't in a content boundary, then (same as previous versions of SCCM) it will assume that it is on a slow-boundary.

    My Microsoft Core Infrastructure & Systems Management blog - blog.danovich.com.au

    Sunday, June 23, 2013 5:16 PM