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 then have a group which runs all of the commands individually. You could easily put this into one batch file, I just like to do it this way, self documenting, and requires no content. The group is set to run if the Task Sequence Variable “AutoLogon” = True
I then have 7 “Run Command line” Steps, creating the User and registry keys.
- Tweak – AutoLogon - Create Tony Stark Account
- Tweak – AutoLogon - Tony's Password Never Expire
- Tweak – AutoLogon - Make Tony Admin
- Tweak - AutoLogon - Key DefaultUserName
- Tweak - AutoLogon - Key DefaultPassword
- Tweak - AutoLogon - Key AutoAdminLogon
- Tweak - AutoLogon - Key DefaultDomainName
- Optional: Add two Steps to remove the Legal Notice Prompt (If you have it in your lab, GPO will probably put it back)
- REG DELETE "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System" /v legalnoticecaption /f
- REG DELETE "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System" /v legalnoticetext /f
After TS finishes, it will reboot and start the logon process automatically. Now you can start your testing.
You can change this to fit your needs, use a domain account in your Lab, just change the steps, as you won’t need 1-3 to create the account, and change step 7 to the Domain Name (Contoso, ViaMonstra, etc) instead of %computername%
Please Note, this is sending the information in Clear Text, and will be available in logs, etc. Probably fine for your lab, not a good idea for production. Please don’t say “Hey Boss, don’t worry about it, it’s totally cool, Gary does it!”