MDT 2012 - Auto login settings were gone at the end of the deployment

Question

I need to make some PC for public use (Has a local user account that no need to login)
There's no problem for me to created the local user account and and its profile folder by using custom tasks.
The auto login settings also successfully set by modify the registry or use Sysinternals - Autologon.exe
But after the last restart of th PC (I set to restart at the end of the deployment), Windows stuck at the login screen.
Then I found that all the auto login settings were gone (Both in the registry and netplwiz).
Since this custom task is place near the end in the Task sequence (which means there should be no other task that can influence it). So, I suspect may be the Group Policy reset all those settings.

Answer 1

I had the same problem, and these were my solutions:
Comment out the relevant lines in LTICleanup. I tried to avoid this, in case any updates to MDT reversed the change. Also even if I documented it, it might not be apparent to another technician years down the line. I prefer to leave the MDT files unchanged.
Create a script that runs after the task sequence has completed. This is the option I chose, and it was a bit more complicated than it appeared.
What I did was as follows:
Create a new AutoLogon Script application.
The "application" must consist of two script files: install and autologon.
The "install" script does the following:
Copy the "autologon" script to a temporary folder on the local drive
Create a new scheduled task which runs on startup, as the SYSTEM user, and runs the "autologon" script (using schtasks.exe)
The "autologon" script does the following:
Create the relevant registry keys to enable automatic logon.
Delete the above scheduled task.
Reboot the workstation.
In the MDT task sequence, create a new task at the very end, which installs a single application. Choose the AutoLogon Script application.
In your CustomSettings.ini, set FinishAction=REBOOT
So at the end of your task sequence, the workstation will reboot. It will then run the autologon script after boot up, but will not autologon. When the script finishes, it will reboot again, at which point it will autologon with the details you specified.
It's a little fiddly, but works for me.
Johan Arwidmark has another method here, which might be even easier - http://www.deploymentresearch.com/Research/tabid/62/EntryId/122/Final-Configuration-for-MDT-2013-Lite-Touch-now-with-Autologon-support.aspx