I like my chances when Michael Niehaus provides a stab-in-the-dark guess. It was the computer name! Thank you!
Brian From: [email protected] To: [email protected] Subject: RE: [mssms] Win7 setup fails using MDT integrated TA Date: Thu, 29 May 2014 01:15:27 +0000 My complete stab-in-the-dark guess is that MDT injected a bad computer name (maybe too long?), but you told it to do that J To confirm if that’s really the case, you should look at the setupact.log or setuperr.log yourself. It will tell you the exact entry in the unattend.xml that was bad. Thanks, -Michael From: [email protected] [mailto:[email protected]] On Behalf Of Brian McDonald Sent: Wednesday, May 28, 2014 6:00 PM To: [email protected] Subject: [mssms] Win7 setup fails using MDT integrated TA I have a TS that fails when using an MDT integrated TS, but not when I use an SCCM only TS. Same .wim file used for both sequences. IF deployed with SCCM only TS then OS applies with no errors. IF deployed with MDT/SCCM TS then Apply Windows Setting step fails. I reboot the client and enters setup then I get the following error: Windows could not process the unattend answer file for pass [specialize]. The settings in the answer file cannot be applied. The error was detected while processing settings for component [Microsoft-Windows-Shell-Setup] Why would the MDT integrated approach cause setup issues? :) Thanks, Brian Sent from my iPhone
