KACE Product Support Question
Windows 10 1709 Domain Autologon
12/10/2017 7413 views
I've seen a few similar questions floating around here, but I've tried all the steps on them and haven't been able to come up with anything that works.
Trying to set up my Scripted Installations on the K2000 so that the laptops automatically join the domain during the installation process and then auto-login so that they can finish the build as a domain-joined laptop.
This was previously never an issue with Windows 7 - our Powershell script would run and the laptop would join the domain and continue auto-logging in without any issues.
However with Windows 10, the AutoLogin function breaks as soon as the laptop joins the domain. I cannot put this post-install task at the very end of my task list as the default Restore UAC and Cleanup tasks must finish after it. I also run a script that clears the last login so the imaged laptop shows as if it has never been logged into before for the user who receives it.
I'm adding the following registry values during the install process (as a .BAT script):
reg.exe add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinLogon" /v AutoAdminLogon /d 1 /f
reg.exe add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinLogon" /v AutoLogonCount /t REG_DWORD /d 10 /f
reg.exe add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinLogon" /v DefaultDomainName /d our.domain /f
reg.exe add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinLogon" /v DefaultUserName /d user.name /f
reg.exe add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinLogon" /v DefaultPassWord /d password /f
As soon as it restarts after performing our domain join task the machine stops auto-logging in. I can see the registry keys sitting there after the restart (and manually logging in).
I've even added these keys manually once it has been domain joined and restarted it with no joy.
Does anyone have any extra information about how to get this working so I can configure my Scripted Installations like Windows 7?
Answer Chosen by the Author
Please log in to answer
Alright everyone... turns out it was a GPO that was causing my issue. I had a GPUpdate task running before my AutoLogon and my domain join task - moving that to the end of the queue means it's worked fine!
Now to track down the GPO that is causing my problem... I suspect it might be to do with wireless login or something along those lines.
Thanks all for your help!
Answered 12/13/2017 by: onionst