We Understand Planning and details requirement now lets talk about details how to full fill and make successful Migration:-
In this Article i will be sharing details.
End to End Procedure for Running Migration from Source Hierarchy.
Once we have configured the Destination Hierarchy and Verified Operational Functionality and after meeting all the Prerequisites, We can perform the Migration activity by connecting to Source Hierarchy from Destination Hierarchy. Below steps should be followed in order to perform the Migration.
Logon to the Top Level server (CAS or Standalone Primary server) in i will be sharing Standalone Primary server.
From the SCCM console.
Browse to Administration Workspace.
Select Migration, at the Top Ribbon click on the Icon Specify Source Hierarchy.
Now in the below Source Hierarchy:
Select the following options:
-
Provide the FQDN for Top-level Configuration Manager Site server.
-
Specify the Migration account that you have already created as part of your Migration Prerequisite.
Note: Migration account requires Read permission to all source site objects and requires Connect, Execute, and Select permissions to the source site database. This account must be assigned the role-based administration security role of Infrastructure Administrator.
-
In the User Accounts Radio Button Options Set the Migration Account that you Already Created.
If you are planning to utilize the Existing distribution points from the source Hierarchy, then select the option.
Enable Distribution points sharing for the Source site.
By Selecting this option Sccm clients in Destination Hierarchy may can get the content from the Distribution points that belong to Source Hierarchy.
Also Very important note > Devices in Source Hierarchy can only receive the content that is already available in Source.
Hierarchy, meaning that any new applications or packages that are available in destination Hierarchy cannot be distributed to DP Shared DP’s from Source Hierarchy. We have covered more on DP sharing and reassignment in upcoming documents, you may refer it for more information.
Click Ok to initiate a Data Gathering Session that may run up to several minutes, wait for the Data gathering to be completed. Data Gathering would analyze the total number objects that are available for Migration from the source Hierarchy.
Note: Now We are ready to Migrate object
Create a Migration Job to Migrate Objects from Source Hierarchy, Post Completion of Data-Gathering Job.
Now Create Migration Job to Fetch Objects from Source Hierarchy, below is the procedure.
Right click Migration Jobs and Select Create Migration Job.
Provide a Name of your choice for the Migration Job.
Under Job type We have 2 Options Object Migration and Objects modified after Migration.
Select Object Migration in this case Objects modified after Migration can be used in future Migrations when the Objects in Source Hierarchy are Modified after our first Migration process is run.
Ex: if there are new Applications and Collections are added in the Source site after our 1st Migration job is executed, then we must select the option Objects modified after Migration.
This job will only show us the Objects that are newly added or modified in Source Hierarchy instead of listing all Available objects.
Review the list of Objects that are listed and Select All Objects that you would like to Migrate from Source Hierarchy and Click Next:
In Content Ownership Tab Source and Destination Servers will auto populate, Click Next.
In Site Code Replacement Tab, you may choose to leave it blank and Click Next
If we select the Source site code, then All the collections will be changed.
On the Security Scope tab, specify the security scope to apply to the migrated objects, click Next Note: If you are planning to run Multiple Migration jobs it is best practice to assign Security scope.
On the Settings tab, Select the following Options
Select the Option Run the Migration Job now or You may configure it to fun after business hours.
Also Select the option Do Not Migrate updated objects, this option will be help us from Protecting the Objects that are previously Migrated from getting Overwritten.
On the Summary tab, Review the options and settings and Click Next
Once the Migration Job is completed, you May view the status of the Job Under Migratio Jobs Tab.
Also, it is a Best practice to View Migmctrl.log
when the Migration jobs are in progress.
You and find it in SCCM installation directory Microsoft Configuration Manager\Logs\Also, upon Successful Migration Successful completion of All Migration Jobs you can find below objects.
- Applications.
- App-V Virtual Environment .
- Asset Intelligence customizations.
- Boundaries.
- Collections.
- Compliance settings: 1) Configuration baselines and 2) Configuration items
- Deployments.
- Operating system deployment: 1) Boot images. 2) Driver packages 3) Drivers 4) Images 5) Packages 6) Task sequences.
- Software updates: 1) Deployments 2) Deployment packages 3) Templates 4) Software update lists.
- Software distribution packages.
- Software metering rules.
- Virtual application packages.
Important Note:
Collections: Collections will be migrated along with their Query memberships and the targeted deployments
Packages and Applications: Package and Applications along with All Deployment types will be migrated. Note: Source files for this packages will not be migrated to Destination server. For migrating the Source files,we have to copy all the Source files from its original location on the Destination server and paste them to the Source Hierarchy package source location, following which you need to update the content location of all packages and applications to new Source location.
We can perform this using a Power Shell Script. We will cover this in detail in our next Article about Content Source Movement of Migrated Applications and Packages
Thank you All,
Happy Learning!!!
Thanks & Regards,
Haresh Hirani
Email: [email protected]
Follow me: https://www.linkedin.com/in/hiraniconfigmgr
X
![]()
5 Comments
Del
12-03-2019 09:06 pmGreat article ! 'Enable Distribution points sharing for the Source site.' - does this option need to be selected on all migration jobs ? Can it be selected on the final migration task once you are ready for DP's to be share ? If selected on last migration task, will all content migrated in previous tasks be visible to clients on the shared DP ?
Haresh Hirani
Thanks for feedback
Haresh
13-03-2019 08:25 am! 'Enable Distribution points sharing for the Source site.' - does this option need to be selected on all migration jobs ? Answer is No Can it be selected on the final migration task once you are ready for DP's to be share ? If selected on last migration task, Answer is Yes it can be will all content migrated in previous tasks be visible to clients on the shared DP ? Yes For more wait for more space. will be updating soon DP reassignment task which cover all these information
Manu
18-09-2019 09:58 amThanks for writing this Haresh. I have created the migration job which are running successfully but when I check the console I dont see the objects which the migmctrl.log is claiming to migrate. Have you seen this behaviour?
Haresh Hirani
I have not seen any such behavior i feel there would be some of the block or port not open or wmi is not accessible please validate.
Haresh
22-11-2019 08:35 amDear manu, there is no such behavior
dashrathchate
24-09-2021 02:07 pmhttps://dashrathchate.blogspot.com/2021/09/sccm-image-migration-to-new-server.html