locked
Migrating boundaries from Configuration Manager 2007 to Configuration Manager 2012 RRS feed

  • Question

  • I am confused with the migration process with boundaries from Configuration Manager 2007 to 2012.  I want to rollout the Configuration Manager 2012 client slowly where I move over test groups, then departments.  I want to avoid moving over our servers that are clients at this time and keep them on the 2007 site until we are ready to move them.  Our setup is one site server for 2007, AD Schema for 2007 extended, we use system discovery.  System discovery and boundaries are not setup in Configuration Manager 2012.

    If I migrate over the 2007 boundaries, will the 2007 clients be ready for individual client push to where we can see the 2007 clients in 2012 console? Can we then push the client to them?  Will the 2007 site continue to work without issue if the boundary is migrated over to 2012? 

    We need to use both site servers unitl all 2007 clients are moved over to 2012.  So far I have done the data gathering process and plan on migrating over our test machine collection.

    Thanks,

    Brit

    Monday, August 20, 2012 7:38 PM

Answers

  • Your going to want try to not have overlapping boundries between the 07 and 12 site this can mess up automatic client assignment (Client Push). So once you migrade the boundries your going to want to make sure the same boundry isn't setup in the 07 site. Once the boundry is setup in the 12 site and you run discovery the clients in that boundry should get assigned the 2012 site code and you can begin pushing the client. The 2007 clients can still function in the 2007 site even if their boundry is removed. Here's a pretty good reference that should help you: http://technet.microsoft.com/en-us/library/gg712679.aspx & http://www.petervanderwoude.nl/post/overlapping-boundaries-and-configmgr-2012/


    Justin | http://patchmypc.net | Please remember to mark this answer as helpful/answer if it helped you



    • Edited by Justin Chalfant Monday, August 20, 2012 8:03 PM
    • Marked as answer by Brit2008 Monday, August 20, 2012 8:37 PM
    Monday, August 20, 2012 8:02 PM
  • A very important thing to point out is that boundaries are only used for two things: auto-client assignment and content location. That's it. You do *not* need boundaries for ConfigMgr to work properly.  

    Clients only auto-assign during installation (if you let them) so unless you are deploying more clients in your 2007 environment, then you don't need the boundaries for that. On the 2012 side, if you are using manual client push or another method, auto-assignment isn't used; however, auto-client push won't push to clients unless they are assigned to the site already during the discovery process.

    For content location on the 2007 side, all DPs will be treated as remote and follow the normal rules of content location from there: http://technet.microsoft.com/en-us/library/bb932150.aspx .

    Thus, the usual way of migrating is to deploy the 2012 server hierarchy, migrate everything, delete the boundaries from 2007, and then deploy the 2012 client to the managed systems.


    Jason | http://blog.configmgrftw.com

    • Marked as answer by Brit2008 Monday, August 20, 2012 8:37 PM
    Monday, August 20, 2012 8:31 PM

All replies

  • Your going to want try to not have overlapping boundries between the 07 and 12 site this can mess up automatic client assignment (Client Push). So once you migrade the boundries your going to want to make sure the same boundry isn't setup in the 07 site. Once the boundry is setup in the 12 site and you run discovery the clients in that boundry should get assigned the 2012 site code and you can begin pushing the client. The 2007 clients can still function in the 2007 site even if their boundry is removed. Here's a pretty good reference that should help you: http://technet.microsoft.com/en-us/library/gg712679.aspx & http://www.petervanderwoude.nl/post/overlapping-boundaries-and-configmgr-2012/


    Justin | http://patchmypc.net | Please remember to mark this answer as helpful/answer if it helped you



    • Edited by Justin Chalfant Monday, August 20, 2012 8:03 PM
    • Marked as answer by Brit2008 Monday, August 20, 2012 8:37 PM
    Monday, August 20, 2012 8:02 PM
  • A very important thing to point out is that boundaries are only used for two things: auto-client assignment and content location. That's it. You do *not* need boundaries for ConfigMgr to work properly.  

    Clients only auto-assign during installation (if you let them) so unless you are deploying more clients in your 2007 environment, then you don't need the boundaries for that. On the 2012 side, if you are using manual client push or another method, auto-assignment isn't used; however, auto-client push won't push to clients unless they are assigned to the site already during the discovery process.

    For content location on the 2007 side, all DPs will be treated as remote and follow the normal rules of content location from there: http://technet.microsoft.com/en-us/library/bb932150.aspx .

    Thus, the usual way of migrating is to deploy the 2012 server hierarchy, migrate everything, delete the boundaries from 2007, and then deploy the 2012 client to the managed systems.


    Jason | http://blog.configmgrftw.com

    • Marked as answer by Brit2008 Monday, August 20, 2012 8:37 PM
    Monday, August 20, 2012 8:31 PM
  • Thanks to you both for the information. I am making this harder than it needs to be. 
    Monday, August 20, 2012 8:38 PM