SYSPREP and CAPTURE Windows SP1 with the WAIK Supplemental for SP1

The question has been asked multiple times in multiple ways, but am still confused WHY?

Anyways, I've had no problems in the past year?with MDT 2010.? Great product IMO; however, ever since I created a new MDT server with the SP1 and the newest WAIK and supplement for SP1 Ive had nothing but problems with SYSPREP and Capture.? So, I've been digging into the issue more.? Yes, I've read the technical "issue" for the boot WIM (thank you Mike!) and have seen the problems with the clone tag, and have experienced may authenication issues and resolved them figuring out why there were problems.? However, my confusion lies in a recent attempt to make things work right.?

Im a domain admin, verified I can access everything over the network with and without domain connectivity, and ensured I have full permissions on the MDT server (of course I do ... lol)? Interesting thing is I get the following LTI failure

SO, I examine the logs and I check the TS to ensure nothing is changing my permissions; which there isn't.? So after several more attempts and more failiures I decided why not just put my domain account in the TS TEP APPLY WINDOWS PE "Run this step as the following account".

Well, needless to say, it works fine; works as it did prior to SP1 for Windows 7.

But please, anyone ... explain WHY.? It was me on the server who created the TS; it was my account who authenicated over the network to connect to the MDT server; and it was my account I used to authenicate the process initiation of the MDT task.?

So, why, the APPLY WINDOWS PE task not getting the authenication to proceed?

Thank you for your patience.

Source: http://social.technet.microsoft.com/Forums/en/mdt/thread/265f7c92-2d5b-43cd-9d52-21141cbbe249

st.louis cardinals st.louis cardinals drag me to hell alot alot are you afraid of the dark are you afraid of the dark