Manually, Open a CMD prompt, in the CMD prompt type Control Userpasswords2 , the first checkbox you see check it. [X] Users must enter a username and password to use this computer.
registry item is:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\AutoAdminLogon
Just as i figured, set to 0 and autologin is disabled, set to 1 and (this is bad) it is re-enabled fully. Tested.
why is that bad? because initialy I had put in a Password that will be used to access the the admin account automatically. By changing ONLY this one registry entry, the AutoPassword is still in the system.
Logically by using the GUI interface, the AutoPassword stored would be removed.
Tested, my hunch was right, the GUI method did remove the AutoPassword, and I was unable to autologin without a password, Via just changing the registry item.
I was still able to get in after Password error, by supplying the password, after the stored autopassword was removed.
With the registry change, that still leaves removing that protected storage item, the password??
Or a Psudo Admin user (or virus) could set that back to auto pretty quickly, and you should know that.
Side Notes: Also depending on the install, the admin should also be renamed, passworded , and even re-disabled if nessisary for the intended application. if the admin was re-passworded, the stored Auto password should become useless.
I do not really know enough about it, just tested theory.
1
You might want to keep an eye on my question: http://superuser.com/questions/340396/how-do-i-change-user-logon-password-requirements-via-script-or-command-line
– Joe Taylor – 2011-09-30T09:00:48.147MDT sets an autologin when deploying the OS, if it's not turning off the autologin at the very end, something is wrong. Answer below is just a Band-Aid, not a solution to the root cause. Check you MDT log files and determine what is causing MDT to not turn this off like it should. – MDT Guy – 2013-11-05T22:21:40.850