locked
Migrating SCCM 2012 to SCCM 2016 RRS feed

  • Question

  • Hi All,

    We are planning to upgrade System Center Configuration Manager 2012 R2 SP1 to 2016

    Could you please share your suggestion and Risks involved before we start the Migration.

    Thanks,
    Raghu

    Friday, November 4, 2016 1:24 PM

Answers

  • Which is it? The title says "migrating" while your question says "upgrade". Are you migrating to SCCM 1606 or upgrading the current 2012 R2 SP1?

    In all cases, there are plenty of guides out there for both.

    Upgrade (it's for 1511 but the same process applies): https://www.systemcenterdudes.com/sccm-1511-upgrade/ There are a number of prerequisites mentioned, read them. Other considerations if you are upgrading, make sure to run a test DB upgrade. Also turn off maintenance tasks for the duration of the upgrade and enable them after the upgrade is done. Check all site systems OSes to make sure they are compatible and have the latest KBs installed.

    Make sure AV exclusions are properly in place or turn off active protection for the duration of the upgrade, you won't believe the problems I've seen because of this. If you have custom boot images, manually upgrade them once the process is done. MOST important, have a backup of everything ConfigMgr before you start the process.

    If Migrating (also for 1511 but same applies): https://www.systemcenterdudes.com/sccm-1511-migration/ Take a look at the considerations in it. Turn off as well automatic client push on the source hierarchy before you proceed with this. Decide what you want to migrate over to the new hierarchy, you can also migrate DPs if needed. DPs can be shared for the duration of the migration as well. There are also a number of ways to migrate the clients over (through packages deployment, baselines, etc). Make sure TO NOT use in the new hierarchy any site codes currently being used in the source hierarchy.

    Friday, November 4, 2016 1:44 PM
  • Risk 1: There's no such thing as "SCCM 2016" and never will be. So first, determine what product version you would actually like to get to. The most current version is ConfigMgr Current Branch (CB) 1606 (with 1610 hopefully released in the next month or so).

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

    Friday, November 4, 2016 2:28 PM

All replies

  • Which is it? The title says "migrating" while your question says "upgrade". Are you migrating to SCCM 1606 or upgrading the current 2012 R2 SP1?

    In all cases, there are plenty of guides out there for both.

    Upgrade (it's for 1511 but the same process applies): https://www.systemcenterdudes.com/sccm-1511-upgrade/ There are a number of prerequisites mentioned, read them. Other considerations if you are upgrading, make sure to run a test DB upgrade. Also turn off maintenance tasks for the duration of the upgrade and enable them after the upgrade is done. Check all site systems OSes to make sure they are compatible and have the latest KBs installed.

    Make sure AV exclusions are properly in place or turn off active protection for the duration of the upgrade, you won't believe the problems I've seen because of this. If you have custom boot images, manually upgrade them once the process is done. MOST important, have a backup of everything ConfigMgr before you start the process.

    If Migrating (also for 1511 but same applies): https://www.systemcenterdudes.com/sccm-1511-migration/ Take a look at the considerations in it. Turn off as well automatic client push on the source hierarchy before you proceed with this. Decide what you want to migrate over to the new hierarchy, you can also migrate DPs if needed. DPs can be shared for the duration of the migration as well. There are also a number of ways to migrate the clients over (through packages deployment, baselines, etc). Make sure TO NOT use in the new hierarchy any site codes currently being used in the source hierarchy.

    Friday, November 4, 2016 1:44 PM
  • Risk 1: There's no such thing as "SCCM 2016" and never will be. So first, determine what product version you would actually like to get to. The most current version is ConfigMgr Current Branch (CB) 1606 (with 1610 hopefully released in the next month or so).

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

    Friday, November 4, 2016 2:28 PM

  • Check this : https://blogs.technet.microsoft.com/hybridcloud/2016/10/12/managing-the-software-defined-datacenter-with-system-center-2016/

    ... which does NOT talk about SCCM 2016. It says "Configuration Manager (version 1606)".

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

    Thursday, May 11, 2017 1:50 PM
  • There is such thing as SCCM 2016

    https://www.microsoft.com/en-gb/cloud-platform/system-center-pricing


    • Edited by PJBrandon Thursday, June 15, 2017 1:37 PM
    Thursday, June 15, 2017 1:36 PM
  • No, there's not. That link is for **System Center** 2016, not Configuration Manager 2016 (which does not exist).

    "Configuration Manager Current Branch" is the current product name; ConfigMgr CB is part of System Center 2016 though. Some details at https://blogs.technet.microsoft.com/enterprisemobility/2015/10/27/system-center-configuration-manager-support-for-windows-10-and-microsoft-intune/


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

    Thursday, June 15, 2017 1:49 PM
  • Maybe if they try just a little harder, they can make these product names even more confusing.

    Jordan Cobb

    Monday, August 6, 2018 4:47 PM
  • Maybe. But, honestly, is it really that difficult?

    Jason | https://home.configmgrftw.com | @jasonsandys

    Monday, August 6, 2018 5:32 PM