locked
Migrating to New Hardware RRS feed

  • Question

  • We're planning on moving our SCCM 2012 site server to new hardware. We're currently running SCCM 2012 SP1 CU3 on Server 2008 R2. We want to migrate to a Server 2012 R2 box.

    Would it be wisest to upgrade our existing SCCM 2012 SP1 server to R2 and then migrate over? I've seen that many people have migrated their sites by doing a backup and restore from the console.

    Any input is greatly appreciated!


    Orange County District Attorney

    Saturday, November 9, 2013 7:14 PM

Answers

  • The upgrade of the OS cannot be done while ConfigMgr is running on it, so you would have to use backup/restore. The order (R2 or not) does not matter, but I'd prefer restoring the current version and upgrade later on (after a couple of days or so). It's easier to determine the cause of a failure if there will be any (restore vs R2).


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

    • Proposed as answer by Joyce L Tuesday, November 12, 2013 2:08 AM
    • Marked as answer by Sandy Wood Monday, November 18, 2013 6:37 PM
    Saturday, November 9, 2013 11:14 PM
    • Backup ConfigMgr on the current server using the built-in maintenance task
    • Shut down the current server.
    • provision the new server (OS 2012 R2) with same server name & partition layout
    • Install ConfigMgr (during the installation, select the same drives location as the old one)
    • Restore ConfigMgr from backup

    http://technet.microsoft.com/en-us/library/gg712697.aspx

    then, as Torsten's mentioned, I will upgrade it to R2 later on http://technet.microsoft.com/en-us/library/jj822981.aspx#BKMK_PlanningR2Upgrade

    • Proposed as answer by Joyce L Tuesday, November 12, 2013 2:08 AM
    • Marked as answer by Sandy Wood Monday, November 18, 2013 6:36 PM
    Saturday, November 9, 2013 11:54 PM

All replies

  • The upgrade of the OS cannot be done while ConfigMgr is running on it, so you would have to use backup/restore. The order (R2 or not) does not matter, but I'd prefer restoring the current version and upgrade later on (after a couple of days or so). It's easier to determine the cause of a failure if there will be any (restore vs R2).


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

    • Proposed as answer by Joyce L Tuesday, November 12, 2013 2:08 AM
    • Marked as answer by Sandy Wood Monday, November 18, 2013 6:37 PM
    Saturday, November 9, 2013 11:14 PM
    • Backup ConfigMgr on the current server using the built-in maintenance task
    • Shut down the current server.
    • provision the new server (OS 2012 R2) with same server name & partition layout
    • Install ConfigMgr (during the installation, select the same drives location as the old one)
    • Restore ConfigMgr from backup

    http://technet.microsoft.com/en-us/library/gg712697.aspx

    then, as Torsten's mentioned, I will upgrade it to R2 later on http://technet.microsoft.com/en-us/library/jj822981.aspx#BKMK_PlanningR2Upgrade

    • Proposed as answer by Joyce L Tuesday, November 12, 2013 2:08 AM
    • Marked as answer by Sandy Wood Monday, November 18, 2013 6:36 PM
    Saturday, November 9, 2013 11:54 PM
  • Thanks to you both for the great information. I like the idea of a backup / restore with an R2 upgrade a few days later. That will work for us. Now to throw another curve ball. I'd be interested in your approach to this scenario with the addition of other System Center products in the mix. I've got Orchestrator, Service Manager, OpsMgr and Virtual Machine manager I plan on migrating as well. Would you still approach the SCCM migration in the same manner?

    Orange County District Attorney

    Tuesday, November 12, 2013 3:33 PM
  • Unless you have some kind of integration between your products the ConfigMgr migration/upgrade would be unrelated.


    Gerry Hampson | Blog: www.gerryhampsoncm.blogspot.ie | LinkedIn: Gerry Hampson | Twitter: @gerryhampson

    Tuesday, November 12, 2013 3:49 PM
  • Thanks for the note back Gerry.

    Orange County District Attorney

    Tuesday, November 12, 2013 4:19 PM
  • If you do have integrations, then the recommended order for the Upgrade is listed here:

    http://technet.microsoft.com/en-us/library/dn521010.aspx

    Basically, everything you've got except VMM should go to R2 before ConfigMgr for them to play nicely together.

    I hope that helps,

    Nash


    Nash Pherson, Senior Systems Consultant
    Now Micro - My Blog Posts
    <-- If this post was helpful, please click "Vote as Helpful".

    Tuesday, November 12, 2013 4:46 PM