none
Requirements for migrating applications RRS feed

  • Question

  • We are migrating from ConfigMgr 1706 to a new ConfigMgr 1810 environment, these are completely separate environments. The new environment has the 1706 primary server configured a source hierarchy. Wen using object migration jobs to migrate applications does this process copy the actual files to the new server or does this need to be done manually? Also, after migrating an application, does this remain functional in the source environment?

    Thanks in advance.

    Thursday, May 2, 2019 1:10 PM

Answers

  • No, source files are not copied in any way to the new environment as these are outside the scope of control of ConfigMgr. You need to manually copy (or move) them *and* update their source paths if necessary unless they are already in a separate location that does not need to change.

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

    • Marked as answer by AllyRussell Friday, May 3, 2019 11:52 AM
    Thursday, May 2, 2019 1:54 PM

All replies

  • No, source files are not copied in any way to the new environment as these are outside the scope of control of ConfigMgr. You need to manually copy (or move) them *and* update their source paths if necessary unless they are already in a separate location that does not need to change.

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

    • Marked as answer by AllyRussell Friday, May 3, 2019 11:52 AM
    Thursday, May 2, 2019 1:54 PM
  • OK, that was expected. The current applications are not in a shared location so presumably all that's required is to robocopy the data specified in the applications content location path, and update their source paths? I'm also presuming the object migration jobs still allow the content to be deployed in the source environment I.E. do not modify the source in any way?
    Thursday, May 2, 2019 3:44 PM
  • Correct to both questions.

    For updating the source paths, that's probably not something that you want to do by hand. PowerShell for the win here or a tool built on PowerShell like this one by Nickolaj: https://gallery.technet.microsoft.com/ConfigMgr-Content-Source-ac490b67

    Also, keep in mind that this won't re-copy the content but it will generate traffic as the content must be validated on the DPs as changing the source path will increment the version of the content and thus ConfigMgr must validate whether there are (or aren't) changes to the content.


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

    Thursday, May 2, 2019 3:52 PM
  • Great thanks, I already had a couple of tools and scripts sourced for changing the content due to the number of applications.

    In terms of content version being incremented this wont be an issue. The plan is to robocopy the data to the primary server, migrate the applications via a migration job, update the application source paths via the tool and then deploy to the required distribution points (The DP's are new as well I.E. no shared Distribution Points)

    Thanks again for the clarification

    Thursday, May 2, 2019 4:03 PM