Dear Folks!!
Today we will be sharing you the procedure to update the Content Library in the Destination Hierarchy, once the Object Migration Jobs are completed. Also we will share you the PowerShell script that you can download from TechNet. Also we will provide you step by step procedure how to use this GUI tool to automatically update the Content Library.
-
Go to below link to download the ConfigMgr Content Source Update Tool 1.0.2
-
Copy the Script to the Destination Hierarchy server and Run the PowerShell script with the Account that has Read rights on Content Library of Source Hierarchy (It is a prerequisite for Migration account to have Read access to Package source server of Source Hierarchy).
-
Enter the Site Server Name for the Source Hierarchy as Input.
-
Enter the Destination Server Content Library path, where you will be hosting your package Share.
-
Enter the Destination Server Content Library Path where the Package source is located.
-
Once step1 and Step 2 is populated, click on Validate. In this step Script will connect to the Destination site and analyze the all the packages and provides the list shown in step6, select all the packages for which you would like to update the content.
-
Select the check box copy files to new location.
-
Click on update. In this step script will copy all the selected packages from Source Content Library to Destination Content Library, Also Packages/Applications that were previously showing the content location from old Package source from the Source Hierarchy will be now updated with New Source location from the Destination Hierarchy. (meaning that now the packages/Application should be ready for Distribution to Distribution points) if you are planning to use the Distribution point Reassignment option then, content Distribution to DP’s can be performed after the DP reassignment is completed. We have covered the DP Reassignment in next Article.
Hello,
This step is not correct:
Enter the Destination Server Content Library path, where you will be hosting your package Share.
Enter the Destination Server Content Library Path where the Package source is located.
It’s the opposite: you put the sources path to Match pattern for content sources and the destination path to replace pattern for content sources locations.
Regards,