:::: MENU ::::
Browsing posts in: OSD


If you encounter an error during the imaging process, please note the error code generated by the Tssk Sequence Wizard. Please reboot the system and boot into the task sequence wizard using an available boot media or PXE function.

Once within the Task Sequence Wizard, select F8 to initiate the command prompt. Within the command prompt, please run the following commands depending on the error listed below:


For Microsoft Surfaces ONLY

  1. Enter the command “ipconfig /all” to verify that the machine has a network connection.
  2. Enter the command “time” to verify that the machine has the proper time set.
  3. Enter the command “date”, to verify that the machine has the proper date set. After verifying this information continue to the diskpart steps.

For Everything Else:

If you are not imaging a Surface Pro and receive a 0x8004005or 0x80070570 error, please use the Diskpart Steps that arebolded and listed below:

  1. Enter the command “diskpart”.
  2. Enter the command “list disk”, this will show a selection similar to the one listed below:

Disk ###  Status         Size         Free     DynGpt

——–  ————-      ——-       ——-    —      —

Disk 0    Online          238 GB     0 B        *(select the OS disk)

Disk 1    Online           28 GB      0 B


  1. Select the OS disk (Disk 0) with the following command: “select disk 0”.
  2. Once selected, enter the command “clean”.
  3. Once cleaned, enter the command “create partition primary”.
  4. Once the partition is created, select the partition with the command “Select partition 1”.
  5. Once selected, enter the command “active” to activate the partition.
  6. After selection, format the OS disk with the following command “format quick fs=ntfs”.
  7. After format, enter the command “assign” to assign a drive letter or mount point.
  8. After assigning the disk a mount point, enter the command “exit” to complete the processfollowed by a full reboot of the machine.

For an “0x8007005 or 0x80070070 error or an image where the primary drive isn’t imaged as C:”, please run the following diskpart steps:

  1. Enter the command “diskpart”.
  2. Enter the command “list disk”.
  3. Select the OS disk (Disk 0) with the following command: “select disk 0”.
  4. Once selected, enter the command “clean”.
  5. After cleaning the disk, enter the command “exit” to complete the process followed by a full reboot of the machine.

OSD Troubleshooting SMSTS.log Location


Phase  Log Location
Windows PE – Before the hard disk is
formatted x:\windows\temp\smstslog\smsts.log
Windows PE – After the hard disk has
been formatted x:\smstslog\smsts.log and copied to
Windows Operating System – Before
the ConfigMgr Client is installed c:\_SMSTaskSequence\Logs\Smstslog
Windows Operating System – After the
ConfigMgr Client has been installed c:\windows\ccm\logs\Smstslog
Windows Operating System – Once the
Task Sequence has completed c:\Windows\CCM\Logs\smsts.log



Basic USMT Understanding with example of windows 7 to Windows 10 user profile migration

USMT is one of the Tool from ADK (Windows Assessment and Deployment Kit )





User State Migration Tool (USMT) is a  tool that can be used to migrate user state, data and settings as part of a image build or outside of image.  It will process to transfer mapped drives,  favorites, and other settings listed below to a separate computer in hopes that it would help with machine refreshes and replacements.


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

Files with the following extensions:we can do customization if we want

  • .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

Limitation of USMT ,Which it wont migrate following things :—

  • 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

How USMT will work :

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

download sample  XML files  it has my sample custom files Custom2.xml and Migration.xml  you needs to call at  Capture User Files and Settings in Task sequence and Restore User State




Sample SCCM Task Sequence :–

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) : Its a role from SCCM. its kind of share location where we can use for profile storage

Advantages /Disadvantages : —

  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 HardDrive. When It restore calls.

Advantages /Disadvantages : —

  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]. :—

SCOPE :User  profile migration from Windows7 to Windows 10/other machine as your wish

  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

Above steps will explain in details in below :—

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.

computer association 1.

computer association 2


Here you can add specific user or all user etc settings

computer association 3


computer association 4


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 1 : ScanState [ For Capturing the User profile settings]





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

For  capturing the user data below logs will help you

  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


For  restoring the user data below logs will help you

  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



Known Issues: —



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



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.