none
SCCM 2012 SP1 R2 to SCCM CB1802 migration

    Question

  • Hi All,

    We are planning to migrate SCCM 2012 to SCCM CB 1802 ver. and  also considering upgrading Primary & Secondary Site Operating system to Windows server 2016. Could someone recommend best ideal approach

    Curent SCCM Environment

    SCCM 2012 R2 SP1
    Primary Site Server Os: Windows 2008R2
    Backend database server: Windows 2008 r2/Sql 2008r2
    Secondary Sites: Windows Windows 2012 R2

    Thanks


    Wednesday, April 25, 2018 12:46 PM

All replies

  • Not a migration at all.

    Upgrade. It's a little tricky now that you've waited this long into the CB era as it will require multiple steps, but it's [far] less (re-)work than a full migration.

    1. Upgrade to 1606 (using media).

    2. Upgrade SQL Server to 2014 or 2016.

    3. Back up and restore to new site server running Server 2016.

    4. Upgrade to 1706 (using in-console servicing).

    5. Upgrade to 1802 (using in-console servicing).

    6. Upgrade clients to 1802.

    As noted, a migration sounds like less work and while it's fewer steps, it's not less work particularly when you have secondary sites and other remote infrastructure involved that doesn't really need to change at all. Also, the migration toolset doesn't actually migrate everything and there are always caveats, idiosyncrasies, and other pain that comes with migrations.


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

    • Proposed as answer by Dan Padgett Thursday, April 26, 2018 3:51 PM
    Wednesday, April 25, 2018 2:14 PM
  • Thanks Jason for your reply. I was thinking in below order. After new Server restore, Can't we upgrade to 1802 using baseline media.. Could you recommend any article or document that shows backup and restore of site server.

    What steps to follow for secondary sites OS upgrade as they are running on windows server 2012 R2. Can we do in place upgrade of Secondary sites and DP's running on Windows server 2012 R2

    .1. Upgrade SQL Server to 2014 or 2016.

    2 . Upgrade to 1606 (using media)

    3. Back up and restore to new site server running Server 2016.

    4. Upgrade to 1802 (using Baselinemedia)

    5. Upgrade clients to 1802.

    Wednesday, April 25, 2018 2:33 PM
  • I don't remember what SQL versions that 2012 R2 supported so that's why I had the SQL upgrade after the 1606 upgrade.

    For #4, you cannot (in a supported manner) use media to upgrade a CB site -- you must use in-console servicing.


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

    Wednesday, April 25, 2018 2:56 PM
  • Thanks Jason for guidance.

    Regarding Secondary Sites

    1) Do we need to upgrade them each time when we install 1606, 1702 and then 1802 or just upgrade secondary site only after 1802 version.

    2) What steps to follow for secondary sites OS upgrade as they are running on windows server 2012 R2. Can we do in place upgrade of Secondary sites and DP's running on Windows server 2012 R2.



    Wednesday, April 25, 2018 3:10 PM
  • 1) I honestly don't know off hand but I think the answer is yes.

    2) Yes, but there's no rush on this to my knowledge. 2012 R2 should be supported for at least 4 more years and the site should be fine with them being on Server 2012 R2. One thing that isn't explicitly supported though but is generally known to work is if your secondary sites host the SUP role because technically the WSUS versions must match and to match they need to be on the same server OS.


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

    Wednesday, April 25, 2018 3:19 PM
  • Jason one more query. instead of upgrading sccm 2012 to 1606 version first, could we follow below approach as per your suggested approach

    1. Upgrade SQL Server to 2014 or 2016.

    3. Back up and restore sccm 2012 primary site to new site server running Server 2016.

    3 Upgrade to 1802 (using base media).

    4. Upgrade secondary sites & clients to 1802.

    In-place upgrade paths

    Upgrade to version 1802
    When you have version 1802 baseline media, you can upgrade the following to a fully licensed version of System Center Configuration Manager version 1802:

    • An evaluation install of System Center Configuration Manager version 1802
    • System Center 2012 Configuration Manager with Service Pack 1
    • System Center 2012 Configuration Manager with Service Pack 2
    • System Center 2012 R2 Configuration Manager
    • System Center 2012 R2 Configuration Manager with Service Pack 1

    Thanks for your responses

    Wednesday, April 25, 2018 5:48 PM
  • No because ConfigMgr 2012 is not support on Server 2016.

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

    Wednesday, April 25, 2018 6:50 PM
  • Jason, if i follow below then i think i will only need to use sccm cb media once,  and it will save time on secondary site upgrade as well as i have to use it only once.

    1. Upgrade SQL Server to 2014 or 2016.

    3. Back up and restore sccm 2012 primary site to new site server running Server 2012 r2.

    3 Upgrade to 1802 (using base media).

    4. Upgrade secondary sites & clients to 1802.

    5. inplace upgrade of os to 2016

    Wednesday, April 25, 2018 7:21 PM
  • Yes, that can work also. Most folks avoid in-place OS upgrades though.

    Also note that for #1, as noted, I'm pretty sure ConfigMgr 2012 doesn't support SQL 2016 although it may support 2014 so you need to check that.


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

    Wednesday, April 25, 2018 8:18 PM
  • As per Microsoft SQL 2016 is supported with sccm 2012 

    https://technet.microsoft.com/en-us/library/gg682077.aspx?f=255&MSPPError=-2147217396#Configurations%20for%20the%20SQL%20Server%20Site%20Database

    Thursday, April 26, 2018 3:08 AM
  • OK, then you should be fine with upgrading SQL Server first -- that's why we have documentation to avoid assuming bad things.

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

    Thursday, April 26, 2018 1:01 PM