Hello,

sorry for not getting back to you sooner (two weeks of vacation, you know :P).

Thanks agauvrit, your solution seems to work!

Create an Organizational Unit into which you move the test WAPT deployment workstations.
It contains only the computer accounts, no...

So, if I understand correctly from the thread you linked, it's a problem with the computer's GPO not being able to be applied to a user. I therefore "duplicated" my GPO in User Configuration (see attached).
And now, the GPO is applied to the machine, but I have to log in as an administrator to...

We do indeed have Sophos on our machines, but after a quick look, nothing unusual appears to be happening.
Furthermore, my test environment doesn't have an antivirus program (nor an internet connection, for that matter), only a local network.
After running `gpupdate /force`, the GPO was applied to the client machine...

Thank you for your feedback.
I just tested both proposed solutions, and they both work; the client correctly connects to the WAPT server. However, the GPO does not work. (See attached image.)

The GPO is clearly separate from the other GPOs.

I had the same problem as Mika, but unfortunately, the solution of directly entering the WAPT server URL doesn't work...

After a `gpresult /h gpo.html & gpo.html`, I can see on my client (Windows 7) that it hasn't been applied (unlike a GPO for changing the background...).