Usmt is one of the Tool from adk (Windows Assessment and Deployment Kit)

With this USMT tool we are able to copy and restore the following:

• 
  Custom Map drives
  
• 
  STARTMENU configuration
  
• 
  QUICK LAUNCH settings
  
• 
  DESKTOP settings
  
• 
  Printers
  
• 
  User Accounts
  
• 
  PERSONAL
  
• 
  MYPICTURES
  
• 
  FAVORITES
  
• 
  MYVIDEO
  
• 
  MYMUSIC
  

• 
  .qdf, .qsd, .qel, .qph, .doc*, .dot*, .rtf, .mcw, .wps, .scd, .wri, .wpd, .xl*, .csv, .iqy, .dqy, .oqy, .rqy, .wk*, .wq1, .slk, .dif, .ppt*, .pps*, .pot*, .sh3, .ch3, .pre, .ppa, .txt, .pst, .one*, .vl*, .vsd, .mpp, .or6, .accdb, .mdb, .pub
  

• 
  Files tagged with both the hidden and system attributes.
  
• 
  Files and folders on removable drives,
  
• 
  Data from the %WINDIR%, %PROGRAMFILES%, %PROGRAMDATA% folders.
  
• 
  ACLS for files in folders outside the user profile.
  
• 
  Local attached printers won't migrate
  

USMT will work based on XML Files. USMT Package will have XML Files. Like MigApp.XML, MigUser.XML , MigDocs.XML , Config.xml etc. Each and every XML file has specific components to migrate.  If you want to read the XML file user the XML Editor for easy to understand.

I haven't tried but you can also use the USMT GUI editor check out this .

So if you want to customize the XML file always better to create new XML file rather than editing the default XML file

In my example I'm attaching my XML file.

My requirement is user profile only requires to restore .below are the points in detailed

1. 
   It should not restore any documents under C:\Drive (or any other folders under C drive).
   
2. 
   User desktop documents and user profile settings,shortcuts,Pin items,desktop wallpaper , favorites  , My pictures,my documents,etc
   
3. 
   Also under C:\temp\Printer\any files it should restore
   

Assuming you already have the USMT package in place in SCCM console

Here Profile Capturing /Storing will be in 2 Ways

• 
  SMP (State Migration Point): It’s a role from SCCM. it’s kind of share location where we can use for profile storage
  

1. 
     We should have enough space to store the user data. If your concern about space check out this to get some idea how much space you may requires Collecting USMT Estimates using ConfigMgr
   
2. 
    With SMP It has it own mechanism for deleting the aged data or maintenance task
   
3. 
    Also data will be encrypted and we can't able to see the files. It will be stored in .MIG format
   
4. 
    It will slow process to compare to Hard-Link process. Since data will be stored in remote location. Speed of the process will depends on the bandwidth
   

• 
  Local store / Wipe Mode (Hard-link migration) - It will create Links in the Sectors of inside the Hard disk and It will Wipe the Hard Drive. When it restore calls.
  

1. 
   By using the linking mechanism from sectors it will restore the user data - So here We can't  format 100% of the hard drive
   
2. 
   Since data will be stored under local hard drive.it will be faster to compare to SMP
   

 

Summary of steps need to perform to migrate the Standalone user profile [SMP]. :---

1. 
   USMT Package should be ready with above Xml Files. Paste above XMl files under USMT folders
   
2. 
    SMP Role should be in place
   
3. 
    relate the old and new computers in Computer Association as shown 
   
4. 
   create a task sequence for capture in above case Task sequence 1
   
5. 
   create a task sequence for restore in above case Task sequence 2
   
6. 
   Create a Collection  called " Capture " and add the machine windows 7
   
7. 
   Deploy the Task sequence 1 on " Capture "Collection. Make sure it should get success
   
8. 
   Create a Collection  called " Restore " and add the machine windows 10
   
9. 
   Deploy the Task sequence 2 on  " Restore "  Collection. Make sure it should get success
   

I have 2 machines windows 7 and Windows 10 / or any other version windows7/8.1 etc

Now I want to transfer my user profile data from Windows7 machine to windows 10 machine

For this, we need 2 Task sequences with below steps and Computer Association

First we need to co-relate the machine relation with help of Computer Association.

Here you can add specific user or all user etc settings

 

1 Task sequence -- > For user profile Capturing - Here "Capture USMT " Task Sequence Set will be use full as showing in below screenshots. This  Task sequence we will be run on Windows 7 machine

2. Task Sequence -->  To restore user profile.Here "Restore" Task Sequence Set will be use full as showing in below screenshots. This  Task sequence we will be run on Windows 10 machine

Task sequence 2 : LoadState [ For Restoring the User profile settings]

 
 

TrobleShooting Steps  and Logs info :---

• 
  You may face the issues in either capturing or Restoring stage which are related to USMT
  
• 
  At the time of running the task sequence it create a Folder "C:\_SMSTaskSequence" and download the USMT Package inside it and also it will create the folder "SMSTSLog"under C:\Windows\CCM\Logs\SMSTSLog
  
• 
  SMSTSLog folder contains the log at the time of running the task sequence .once task sequence completes it will move the logs to under CCM folder C:\Windows\CCM\Logs
  

1. 
   SMSTS.log : General Task sequence execution info
   
2. 
   scanstate.log -  scans all user profiles and what files its scanned according to the XML defined
   
3. 
   scanstateprogress.log :  How much Percentage it completes
   

1. 
   SMSTS.log : General Task sequence execution info
   
2. 
   loadstate.log-  Loads all user profiles and what files it should restore according to the XML
   
3. 
   loadstateprogress.log :  How much Percentage it restored s it will shows
   

1. 
   If you're running multiple time on same machine irrespective of result. So might get certificate error.
   
2. 
   
   
3. 
    Just delete the certificates from the  locations [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SystemCertificates\SMS\Certificates] It will resolve the issue 
   
4. 
   
   

Failed to decrypt state encryption key

sometime at the time creating the computer association it got sucked , hanged. Please remove it and recreate the computer association will fix above error

 

Most of the cases USMT will failed due to Invalid User Mapping or duplicate SID issue on Source machine while capturing.

This issue will occur due to domain migration when they are migrating the user profile with ADMT (Active Directory Migration Tool) they won't delete the old domain SID's

Check out for more info http://networksteve.com/?p=5022

Please find the script which it will remove the Specified SID user profile SIDREMOVAL.vbs .It will takes the Registry back and removes the user profile if the user profile has duplicate SID.