locked
Migrating ConfigMgr 1710 to new server RRS feed

  • Question

  • Planning to migrate ConfigMgr (single server holding all the roles and DB) to another server (from physical to virtual). Current OS is Server 2012 R2 and SQL is 2012. I would like to refresh OS and SQL to latest versions when moving to new server. There is new high availabiity option (or was it still only at technical preview level?) for site server and maybe I could leverage that in this case but what about the SQL? Or what would be the best way to move everything to from old server to new one?

    Tuesday, January 9, 2018 4:56 AM

Answers

  • Here's a post I crafted recently with an outline of the process: https://home.configmgrftw.com/configmgr-site-backup-restore/

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

    • Marked as answer by jqx12 Monday, March 26, 2018 4:33 AM
    Tuesday, January 9, 2018 2:54 PM

All replies

  • Hi,

    For SQL you must restore the DB to the same version as you took the backup from. I would install the new server with Server 2016 and the same version of SQL as the version that was used on the "old" when the backup was taken.(make sure the SQL Server version used is supported on both Server 2012 R2 and Server 2016) 

    Then make the restore and the whole procedure and then upgrade SQL when you are in a stable state..

    Regards,
    Jörgen


    -- My System Center blog ccmexec.com -- Twitter @ccmexec

    Tuesday, January 9, 2018 7:51 AM
  • Here's a post I crafted recently with an outline of the process: https://home.configmgrftw.com/configmgr-site-backup-restore/

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

    • Marked as answer by jqx12 Monday, March 26, 2018 4:33 AM
    Tuesday, January 9, 2018 2:54 PM
  • Hi,

    Reference the following documents about site backup and restore:

    Back up a Configuration Manager site

    Recover a Configuration Manager site

    Best Regards,

    Lorry


    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, January 10, 2018 2:01 AM
  • Hi,

    You have not updated your replied for a long time.

    Is your problem solved? If solved, can you share your solution to help more people.

    Please remember to mark the replies as answer if the help.

    Best Regards,

    Lorry


    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, February 5, 2018 8:53 AM
  • I'm not understanding why the above answer involves backing up and restoring the SCCM database. Isn't the hierarchy migration the supported path?

    Migrate data between hierarchies in System Center Configuration Manager
    https://docs.microsoft.com/en-us/sccm/core/migration/migrate-data-between-hierarchies

    Mike Crowley 
    My Blog -- Baseline Technologies


    • Edited by Mike Crowley Thursday, September 6, 2018 5:07 AM
    Thursday, September 6, 2018 5:07 AM
  • Because a migration is painful at best, does not migrate all settings, does not migrate client agents, does not migrate site systems, does not migrate content, and generally involves a lot of unnecessary re-work and re-configuration. Creating a whole new site just to refresh the OS or move to a new server just doesn't make sense. See https://home.configmgrftw.com/configmgr-site-server-os-instance-change/

    If you have a single site server with no additional systems (remote or local), a handful of clients and minimal configuration, a migration may be the easiest path -- but that's rarely the case.



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

    Thursday, September 6, 2018 1:12 PM