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?
[SOLVED] Windows Deployment via USB Boot
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
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
(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
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?
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?
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Good morning
As mentioned in my previous post, you can restart the postconf.
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
As mentioned in my previous post, you can restart the postconf.
Code: Select all
/opt/wapt/waptserver/scripts/postconf.shYou must answer no if you do not want authentication on wads
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.
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.
