Had a chance to be involved in a project whereby a client had requested to implement user state and profile migration via SCCM / USMT.
This basically requires configuring the State Migration Point in the SCCM site server and creating computer association, determining from which machine (Source) the user’s profile and data files are being migrated over to (Target)
Then, there will be 2 separate Task Sequences to capture and restore user’s profile and files via USMT scanstate and loadstate executions. As the rule of thumb, the Task Sequence to restore user’s data should only be run after the data capture has successfully executed.
I decided to take a step further by further automating the entire process via System Center 2012 R2 Orchestrator.
It consists of several runbooks, ranging from
- Performing readiness check, making sure both machines are ready for user’s profile and data transfer
- Performing user’s profile and data migration by
- creating the computer association
- pushing the task sequences to both source and target machines and verify its execution
- Replicating all the SCCM direct membership collections from the source to destination, ensuring additional software / applications are successfully pushed to the target machine
which are all called from a main runbook
