locked
Migration of Configuration Mgr 2012 SP1 to Configuration Mgr 1511 RRS feed

  • Question

  • We are working on restructuring our Configuration Manager hierarchy. Currently we have 2 separate primary sites both with little quirks which is why I am opting for a rebuild and migration.  My original plan was to build out a new 2012 R2 SP1 primary and migrate the other two into that.  However, now that SCCM 1511 is out I would like to build out that and migrate to that build.  What are the supported migrations for 1511?  I found documentation on going between 2012 sites (https://technet.microsoft.com/en-us/library/gg712313.aspx?f=255&MSPPError=-2147217396#BKMK_SupportedMigrationVersions) but unable to find a similar table for 1511.

    Our current primaries are 2012 SP1.

    Monday, January 4, 2016 11:45 PM

Answers

  • You should also be able to create migration jobs on a 1511 site that gather data from 2012 sites.

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

    • Proposed as answer by Frank Dong Saturday, January 16, 2016 6:27 AM
    • Marked as answer by Frank Dong Monday, January 25, 2016 7:09 AM
    Tuesday, January 5, 2016 7:20 AM

All replies

  • Dear Sir,

    It's supported to upgrade directly (in-place) from 2012 SP1 to ConfigMgr 1511. More information you can check below reference:

    http://www.scconfigmgr.com/2015/12/04/upgrade-to-configmgr-1511-in-your-hierarchy/

    https://www.systemcenterdudes.com/sccm-1511-upgrade/

    Best regards

    Frank


    • Edited by Frank Dong Tuesday, January 5, 2016 3:28 AM
    Tuesday, January 5, 2016 1:38 AM
  • You should also be able to create migration jobs on a 1511 site that gather data from 2012 sites.

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

    • Proposed as answer by Frank Dong Saturday, January 16, 2016 6:27 AM
    • Marked as answer by Frank Dong Monday, January 25, 2016 7:09 AM
    Tuesday, January 5, 2016 7:20 AM
  • I had an idea today on my way to work. I will do the new build with 1511.  If I cannot gather data from the old primaries I will upgrade the preexisting to at least SP2 to see if that works.
    Tuesday, January 5, 2016 4:48 PM
  • Hi Nick,

    your Idea is good, upgrade your site to SCCM 2012 SP2, enable R2 features and then CU1

    As per Torsten reply, create the migration jobs.


    Kannan.CS | http://kannancs.wix.com/blog | Please remember to click “Mark as Answer” on the post that helps you. This can be beneficial to other community members reading the thread.

    Tuesday, January 5, 2016 6:16 PM
  • From : https://technet.microsoft.com/en-us/library/mt593351.aspx

    You can migrate data from a source hierarchy that runs any of the following versions of Configuration Manager:

    •  Configuration Manager 2007 SP2 (For the purpose of migration, Configuration Manager 2007 R2 or R3 on the source site are not a consideration. So long as the source site runs SP2, sites with either the R2 or R3 add-on installed are supported for migration to System Center Configuration Manager)

    • System Center 2012 Configuration Manager SP2 or System Center 2012 R2 Configuration Manager SP1

    We also documented the process on our blog :

    https://www.systemcenterdudes.com/sccm-1511-migration/


    Benoit Lecours | Blog: System Center Dudes

    Tuesday, January 5, 2016 6:26 PM
  • I have followed the migration guide put out by https://www.systemcenterdudes.com/ and am 99% of the way there with all services working with exception to getting the actual content library source moved in my side-by-side migration project.  How can I get my source moved so that I can kill off the old SCCM server?  Am I missing something?  Were the migration jobs supposed to be able to actually move the source files as well as the database entries for drivers, apps, packages, ts...?

    I did not want to take the risk upgrading my production SCCM server to 1511 and sql 2014, potentially breaking my environment, and spending weeks fixing things so I took the side-by-side route. 

    Thursday, February 4, 2016 4:31 PM
  • Not that it helps now, but this is one of the reasons a backup and restore works so much better for this scenario. Upgrade then Backup and restore works quite well and is much smoother. Too late now though.

    No, ConfigMgr does not touch source files (and shouldn't because it doesn't own them). You need to move those manually and then update the locations manually also. Nickolaj has a very nice tool to help you do the later at https://gallery.technet.microsoft.com/ConfigMgr-Content-Source-ac490b67


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

    Friday, February 5, 2016 8:37 PM