WinPE - scanstate.exe is not compatible with the version of Windows you're running....
I am running WinPE 3.0 32-bit and working on a task sequence for WinXP 32-bit to Win7 64-bit upgrade scenario using SCCM OSD. For this I need to use scanstate.exe during WinPE to achieve an offline hardlink migration of data. When I run scanstate.exe in WinPE, I constantly get "scanstate.exe is not compatible with the version of Windows you're running....". I have tried both 32-bit and 64-bit versions of this file and get the same error message. The USMT scanstate.exe file has come from the WAIK, I have tried both version of scanstate.exe (amd64 and x86) from inside the C:\Program Files\Windows AIK\Tools\USMT directory. The executable version is 6.1.7601.21645. Anyone else seeing this?
November 19th, 2011 7:56pm
Hi danovich_, From your description, you are using USMT 4.0 hardlink feature to migrate data from windows xp 32bit to windows 7 64bit. Have you created your USMT package correctly? The USMT package's source should only navigate to and select C:\Program Files\Windows AIK\Tools\USMT folder. Do not directly select either the amd64 or x86 folders. When running, the Task Sequence will automatically choose the appropriate binaries. And verify it was updated to DP correctly. Also USMT 4.0 is supported for SCCM 2007 sp2. Have you tried to add both 32 and 64 bit winPE image to the DP? Check the scanstate.log file. And to use hardlink of USMT in SCCM task sequence, there are tricks to create the task sequence to support hardlink migration. OSDMigrateAdditionalCaptureOptions and OSDMigrateAdditionalRestoreOptions variables are the key point. Here is a very good article about how to use USMT 4 hardlink in sccm: http://blogs.technet.com/b/configurationmgr/archive/2010/06/30/how-to-use-usmt-4-hardlinking-in-a-configuration-manager-2007-task-sequence.aspx Also here are some other references: http://www.windows-noob.com/forums/index.php?/topic/1633-sample-xp-to-windows-7-task-sequences/ http://technet.microsoft.com/en-us/library/dd560803(WS.10).aspx Hope this will help. Thanks
November 20th, 2011 12:01am
I've just realised what I did - I applied this USMT 4 hotfix - http://support.microsoft.com/kb/2023591 - but I only downloaded the x64 version of it and copied those files to both (amd64 and x86) subfolders. I needed to download both versions of the hotfix and copy the correct versions to the correct subfolders!
November 20th, 2011 3:25am