MDT 2012 - Image failing during system restore - C:\LTIBootstrap still there. Autologin not happening.

Question

Hello,
I'm hoping someone can assist.  I have an image that was working but the builtin admin account was disabled.  I went into the image and enabled the account and set a password.  I ran sysprep and capture.  Now, when i try to deploy either
image, it installs the OS, reboots and then sits at a login (does not go into the admin account to continue).  I login and i notice that LTIBootstrap.vbs is sitting on the root of c along with the Minint folder and other MDT folders.  I have MDT
on 2 servers and they both do the same thing.  Unattend.xml in c:\minint has the correct local admin/password
Customsettings.ini:
[Settings]
Priority=Default
Properties=MyCustomProperties
[Default]
DeployRoot=\\ourserver\D$\DeploymentShare$
ComputerBackupLocation=Network
Home_Page=http://home
OSInstall=Y
SkipAdminPassword=YES
SkipApplications=YES
SkipAppsOnUpgrade=YES
SkipBDDWelcome=YES
SkipBitLocker=YES
SkipComputerName=YES
OSDComputerName=HDQ-%SerialNumber%
SkipComputerBackup=YES
SkipDeploymentType=YES
SkipDomainMembership=YES
JoinDomain=OurDomain
DomainAdmin=xxxx(Account with Join domain rights)
DomainAdminDomain= Our Domain
DomainAdminPassword=Password for account
SkipAdminAccounts=YES
SkipFinalSummary=NO
FinishAction=Reboot
SkipLocaleSelection=YES
KeyboardLocale=en-US
UserLocale=en-US
UILanguage=en-US
SkipPackageDisplay=YES
SkipProductKey=YES
SkipSummary=No
SkipTaskSequence=NO
SkipTimeZone=YES
TimeZoneName=Eastern Standard Time
SkipUserData=YES
EventService=http://OurServer:9800
[Settings]
Priority=Default
[Default]
DeployRoot=\\OurServer\D$\DeploymentShare$
UserID=account to join to domain                                                                                                                  
USerDomain=Our Domain
UserPassword=Account password to join domain
Any help would be greatly appreciated.
Thanks
Rick
BDD.LOG
<![LOG[ZTINextPhase COMPLETED.  Return Value = 0]LOG]!><time="14:10:58.000+000" date="01-13-2014" component="ZTINextPhase" context="" type="1" thread="" file="ZTINextPhase">
<![LOG[ZTINextPhase processing completed successfully.]LOG]!><time="14:10:58.000+000" date="01-13-2014" component="ZTINextPhase" context="" type="1" thread="" file="ZTINextPhase">
<![LOG[Event 41001 sent: ZTINextPhase processing completed successfully.]LOG]!><time="14:10:58.000+000" date="01-13-2014" component="ZTINextPhase" context="" type="1" thread="" file="ZTINextPhase">
<![LOG[Command completed, return code = -2147021886]LOG]!><time="14:10:58.000+000" date="01-13-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property LTIDirty is now = FALSE]LOG]!><time="14:10:58.000+000" date="01-13-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[If there is a drive letter defined, make sure we clear it now so we can *force* recalcutation.]LOG]!><time="14:10:59.000+000" date="01-13-2014" component="LiteTouch" context="" type="1" thread=""
file="LiteTouch">
<![LOG[Property OSDTargetDriveCache is now = DIRTY]LOG]!><time="14:10:59.000+000" date="01-13-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[LTI initiating task sequence-requested reboot.]LOG]!><time="14:10:59.000+000" date="01-13-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Event 41017 sent: LTI initiating task sequence-requested reboot.]LOG]!><time="14:10:59.000+000" date="01-13-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">

Answer 1

Hi Rick,
To my understanding, sysprep and to be more specific the "gerenalize" step will make sure all personalized information will be removed before entering the capture mode.
I'm aware additional created account's will be preserved, but I can't tell you about the built-in administrator account.
The first thing that comes to mind is that, your Build task sequence uses a Unattend.xml, just the same as your Deploy task sequence does this.
Assuming that you don't do anything you haven't mentioned with the account in the task sequence, like renaming the admin account or setting a different password during the task sequence. Cross checking both your Unattended.xml would be a good place to start.
Also, it is known, that Windows allows the machine to be auto logged on, a couple of times. So please check if this isn't also the case. See this link for more info: http://support.microsoft.com/kb/324737
Lastly if all else fails, you can set the account enabled, and a password by commandline, but this should only be done as a temporarily work around. See these links for more information: http://support.microsoft.com/kb/251394 and http://social.technet.microsoft.com/wiki/contents/articles/3040.enable-disable-the-local-hidden-built-in-administrator-account-in-windows-7.aspx
Good luck!
If this post is helpful please click "Mark for answer", thanks! Kind regards