You're not alone Mike, I ran into the same thing testing today and thanks to your post I know what to fix.
From: [email protected] [mailto:[email protected]] On Behalf Of Marable, Mike Sent: Wednesday, August 19, 2015 8:26 PM To: [email protected]; [email protected] Subject: Re: [MDT-OSD] RE: MDT 2013 Update 1 - Build Failing During oobeSystem Sure enough, if there's one specific scenario that one can shoot themselves in the foot, I'll find it. :) I did exactly those three steps. * When I set up MDT initially I set an admin password through the wizard. * I did edit the unattend.xml * I do have an admin password set in the [Default] section of my CustomSettings.ini Shot myself in the foot I did. At least I'm not crazy and imagining it. Thanks for taking the time to look into it Michael. Thanks Mike From: <[email protected] <mailto:[email protected]> > on behalf of Michael Niehaus <[email protected] <mailto:[email protected]> > Reply-To: "[email protected]" <[email protected] <mailto:[email protected]> > Date: Wednesday, August 19, 2015 at 5:59 PM To: "[email protected] <mailto:[email protected]> " <[email protected] <mailto:[email protected]> >, "[email protected] <mailto:[email protected]> " <[email protected] <mailto:[email protected]> > Subject: [MDT-OSD] RE: MDT 2013 Update 1 - Build Failing During oobeSystem I tried it and it worked fine. But I didn't give up like most auto mechanics do :) So I was able to reproduce the error in one specific scenario: * Create a task sequence through the MDT wizard, specifying an admin password (saved as plaintext in the Unattend.xml). * Edit the Unattend.xml and save it (you don't need to change anything, just save). * Deploy with either the admin password wizard pane enabled (SkipAdminPassword=NO) or a non-blank AdminPassword variable value (specified in CustomSettings.ini, database, etc.). In this particular case, MDT injects the value of AdminPassword into the Unattend.xml but doesn't reset the plaintext value. Definitely a bug. Thanks, -Michael From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Marable, Mike Sent: Wednesday, August 19, 2015 11:26 AM To: [email protected] <mailto:[email protected]> ; [email protected] <mailto:[email protected]> Subject: [mssms] RE: MDT 2013 Update 1 - Build Failing During oobeSystem I just hope this isn't like when my car is making a funny noise that stops once the experts are looking at it. :) Mike From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Michael Niehaus Sent: Wednesday, August 19, 2015 2:19 PM To: [email protected] <mailto:[email protected]> ; [email protected] <mailto:[email protected]> Subject: [MDT-OSD] RE: MDT 2013 Update 1 - Build Failing During oobeSystem Odd. But at least that should be easy to repro, trying that now :) Thanks, -Michael From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Marable, Mike Sent: Wednesday, August 19, 2015 11:16 AM To: [email protected] <mailto:[email protected]> ; [email protected] <mailto:[email protected]> Subject: [mssms] RE: MDT 2013 Update 1 - Build Failing During oobeSystem Yes it is the only difference. I went back to my original XML file and using Notepad replaced the "Value" and "PlainText" settings, re-ran the build and it completed successfully. Same task sequence (factory default client sequence) if I use my unattend with the encrypted passwords it fails. If I replace those fields with plain text versions it succeeds. Thanks Mike From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Michael Niehaus Sent: Wednesday, August 19, 2015 1:58 PM To: [email protected] <mailto:[email protected]> ; [email protected] <mailto:[email protected]> Subject: [MDT-OSD] RE: MDT 2013 Update 1 - Build Failing During oobeSystem MDT would by default insert a plain-text password. WSIM definitely encrypts passwords it finds in the file when it is saving. But MDT shouldn't care that is happening. Is that the only difference that you are seeing in the Unattend.xml? Thanks, -Michael From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Marable, Mike Sent: Wednesday, August 19, 2015 5:34 AM To: [email protected] <mailto:[email protected]> ; [email protected] <mailto:[email protected]> Subject: [MDT-OSD] MDT 2013 Update 1 - Build Failing During oobeSystem This bit me yesterday when I was testing task sequences after upgrading to MDT 2013 U1. My existing Windows 7 builds were failing. If I created a brand new task sequence the build would complete. So I compared my original Unattend.xml with the factory default and found that the passwords in my original were not in plain text while those in the default were. When I was running MDT 2013 (RTM) I modified the XML through the MDT console (triggering Windows System Image Manager) to set the "ProtectYourPC" to disable auto updates. That was the only change I made. I'm guessing that WSIM set the value to encrypt the passwords by default? Anyway, does MDT 2013 U1 have issues with encrypted passwords in the XML? Mike Marable Microsoft Systems Engineer Lead Enterprise Device Engineering and Management MCPS, MCITP, MCTS, MCSA, MCSE, MS [ <http://www.mycertprofile.com/Profile/5319166625> Profile] [ <http://thesystemsmonkey.wordpress.com/> Blog] ---------------------------------------------------- "The difficult we do at once. The impossible takes a little longer." -US Army Corps of Engineers "It is better to have less thunder in the mouth and more lightning in the hand." -Apache Proverb I will rise when I have fallen. "Unless you try to do something beyond what you have already mastered, you will never grow." -Ralph Waldo Emerson ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues
