locked
System Center Migration from 2012 R2 to 1702 RRS feed

  • Question

  • We have CAS and 7 Primary sites in existing SCCM 2012 R2 environment which needs to be migrated using side by side migration to SCCM 1702.

    Query is if CAS content is sufficient in the course of migrating all Primary site or do we need to have content from Primary sites servers as well.

    Wednesday, May 10, 2017 4:16 PM

All replies

  • Primary sites contain no unique configuration data that needs to be migrated; i.e., all migrate-able data in already on the CAS.

    Is there a reason that you are migrating instead of just upgrading in-place?

    Is there a reason you aren't just migrating to a single primary site?


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Wednesday, May 10, 2017 5:27 PM
  • Thank you for the update the reason for the migration is as the existing environment running with SCCM 2012 R2, which is not compatible for in-place upgrade unless it is upgraded to SP1.
    Thursday, May 11, 2017 12:53 PM
  • That's not correct (see https://docs.microsoft.com/en-us/sccm/core/servers/deploy/install/upgrade-to-configuration-manager).

    Even if it were though, why wouldn't you simply upgrade to SP1 instead of incurring the pain of a migration?

    Unless of course you were getting rid of the CAS which you should strongly consider (unless you have more than 150,000 managed systems which is the only reason you should have a CAS and multiple primary sites in the first place).


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Thursday, May 11, 2017 3:11 PM
  • Hi Jason and all,

    Thank you for the post. We are in the same situation. We want to migrate our current environment: CAS with 2 PS SCCM2012R2 SP1 (have about 60,000 clients) to One single PS with either 1607 or 1702. What are the considerations that we need to pay attention to during the migration? We have built our new SCCM Server with 1607. Do we have to stop all the services during the migration? Can we do in-place migration meaning running both old and new SCCM servers during operation? Thank you for all your help in advance!

    Tuesday, July 25, 2017 12:24 AM
  • But why? As Jason said, you don't need to migrate to get to 1607 - just upgrade the existing CAS to SP1, then upgrade to 1607.. it's far easier and would only take about 2 hours
    Tuesday, July 25, 2017 1:53 AM
  • First note that 1607 is a version of Windows not ConfigMgr. 

    Getting rid of the CAS is a totally legitimate reason to perform a migration.

    > "meaning running both old and new SCCM servers during operation?"

    There's no other way to perform a migration. Migration literally copies objects from one online hierarchy to another.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Tuesday, July 25, 2017 2:51 AM