locked
Migration From SCCM 2012 SP1 stand alone primary to SCCM 2012 SP1 Child-Primary RRS feed

  • Question

  • Here's my issue...<o:p></o:p>

    I have a SCCM 2012 SP1 (CU2 - Stand Alone Primary) server that I want to migrate
    contents and object to a new SCCM 2012 SP1 (CU2 - Child Primary) server. 
    The Stand-Alone Primary is in need of a complete rebuild, and I am not able to
    do a direct join to mu CAS topped new hierarchy.<o:p></o:p>

    The initial migration configuration is not posting any errors - there is clear and unfettered communication between the two systems.<o:p></o:p>

    In creating the Migration job, I am pulling objects from the Stand Alone Primary to the
    Child-Primary server.  There is no issue reading the various objects from the old server to the new.<o:p></o:p>

    When finishing the creation of the job, the destination is supposed to be the
    replacement Child-Primary server.  The Child-Primary is further selected during the creation of the Migration job itself.  Yet now, when the Migration job runs, the job status reads that the migration target (Where the objects are being migrated to) is the CAS server.  This is a consistent behavior from the new Child-Primary server, and as of yet - regardless of the destination that is selected, after the job is created, the destination reverts to the CAS server.<o:p></o:p>

    <o:p> </o:p>

    Ideas?<o:p></o:p>


    Wednesday, October 23, 2013 4:29 PM

Answers

  • Operations for migration are run at the top-level site in the destination hierarchy. If you configure migration when you use a Configuration Manager console that is connected to a primary child site, you must allow time for the configuration to replicate to the central administration site, to start, and to then replicate status back to the primary site to which you are connected.

    More Information: http://technet.microsoft.com/en-us/library/gg712307.aspx

    Ronni Pedersen | Microsoft MVP - ConfigMgr | Blogs: www.ronnipedersen.com/ and www.SCUG.dk/ | Twitter @ronnipedersen

    • Marked as answer by Joyce L Saturday, November 2, 2013 5:56 AM
    Wednesday, October 23, 2013 5:47 PM
  • When finishing the creation of the job, the destination is supposed to be the

    replacement Child-Primary server.

    No, that's incorrect. Primary sites in 2012 do not own any configuration data -- it's all considered global data and replicated to every primary site and the CAS and so it doesn't make sense to try to target a primary site individually. Thus, as Ronni pointed out, the CAS is the proper target which represents the entire hierarchy and is the gateway to the hierarchy for migrations.

    The only data that primary sites "own" is client data and this is not migrated in any way.

    Why do you feel you need a CAS now?


    Jason | http://blog.configmgrftw.com

    • Marked as answer by Joyce L Saturday, November 2, 2013 5:56 AM
    Wednesday, October 23, 2013 6:50 PM

All replies

  • Operations for migration are run at the top-level site in the destination hierarchy. If you configure migration when you use a Configuration Manager console that is connected to a primary child site, you must allow time for the configuration to replicate to the central administration site, to start, and to then replicate status back to the primary site to which you are connected.

    More Information: http://technet.microsoft.com/en-us/library/gg712307.aspx

    Ronni Pedersen | Microsoft MVP - ConfigMgr | Blogs: www.ronnipedersen.com/ and www.SCUG.dk/ | Twitter @ronnipedersen

    • Marked as answer by Joyce L Saturday, November 2, 2013 5:56 AM
    Wednesday, October 23, 2013 5:47 PM
  • When finishing the creation of the job, the destination is supposed to be the

    replacement Child-Primary server.

    No, that's incorrect. Primary sites in 2012 do not own any configuration data -- it's all considered global data and replicated to every primary site and the CAS and so it doesn't make sense to try to target a primary site individually. Thus, as Ronni pointed out, the CAS is the proper target which represents the entire hierarchy and is the gateway to the hierarchy for migrations.

    The only data that primary sites "own" is client data and this is not migrated in any way.

    Why do you feel you need a CAS now?


    Jason | http://blog.configmgrftw.com

    • Marked as answer by Joyce L Saturday, November 2, 2013 5:56 AM
    Wednesday, October 23, 2013 6:50 PM