*Not recommended in Prod, this creates a local account with password, password is in plain text in the TS, Scheduled Task & Registry.
Update 2018/11/09 – After the discovery yesterday of how OOBE removes those AutoLogon Keys, I’ve created a Scheduled task that I add during OSD that adds the keys post OOBE. It’s pretty ugly, but it works. Basic idea: Scheduled Task adds the keys, removes the task, and reboots the machine after 5 minutes. Trigger: Machine Turns on. See more below.. All in all, it adds about 20 minutes onto the process, but you can tweak the reboot delay and shave off a few minutes.
Update: 2018/11/08 – This no longer works with new versions of Windows 10. During OOBE stage (Post Task Sequence, Pre First Logon), the OOBE process deletes two keys: “HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon” Values: DefaultUserName & AutoAdminLogon If you have it skip OOBE in your unattend.xml, it works, however that setting is deprecated.
Original Post:
I added a local admin account (Non-Domain) that autologon’s on to the computer after OSD purely to speed up my testing. This way I don’t have to wait for First Logon, after OSD, it will reboot, then autologon as the account I’ve Created.
Make sure you add the SMSTSPostAction to reboot, so you don’t get that Group Policy Error the first time you try to logon. (As explained by Niall)
I’ve created a Task Sequence Variable at the start of the TS, that allows you to trigger the AutoLogon Group. Simple Enable or Disable this step to have the Group run.
Read more