Page 1 of 1
[SOLVED] Windows Deployment via USB Boot
Published: October 21, 2024 - 3:22 PM
by Nicolas19
Hello,
I've been having a problem since updating to WAPT version 2.5 while deploying Windows on my PCs.
My bootable USB drive works fine, but once I get to the WAPT interface, instead of the pop-up asking for the computer name, I get a pop-up asking for my username and password.
I recreated the bootable USB drive to make sure it was working correctly, but I'm still getting this login/password pop-up.
Do you have any idea what could be causing this?
Re: Windows Deployment via USB Boot
Published: October 21, 2024 - 5:58 PM
by sfonteneau
Hello
(There's no mention of the server type, so I'll assume you're using Linux.)
During the postconf session, a question is asked whether authentication is required for the OS deployment.
I assume you answered yes?
Simon
Re: Windows Deployment via USB Boot
Published: October 22, 2024 - 08:43
by Nicolas19
Hello,
First of all, sorry for forgetting this information in my post:
My WAPT server is indeed on Debian, but my console is on Windows 11.
I didn't have this problem with the previous versions 2.3 and 2.4, which is why I think this issue has been present since I upgraded to 2.5.
Could I have simply made a mistake or misclicked something during the update to 2.5?
Re: Windows Deployment via USB Boot
Published: October 22, 2024 - 09:40
by sfonteneau
Good morning
As mentioned in my previous post, you can restart the postconf.
Code: Select all
/opt/wapt/waptserver/scripts/postconf.sh
And to the question "Would you like to activate secure authentication on wads?"
You must answer no if you do not want authentication on wads
Re: Windows Deployment via USB Boot
Published: October 22, 2024 - 10:31
by Nicolas19
Hello again, and I'm truly sorry to have bothered you with this glaring error on my part.

While waiting for your reply, I restarted the postconf on my server and disabled WAD authentication, and wouldn't you know it... it works much better! -)
Thank you for your guidance and help, and sorry for wasting your time with this bug that wasn't actually a bug.
