MDT finishes then tries to log into Win10

[petben]

When we image a win10 1903 computer using MDT2013 the following happens:

 

Task sequence goes through, installs apps, joins domain etc and gets to its last step which is 'restart'

The computer then reboots and tries to auto log in as local administrator but fails with incorrect password.

 

Note

• We definitely don't want it logging in as local admin
  
• The local admin password it tries is correct anyway
  
• It has already logged in as local admin a few times during the task sequence anyway
  
• The MDT rules have FinishAction=REBOOT
  
• The HKLM reg key for AutoAdminLogin is set as 0.
  

 

 

 

Why is it trying to log in...?

Edited June 28, 2019 by petben

[computer_expert]

MDT 2013 doesn't look supported for anything newer than Windows 8.1/Server 2012 R2. I'd try upgrading to the latest version (8456).

 

Log in to the machine after the deployment has completed and check there isn't a (possibly hidden) folder called "_SMSTaskSequence" in the root of C:. If you have this folder left on the drive, it's more than likely that the build has failed for some reason (see the logs in the log folder).

[strawberry]

the finish action comes after teh summary is displayed and cleared unless you've set it not to..

[toffee_paul]

@petben we are having a similar issue here. The FinishAction is set to RESTART (same as REBOOT) and it all worked great in 1809 but 1903 is restarting then prompting for the local Administrator account password at the logon screen. Also it seems the local security group policy settings aren't taking effect. It must be a bug with 1903. We're running the latest 1903 ADK and WinPE addon.

[petben]

I stopped the auto login by removing the last action of the task sequence which was also a 'Restart', I cant remember if that was already there or I put it there, it now solely relies on the FinishAction to restart at the end.