none
Cross Forest Migration RRS feed

  • Question

  • We have a SCCM 1810 hierarchy (CAS with Two Primary, 4 secondary sites) in AD Forest A.com.

    Organization has created Forest B.com where we will create a new SCCM hierarchy with Standalone Primary site. We need all the packages, CIs, Software updates, Boundary etc information from the old SCCM hierarchy to the new SCCM hierarchy.

    Is this a supported scenario? Please point to helpful reference if available.

    Wednesday, May 22, 2019 8:38 PM

Answers

  • Sure. Use the built-in migration tool set: https://docs.microsoft.com/en-us/sccm/core/migration/migrate-data-between-hierarchies. Keep in mind that this does not truly migrate everything, but it gets most things. Basically, anything outside of ConfigMgr's direct control or that did not exist in ConfigMgr 2007 cannot be migrated with the migration tool set. Examples include source files and client settings.

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

    • Marked as answer by 3M3M3M Thursday, June 6, 2019 5:25 AM
    Wednesday, May 22, 2019 9:12 PM

All replies

  • Sure. Use the built-in migration tool set: https://docs.microsoft.com/en-us/sccm/core/migration/migrate-data-between-hierarchies. Keep in mind that this does not truly migrate everything, but it gets most things. Basically, anything outside of ConfigMgr's direct control or that did not exist in ConfigMgr 2007 cannot be migrated with the migration tool set. Examples include source files and client settings.

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

    • Marked as answer by 3M3M3M Thursday, June 6, 2019 5:25 AM
    Wednesday, May 22, 2019 9:12 PM
  • Hi,

    Yes, we can combine multiple hierarchies into one, and we can also move data and configuration from a prior version of Configuration Manager, for the details, we can refer to Jason's link.

    Regards,
    Allen

    Please remember to mark the replies as answers if they help.

    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, May 23, 2019 2:43 AM
  • Thank you Jason. Link talks about this so thought of checking.

    Data Gathering:

    To enable the destination site to gather data, you must configure the following two source site access accounts for use with each source site:

    • Source Site Account: This account is used to access the SMS Provider of the source site.

      • For a Configuration Manager 2007 SP2 source site, this account requires Read permission to all source site objects.

      • For a System Center 2012 Configuration Manager or System Center Configuration Manager source site, this account requires Read permission to all source site objects, You grant this permission to the account by using role-based administration. For information about how to use role-based administration, see Fundamentals of role-based administration for System Center Configuration Manager.

    • Source Site Database Account: This account is used to access the SQL Server database of the source site and requires ConnectExecute, and Select permissions to the source site database.

    • Edited by 3M3M3M Thursday, May 23, 2019 9:18 AM Correct
    Thursday, May 23, 2019 9:17 AM
  • Thank you Allen.
    Thursday, May 23, 2019 9:19 AM
  • > so thought of checking

    Checking what?

    That doesn't change or impact anything. It simple says you need one account (or two) that has permissions in the source hierarchy. How else would you (or it) be able to access anything in the source hierarchy?


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

    Thursday, May 23, 2019 2:23 PM
  • Thank you Jason. Can the new hierarchy in Azure share the DPs of existing on-premise SCCM hierarchy?
    Thursday, June 6, 2019 5:28 AM
  • The location of the hierarchies is irrelevant and Azure is just another location in this case, so yes, as long as the necessary connectivity exists between the locations and other migration prerequisites are fulfilled.

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

    Thursday, June 6, 2019 2:26 PM