locked
SCCM 2012 Migration Overlapping Boundaries RRS feed

  • Question

  • Hi

    I have been tasked with migrating an environment with over 350 Subnets from SCCM 2007 to SCCM 2012 - each subnet is a boundary in SCCM 2007. I have a concern with overlapping boundaries from a client assignment perspective.

    Looking at solutions etc .. to this and the client only wants to migrate a number of machines at a time (i.e. all machines in a subnet will not be migrated at same time)

    Would the following work:

    • Disable Auto Assignment in the SCCM 2007 environment and configure client push in 2007 with the designated SCCM 2007 site code.
    • Migrate the Subnets into the SCCM 2012 Environment and deploy the client via client push or WSUS/Group Policy with the designated SCCM 2012 site code specified
    • Would this result in clients in SCCM 2007 still being assigned to the SCCM 2007 hierarchy with the ability to still maintain core SCCM 2007 functionality - while device in SCCM 2012 will still remain in the SCCM 2012 hierarchy and maintain core SCCM 2012 functionality.

    Also what would be the impact of disabling auto client assignment in SCCM 2007

    Any assistence would be apprecaited

    Raymond


    RDunne76


    • Edited by Rdunne76 Monday, April 8, 2013 3:33 PM
    Monday, April 8, 2013 3:33 PM

Answers

  • I would not have client push running in both environments simultaneaously!

    if you want to migrate at your own pace, disable it in the 2012 environment also

    your agents which are currently managed by sccm 2007 will stay managed, you can use a controlled method to migrate some of those clients to the 2012 environment

    • Marked as answer by Rdunne76 Tuesday, April 9, 2013 11:40 AM
    Monday, April 8, 2013 9:51 PM
  • Overlapping Boundaries are supported but for content only not for site assignment. How I would approach this is as follows.

    • Make sure no task sequences, packages or client push in the 2007 site are using SMSSITECODE=AUTO. Hard code the site Code.
    • Disable client push on the 2012 site for duratrion of the migration (Assuming you aren't deploying any clients natively in the site during the migration)
    • Create a package on the 2007 site for the 2012 client
    • Create a Migration collection on the 2007 site
    • Create a mandatory advertisement for the 2012 client package targeted at the Migration collection

    To migrate a group of clients create a suitable Boundary on the 2012 site and then on the 2007 site add the clients via a suitable query to the Migration collection.

    Post Migration clean up the 2012 boundaries so they're in the most efficient layout for your Hierarchy.


    • Edited by Philaitman Tuesday, April 9, 2013 9:05 AM
    • Marked as answer by Rdunne76 Tuesday, April 9, 2013 11:40 AM
    Tuesday, April 9, 2013 9:04 AM
  • If you don't want to keep any historical data for clients which have successfully migrated then yes of course you can delete the record from the 2007 site. However this isn't a requirement as the 2012 client will never talk to the 2007 site due to the different site code and version requirements.

    My preference is to keep the record until finished so I can run counts to make sure the expected numbers of clients migrated match. I've not had any issues in doing it this way.

    • Marked as answer by Rdunne76 Tuesday, April 9, 2013 10:24 PM
    Tuesday, April 9, 2013 11:46 AM

All replies

  • I would not have client push running in both environments simultaneaously!

    if you want to migrate at your own pace, disable it in the 2012 environment also

    your agents which are currently managed by sccm 2007 will stay managed, you can use a controlled method to migrate some of those clients to the 2012 environment

    • Marked as answer by Rdunne76 Tuesday, April 9, 2013 11:40 AM
    Monday, April 8, 2013 9:51 PM
  • Overlapping Boundaries are supported but for content only not for site assignment. How I would approach this is as follows.

    • Make sure no task sequences, packages or client push in the 2007 site are using SMSSITECODE=AUTO. Hard code the site Code.
    • Disable client push on the 2012 site for duratrion of the migration (Assuming you aren't deploying any clients natively in the site during the migration)
    • Create a package on the 2007 site for the 2012 client
    • Create a Migration collection on the 2007 site
    • Create a mandatory advertisement for the 2012 client package targeted at the Migration collection

    To migrate a group of clients create a suitable Boundary on the 2012 site and then on the 2007 site add the clients via a suitable query to the Migration collection.

    Post Migration clean up the 2012 boundaries so they're in the most efficient layout for your Hierarchy.


    • Edited by Philaitman Tuesday, April 9, 2013 9:05 AM
    • Marked as answer by Rdunne76 Tuesday, April 9, 2013 11:40 AM
    Tuesday, April 9, 2013 9:04 AM
  • Grundlichkeit and Philaitman,

    Many thanks for you assistence - Philaitman - I'd image I will need to delete record from SCCM 2007 - I cangive your suggestion a try and see how it goes

    I'll disable client push on both sites and will work out a process  


    RDunne76

    Tuesday, April 9, 2013 11:40 AM
  • If you don't want to keep any historical data for clients which have successfully migrated then yes of course you can delete the record from the 2007 site. However this isn't a requirement as the 2012 client will never talk to the 2007 site due to the different site code and version requirements.

    My preference is to keep the record until finished so I can run counts to make sure the expected numbers of clients migrated match. I've not had any issues in doing it this way.

    • Marked as answer by Rdunne76 Tuesday, April 9, 2013 10:24 PM
    Tuesday, April 9, 2013 11:46 AM
  • Many Thannks for you answer

    RDunne76

    Tuesday, April 9, 2013 10:24 PM