It was actually my antivirus that had messed up the initial installation, but I hadn't been notified of the error. After uninstalling and reinstalling, it works.

I had to format the server because it wasn't working even without my antivirus.

Hello everyone,

I'm tearing my hair out trying to install the WAPT server; I just don't understand it. I'm running Windows Server 20019, and despite reading numerous posts on the subject and following recommendations (stopping services/deleting files), I've reinstalled it several times. I'm still getting a "Bad Gateway" error...

After testing... the GPO isn't working, but I have several leads. For example, the administrator account is disabled on the domain, and a third-party user is a domain admin; could that make a difference?

As a reminder, here's the link in my GPO for WAPTDEPLOY and then the...

I didn't test the deployment via GPO, only using the BAT command, which explains why it asked me for installation validation (user account control).

I'm testing the deployment via GPO now.

I'm answering my own question; by rebuilding the WAPT agent, the correct configuration can be redeployed via GPO and WAPTDEPLOY.

Now I still need to authorize it in User Account Control; if I find a solution, I'll post an update here.

Hello again,

I think I've found the problem. I installed it on an IP range like 192.168.21.** and when I use waptdeploy (after changing the workstation's IP address), the configuration that's sent to the PCs on the network is on the original IP address (192.168.21.**), however, if I go to...

Good,

I have access, it works (small firewall error and server name corrected) but I still have another problem....(I'm such a klutz you'll say ^^).

So the server absolutely has to be called wapt?

That would explain why. My server is srv-deploy.

I'll try renaming it. I'll keep you posted.

Hello,

I just re-entered the hash as indicated in my documentation (something I did the first time) and here's the output:

deploy.PNG.

For your information, here's the hash I have on my deployment server (it's not the same as the domain controller server; does that change anything?).

Good morning,

I made the changes indicated, and now I get the following feedback: