USMT 4.0 Hardlink Migration

[67_dbc]

Environment: 2012 SCCM (no SP1) with MDT 2012 Update 1

Task Sequence: XP to Windows 7 Mgration using HardLink Migration with USMT 4.0 standard options

Company Hardware: Lenovo T Series and X Series laptops / HP Compaq Small Form Factor and Ultra Slim Form Factor

 

 

Problem: Restore User State in the Task Sequence is not restoring User Profiles. When you log in as the user where Capture User State is performed, nothing is moving over.

 

Validation: C:\StateStore\USMT is being created and I can see all Captured User State files and folder.

 

Unable to Resolve: Loadstate from the same USMT package used to run Capture User State is not working as intended. Steps run through, but looking at the logs, this is all I can see:

 

ZTIuserstate.log

Microsoft Deployment Toolkit version: 6.1.2373.0 ztiuserstate 5/16/2013 4:23:02 PM 0 (0x0000)
The task sequencer log is located at X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log. ztiuserstate 5/16/2013 4:23:02 PM 0 (0x0000)
Checking for USMT Files in D:\_SMSTaskSequence\Packages\00200009\amd64 ztiuserstate 5/16/2013 4:23:02 PM 0 (0x0000)
Found USMT 4 executables. Using USMT 4 ztiuserstate 5/16/2013 4:23:02 PM 0 (0x0000)
About to run command: cmd.exe /c xcopy /iesryhd "D:\_SMSTaskSequence\Packages\00200009\amd64" "D:\_SMSTaskSequence\USMT\X64" 1>> X:\WINDOWS\TEMP\SMSTSLog\ZTIUserState_xcopy.log 2>>&1 ztiuserstate 5/16/2013 4:23:02 PM 0 (0x0000)
Command has been started (process ID 2028) ztiuserstate 5/16/2013 4:23:02 PM 0 (0x0000)
Return code from command = 0 ztiuserstate 5/16/2013 4:23:03 PM 0 (0x0000)
Migration XML file D:\_SMSTaskSequence\USMT\X64\MigApp.xml is already present and up to date. ztiuserstate 5/16/2013 4:23:03 PM 0 (0x0000)
Migration XML file D:\_SMSTaskSequence\USMT\X64\Migdocs.xml is already present and up to date. ztiuserstate 5/16/2013 4:23:03 PM 0 (0x0000)
Copying D:\_SMSTaskSequence\WDPackage\Scripts\UDIOffline.xml to local install directory D:\_SMSTaskSequence\USMT\X64 ztiuserstate 5/16/2013 4:23:03 PM 0 (0x0000)
Copying D:\_SMSTaskSequence\WDPackage\Scripts\ZTIUserState_Config.xml to local install directory D:\_SMSTaskSequence\USMT\X64 ztiuserstate 5/16/2013 4:23:03 PM 0 (0x0000)
Base arguments: /v:5 /c /o /i:"D:\_SMSTaskSequence\USMT\X64\MigApp.xml" /i:"D:\_SMSTaskSequence\USMT\X64\Migdocs.xml" /i:"D:\_SMSTaskSequence\USMT\X64\UDIOffline.xml" /config:"D:\_SMSTaskSequence\USMT\X64\ZTIUserState_Config.xml" ztiuserstate 5/16/2013 4:23:03 PM 0 (0x0000)
Property OSDStateStorePath is now = D:\StateStore ztiuserstate 5/16/2013 4:23:03 PM 0 (0x0000)
------ Performing State Capture ------ ztiuserstate 5/16/2013 4:23:03 PM 0 (0x0000)
USMT log file: X:\WINDOWS\TEMP\SMSTSLog\USMTcapture.log ztiuserstate 5/16/2013 4:23:03 PM 0 (0x0000)
USMT progress file: X:\WINDOWS\TEMP\SMSTSLog\USMTcapture.prg ztiuserstate 5/16/2013 4:23:03 PM 0 (0x0000)
Property OSDMigrateAdditionalRestoreOptions is now = /hardlink /nocompress ztiuserstate 5/16/2013 4:23:03 PM 0 (0x0000)
ScanState arguments: "D:\StateStore" /v:5 /c /o /i:"D:\_SMSTaskSequence\USMT\X64\MigApp.xml" /i:"D:\_SMSTaskSequence\USMT\X64\Migdocs.xml" /i:"D:\_SMSTaskSequence\USMT\X64\UDIOffline.xml" /config:"D:\_SMSTaskSequence\USMT\X64\ZTIUserState_Config.xml" /hardlink /efs:hardlink /nocompress /l:X:\WINDOWS\TEMP\SMSTSLog\USMTcapture.log /progress:X:\WINDOWS\TEMP\SMSTSLog\USMTcapture.prg /offlineWinDir:D:\Windows ztiuserstate 5/16/2013 4:23:03 PM 0 (0x0000)
ZTI Beginning user state capture ztiuserstate 5/16/2013 4:23:03 PM 0 (0x0000)
About to run command: cmd /c ""D:\_SMSTaskSequence\USMT\X64\scanstate.exe" "D:\StateStore" /v:5 /c /o /i:"D:\_SMSTaskSequence\USMT\X64\MigApp.xml" /i:"D:\_SMSTaskSequence\USMT\X64\Migdocs.xml" /i:"D:\_SMSTaskSequence\USMT\X64\UDIOffline.xml" /config:"D:\_SMSTaskSequence\USMT\X64\ZTIUserState_Config.xml" /hardlink /efs:hardlink /nocompress /l:X:\WINDOWS\TEMP\SMSTSLog\USMTcapture.log /progress:X:\WINDOWS\TEMP\SMSTSLog\USMTcapture.prg /offlineWinDir:D:\Windows > nul 2>&1" ztiuserstate 5/16/2013 4:23:03 PM 0 (0x0000)
Return code from command = 0 ztiuserstate 5/16/2013 4:25:40 PM 0 (0x0000)
ZTI USMT SCANSTATE reported 0 errors and 0 warnings. ztiuserstate 5/16/2013 4:25:41 PM 0 (0x0000)
ztiuserstate processing completed successfully. ztiuserstate 5/16/2013 4:25:41 PM 0 (0x0000)

