Upgrading and migrating RRS feed

  • Question

  • I have been tasked with doing an upgrade of SCCM 2012 that is installed on Windows 2008 R2. We need to move it to 2016, both the OS and SCCM. Management has told me I will be migrating to a new Hyper-V virtual machine; so I'm trying to come up with some plans. I know I need to move the SQL database off it's "local install" and up into our cluster; I've done this before so that part is documented already.  I've been reading over this documentation but this is for an existing install on the same server. We cannot just upgrade the existing server to SCCM 2016 since it's on a 2008 VM.

    So, the questions are:

    1. Should I install SCCM 2012, patch it up, transfer the site over, etc? I can't seem to find any documentation (from an "official MS site") on this.
    2. Do I set up a secondary SCCM 2016 in the same site hierarchy, connect the two, transfer all the roles over from 2012 to 2016, and then remove the primary site?
    3. How will this affect all the currently deployed Configuration clients that are already out in the environment? These are scattered all across the planet (I work for a small airline), so physically going to them and uninstalling old CC and installing a new one is really out of the question.
    4. What documentation exists for fixing any failures in these steps?  What in AD might break, is there anything that might need ADSI, etc. We must maintain 800-171 compliance so I have to have proper change control on this project.
    Sunday, April 8, 2018 1:39 PM

All replies

  • you can move on from sccm 2012 to sccm 1606 under these conditions:

    1- min of OS W2008 R2 SP1;

    2- min of SQL Server 2008 R2 SP3;

    3-then you can move SQL server to 2012;

    4- after that upgrade to SCCM 1610;

    5- move then OS to W2012 R2

    6- a little bit of workarounds to get the new OS up and running: IIS, dot net, WDS, 

    look at my thread of similar upgrade journey


    Cherif Benammar

    Sunday, April 8, 2018 6:33 PM
  • One correction here -- don't upgrade to 1606 as that version is no longer supported; you should upgrade to 1702 or 1802 if the media has been released.

    To directly answer the questions, you have multiple steps no matter how you do it -- that's what happens when you fall this far behind.

    1. There's no such thing as "transferring" a site. You can perform a backup and restore though to a new system running a different OS but you must use the same ConfigMgr and SQL version. After you restore the site, then you can upgrade it.

    2. This is technically valid also but not nearly as straight-forward as most would have you believe and involves a lot of extra work and some pain. This is not my preference.

    3. You'd never have to do this. If you backup and restore and upgrade, the client won't know anything has changed at all. If you perform a migration, then you'd simply use whatever your preferred client deployment methodology is to deploy the new agent.

    4. See https://home.configmgrftw.com/configmgr-site-server-os-instance-change/ and https://home.configmgrftw.com/configmgr-site-backup-restore/

    This has nothing to do with AD so nothing in AD will break.

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

    • Proposed as answer by Lorry Luo Friday, May 4, 2018 7:22 AM
    Sunday, April 8, 2018 8:59 PM
  • Thanks Jason for that correction, I am telling him SCCM 1606 just for transition phase, as 1702 doesn't run on Windows 2008 R2, then all of remaining supported CB will be possible to upgrade to, either from installation media or update and servicing,

    having SCCM 1606 installed will permit to upgrade OS from 2008 to 2012,

    Cherif Benammar

    Sunday, April 8, 2018 9:05 PM
  • Right, that's why you perform a backup and restore first to a new system which is the goal of the OP.

    If they weren't moving to a new system, then you are correct, they'd have to go to 1606.

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

    Sunday, April 8, 2018 9:22 PM