Home > ConfigMgr 2007 > USMT 4.0 and SCCM 2007 SP2 R3

USMT 4.0 and SCCM 2007 SP2 R3

In this post I wanted to show you one of the many different methods to use USMT 4.0 to transfer settings in a side-by-side scenario in SCCM 2007 SP2 R3. I will be using an existing XP system and transferring the profile over for the user to their new Windows 7 system.


Source PC: Windows XP with sp3. The primary user of this computer is TestUser1 with favorites, local documents and items on the desktop.

Destination PC: Windows 7 with SP1. This computer is newly imaged through SCCM.

Both computers have the SCCM 2007 SP2 client with the R3 hotfix applied.

Setting up the SMP Role on the Server

In order to help transfer the profile I am setting up a Migration point. It is also a good idea specify a retention policy. Doing so will allow you to keep the profile for a specified amount of time and will not cause space issues down the road.

Note: If you are installing the SMP role for the first time, it is recommended to wait about an hour after installing before you try a USMT capture and restore.

Below you can see how I setup my folder.

Computer Association

Note: you must setup the computer association before you attempt to capture and restore the USMT.

You can also specify a computer account(s) to migrate over. If you do not specify, all accounts will be migrated. If you do not specify an account then all accounts will be migrated over. I have seen this cause issues with accounts such as ASPNET.

Once you click ok, you will see the computer association and the type of migration that will take place.

Capture Task Sequence

The capture task sequence is pretty simple.

  1. It is requesting access to the User Stage Storage
  2. The capture of the profile(s) you selecting will be taking place
  3. It process will release the state store. Basically it’s telling the migration point, ok I am done with what I need to do.

Restore Task Sequence

In my restore you can see the steps I selected.

  1. Restart the computer. (This is not necessary, I just had it setup this way in my lab)
  2. Use Toolkit package. This is the MDT 2010 toolkit itself
  3. Gather. This is using the CustomSettings.ini from the settings package
  4. Tattoo. This is the command line that it will run cscript.exe “%deployroot%\scripts\ztitatoo.wsf”
  5. Restore Groups. This is another command line based task sequence cscript.exe “%deployroot%\scripts\ztigroups.wsf” /restore
  6. Request State Store.
  7. Restore State Store. This will restore the profile from the computer you associated with.
  8. Release State Store. Just like before it tells the migration point it is done.
  9. Copy Logs. This is a command line based task sequence. cscript “%deployroot%\scripts\zticopylogs.wsf”
  10. Set Error Code. This is a Task sequence variable. %_SMSTSLastActionRetCode%
  11. Use toolkit package.
  12. Gather.
  13. Move State Store. Is a command line. cscript.exe “%deployroot%\scripts\ztimovestatestore.wsf”
  14. Copy Logs. Command line cscript “%deployroot%\scripts\zticopylogs.wsf”
  15. Error in the task sequence. Command line cscript “%deployroot%\scripts\ztierrormsg.wsf”

Once the migration has completed the general information will appear about the Migration Date. You can also look at the advertisement to see that it was successful

Categories: ConfigMgr 2007
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: