locked
SCMM 2012 R2 SP1 to SCCM 1511 migration question RRS feed

  • Question

  • Hello everyone,

    Existing Infrastructure
    1. SCCM 2012 R2 SP1 Server
    a) All roles on one server
    2. Windows Server 2008 R2

    Project Goals
    1. Upgrade SCCM 2012 R2 S1 to SCCM 1511
    a) Windows Server 2012 R2
    2. Split SCCM roles as such
    a) Remote SQL server - single server
    b) SUP Role - single server
    c) DP Role - single server
    d) All other roles - single server

    My idea was to start the migration process with 2.a, 2.b then 2.c and so on. However, I don't know if this the proper way of doing it. In the end the original single SCCM server will no longer be used.

    I know I could do a backup and restore SCCM on a new Server 2012 R2, but that will put all roles on a single server, which I'm trying to avoid. Now, is it better to do the restore on a single server, make sure all works again and then migrate the roles?

    Any suggestions, pointers or concerns?

    Thanks!!
    Thursday, June 2, 2016 2:43 PM

Answers

  • Meh. A SQL Server backup + the other things you need to back up is sufficient (and preferred IMO). The site backup maintenance task only backs up the DB, doesn't compress it, pauses services, and doesn't back anything else up that you need so is not the best choice IMO.

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

    Sunday, June 5, 2016 1:23 AM

All replies

  • Upgrade to SCCM 1511 and then update that to 1602. You can then run an in-place upgrade of the O/S to Server 2012 R2 as this is supported from 1602.

    I would not go with a remote SQL server (how many clients are you supporting?)

    Are you trying to scale out with the roles on different servers? Not sure why you are doing this.


    Cheers Paul | http://sccmentor.wordpress.com

    Thursday, June 2, 2016 2:55 PM
  • Upgrade to SCCM 1511 and then update that to 1602. You can then run an in-place upgrade of the O/S to Server 2012 R2 as this is supported from 1602.

    I would not go with a remote SQL server (how many clients are you supporting?)

    Are you trying to scale out with the roles on different servers? Not sure why you are doing this.


    Cheers Paul | http://sccmentor.wordpress.com

    I'm supporting 1700+ devices (laptops, computers, servers, etc).

    Yes, I'm trying to scale out to make sure I can manage our growth.


    • Edited by GonzEd Thursday, June 2, 2016 3:04 PM
    Thursday, June 2, 2016 3:03 PM
  • 1,700 is honestly a very small number and no reason to separate out SQL Server. Unless you are planning on hitting 25,000+, you should never consider this and even then its debatable and most of us will still say not to: https://stevethompsonmvp.wordpress.com/2014/12/20/why-you-should-not-use-remote-sql-server-with-configmgr-2012/

    If you want to split roles off, split the MP, DP, and SUP off onto its own system (aka site system). This will allow you to remove IIS from the site server and provide the most benefit.


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

    Thursday, June 2, 2016 8:15 PM
  • Echo what Jason said hence the question.

    Cheers Paul | http://sccmentor.wordpress.com

    Thursday, June 2, 2016 9:07 PM
  • 1,700 is honestly a very small number and no reason to separate out SQL Server. Unless you are planning on hitting 25,000+, you should never consider this and even then its debatable and most of us will still say not to: https://stevethompsonmvp.wordpress.com/2014/12/20/why-you-should-not-use-remote-sql-server-with-configmgr-2012/

    If you want to split roles off, split the MP, DP, and SUP off onto its own system (aka site system). This will allow you to remove IIS from the site server and provide the most benefit.


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

    Okay, say that I do an in-place upgrade (SCCM 2012 R2 SP1 to SCCM 1511 for now), if I take a backup (or better yet if I snapshot the server) and if something goes awfully wrong - will reverting back to the snapshot be enough to bring SCCM back to production?

    Another thing that concerns me is AD schema changes during the SCCM upgrade process. Is there anything that gets updated/changed during the upgrade process?

    I just want to minimize downtime and I'd like to be extra careful.

    Thanks!

    Saturday, June 4, 2016 4:57 PM
  • "or better yet if I snapshot the server"

    Be careful with this one, it can cause all sorts of issues. A backup is much better and is supported.

    Yes, a simple restore will revert things.

    There are no schema changes and an upgrade would never have permissions to perform them anyway.

    The 1511 upgrade is pretty smooth and I've only seen sporadic issues.


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

    Saturday, June 4, 2016 9:02 PM
  • "or better yet if I snapshot the server"

    Be careful with this one, it can cause all sorts of issues. A backup is much better and is supported.

    Yes, a simple restore will revert things.

    There are no schema changes and an upgrade would never have permissions to perform them anyway.

    The 1511 upgrade is pretty smooth and I've only seen sporadic issues.


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

    And we're talking about doing a "Backup Site Server" task, correct? 

    Thanks!

    Sunday, June 5, 2016 1:10 AM
  • Meh. A SQL Server backup + the other things you need to back up is sufficient (and preferred IMO). The site backup maintenance task only backs up the DB, doesn't compress it, pauses services, and doesn't back anything else up that you need so is not the best choice IMO.

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

    Sunday, June 5, 2016 1:23 AM