Hey everyone! I've recently taken over a network that's configured to use Windows Deployment Services (WDS) on a Windows Server 2019 setup. This network is limited to specific VLANs, and I've got a new PC that can PXE boot into WDS. However, I hit a snag after it prompts me to select the keyboard and language. At that point, it's asking for domain credentials. I've tried using both 'domain\username' and 'domain.com\username' but keep getting an error that says, "A login attempt failed due to incorrect credentials (bad password error) hour restrictions, or policy enforced." I can log into the domain controller without a hitch using my admin credentials, and the same goes for another computer on the same VLAN. So I know my login info is right. I suspect there might be policy restrictions at play, but I can't find anything in the GPOs related to WDS. There might also be some STIG settings causing issues, but I can't reach out to the previous admins for clarification. Any advice from this community would be a lifesaver! Thanks for reading!
3 Answers
Just a thought—are you sure the PC is part of the domain? Since you're using an older setup, it's possible that the device is in a workgroup instead. And don't forget if there are unattend files from previous deployments that could help with the process!
First off, avoid using 'domain.comusername'—that format won’t work. It's crucial to check what permissions the account you're using has. Make sure the computer object is properly created in the domain. Also, have you tried connecting remotely to the event viewer to look for any clues? Trying a local account to see if that helps might be worth it too.
Sounds like there's a good chance that NTLM authentication is disabled or restricted in Group Policy. While it's good for security, it can complicate WDS authentication, so definitely look into that!
Thanks for the tip! I'll prioritize checking on that first thing on Monday.

Good call! I'm currently using a domain admin account, but the PC isn't joined to the domain yet since it doesn't have an image installed. I'll check the event logs tomorrow and confirm the computer object status.