MDT2012 will not Capture/Sysprep from within Windows using the default Capture Sysprep TS. Receiving Exec Sysprep failure message "Incorrect Function". Originally my issue was related to a deployment failing the State Restore phase, but I tracked it back to a failed Sysprep after the update to MDT2012.
Below is my original post and findings...
--------
Since I upgraded to 2012 I recently noticed my that my captures do not display the "task sequence finished successfully" message and that my C: drive still had files _SMSTaskSequence or w/e it's called still present. I also had to modify
my capture task sequence adding a registry entry for Clonetag, or my sysprep would fail in a few seconds. The capture appears to be working now however...
Regarding the State restore issue, here I am 1 week later having tried everything except uninstalling MDT from the server starting from scratch. Most recently I modified my image to reset all Domain policies at the possibility that CTRL+ALT+DEL or
the Legality message was preventing auto-login. So I assume the system has to have autologin to be able to execute LITETOUCH.WSF...or wait, was it LTIBootstrap.vbs??? That's certainly the question...I'm comparing a functioning TS/Unattend.xml created under
MDT2010 that references "cscript.exe C:\MININT\Scripts\LiteTouch.wsf /start in the Unattended file . This is located in step 7 oobeSystem (edited through the deplyoment work bench). Now in the new Unattend.xml I see: "wscript.exe %SystemDrive%\LTIBootstrap.vbs"
in the same place. Anyone know what's going on with the different file references? The .vbs does appear to be one of the files left over sitting on the C: drive. I'm desperate for a solution so I just built a task sequence that references the .WSF file for
giggles. Nextup I'll but all of the references in there however I'm still thinking that the auto-login is not processing correctly. Any ideas?