loadstateprogress.log

16 May 2013, 17:13:11 -05:00, 00:00:00, program, loadstate.exe, productVersion, "6.1.7601.21645 (win7sp1_ldr.110119-1504)", computerName, ERICOM-WT-T430, commandLine, "C:\_SMSTaskSequence\Packages\00200009\amd64\loadstate.exe C:\StateStore /v:5 /c /l:C:\WINDOWS\CCM\Logs\SMSTSLog\loadstate.log /progress:C:\WINDOWS\CCM\Logs\SMSTSLog\loadstateprogress.log /i:C:\_SMSTaskSequence\Packages\00200009\amd64\miguser.xml /i:C:\_SMSTaskSequence\Packages\00200009\amd64\migapp.xml /hardlink /nocompress"

 

16 May 2013, 17:13:11 -05:00, 00:00:00, PHASE, Initializing

 

Can someone shed some light where I can start with my loadstate issues?

 

Thanks,

 

Eric

 

 

[67_dbc]

Anyone that can help?

 

I guess ultimately the question is do I have to specify if the USMT local path. If so, I currently have it set to %OSDStateStorePath% as the value. Is that correct or do I need to specify the actual C:\_SMSTS\StateStore as a valid response? Is that really my issue here?

 

Either way, I can't seem to get over this little bump in the road and it's making me go crazy over the fact anything I use with MDT doesn't work out-of-the-box setup.....

 

Any suggestions is greatly appreciated.

[englishjg]

Hi. I think I have the same basic issue. I have just started developing a migration. I store the user data and it seems like it is working, but nothing on the restored side. I am going to retest and watch it more closely this time. I have not tried hardlinking yet, I am storing the data on the user state migration point.

[67_dbc]

Manage to figure it out. I am running this task sequence using MDT with SCCM and it does not like that if you use it to capture and then use SCCM to restore user data. Well at least I couldn't do it that way and don't understand why. Also, I've determine that one my other issue that it can't create %machinename%\SetupUser local account. This must be a native account in which migration likes to keep. So when the steps run on Restore the process fails, the data doesn't restore. Thus, I included the /lac switch just above the Restore User Data steps and everything went smooth again.

 

SCCM is the most finicky product I've ever worked with and I tell you that small things like this seems to be a daily occurence constantly working out the basics....

[67_dbc]

Fixed all my issues by adding the /lac switch in my TS.

 

Once that was added, problems went away and restoring users like a charm without any issues

 

Eric