Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, December 14, 2017 7:50 PM
Greetings all.
We've discovered a strange issue, possibly a new bug with our domain Windows 10 devices.
Quick and dirty; Domain devices requiring AutoAdminLogon work fine, EXCEPT for one model device, Dell 3020m
DETAILS:
We use the same Windows 10 image (version 1703 build 15063.726), deployed via MDT for every device in our office.
A few devices used randomly by multiple persons require AutoLogon (please omit 'security issue' responses, we are aware...)
Recently we re-imaged a Dell 3020m to be Win10 and setup the auto-logon and we are met with this:
https://i.imgur.com/V8a3iC7.png [Seems my account is 'unverified' after having it for three years..]
Instead of logging in (as any other model device) we get this 'Phone number or email' prompt. **ONLY **only the Optiplex 3020m do we see this. We've verified the REG:
https://i.imgur.com/ThgLY5l.png
The REG is identical to a verified working device (obviously, credentials are 'fake' for security reasons)
And here's the kicker: If we set *AutoAdminLogon *to 0, the 'Phone or email' prompt goes away, but of course it also doesn't log on.
Do ANY of you know what would cause this on the Dell Optiplex 3020m?
Additional Information
Works fine on these devices:: Dell Optiplex 7020 - 5040 - 5050 AND Dell Latitude e5440 - e5470 - 5480
We have tried 8 different user accounts
Verified that these devices are not in any different OU than the other models
These are all DOMAIN devices, therefore control userpassword2/netplwiz will not work to store credentials.
All replies (10)
Friday, December 15, 2017 3:58 AM
Hi,
Based on your description, it seems that this issue only occurred on this Dell 3020m computer.
Have you tried to reset this computer and check the result?
If the issue still persists, I’m afraid you may need to contact Dell support for further help.
Best Regards,
Tao
Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact [email protected].
Friday, December 15, 2017 6:42 AM | 1 vote
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
"DefaultUserName"="USERNAME"
"DefaultDomainName"="DOMAIN"
"DefaultPassword"="PASSWORD"
"AutoAdminLogon"="1"
This is all that you need.
https://www.tenforums.com/tutorials/3539-sign-user-account-automatically-windows-10-startup.html
http://expert-advice.org/windows-server/how-to-set-up-auto-login-windows-server-2012-and-2016/
Monday, December 18, 2017 1:08 PM
W've re-imaged it around 5 times as well as updated BIOS..
Monday, December 18, 2017 1:08 PM
Yes, as i've said we have Auto-Logon working fine on every other model PC in the building (that requires it)
Wednesday, December 20, 2017 7:40 AM
Hi,
We haven’t heard from you for a couple of days, have you solved the problem?
Best Regards,
Tao
Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact [email protected].
Wednesday, December 20, 2017 12:46 PM
Sadly no. I was hoping for other suggestions as those posted have been tried
Friday, April 27, 2018 4:40 AM | 2 votes
I believe the wireless adapter is causing the issue.
To test, I disabled the wireless adapter and connected directly to LAN cable. Autologon has worked every time. I enabled the wireless adapter and chose an alternate wireless connection and the issue went away. Hopefully in some way this information can help someone else.
Wednesday, April 3, 2019 10:07 PM | 1 vote
Hi,
I banged my head on this one for a while, so I figured I would share our solution. Windows 10 autologon was not working. The autologon account would be prompted to enter an email address whenever autologon was enable. We had an 802.1x policy that was causing the issue. On the Security Tab, under advanced; we changed the Single Sign On behavior from "Perform immediately before User Logon" to "Perform immediately after User Logon".
I hope this information helps someone out there.
Cheers!
Thursday, April 25, 2019 6:58 PM
This was the issue with mine as well. Thanks!
Friday, June 28, 2019 1:43 AM
If you want to use autologon and enable wifi connection perform before Windows logon, you should not connect any wired LAN cable. I found that pre-logon-Wifi with a wired LAN connection will recreate this issue. e.g. You have a laptop PC with WiFi usually use WiFi only, make sure LAN cable unplugged and reboot when you want to make it autologon and leave and ignore the strange email/phone message for 20~30sec, your machine will do autologon to domain.
Tanomaki