Tranquil IT Forum

Hello,
I created a GPO on my server to deploy the WAPT agent to an OU. I followed the tutorial:
Create the deployment GPO with WAPTdeploy.

It doesn't work.

So I downloaded waptdeploy.exe to a client and ran the following command (in cmd):

waptdeploy.exe --hash=2xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx7 --minversion=1.4.2.0 -- waptsetupurl=http://mywaptserver/wapt/waptagent.exe --wait=15.

This works, but it asks me for a password at the end of the installation. I enter it, and my machine appears in the console.

Is this password the problem when trying to use GPOs?
If so, how can I work around this issue?


Thank you

, F. Carré

Hello CARRE-FRED,

CARRE-FRED wrote: ↑June 5, 2019 - 8:13 PM I created a GPO on my server to deploy the WAPT agent to an OU. I followed the tutorial:
Create the deployment GPO with WAPTdeploy.

It doesn't work.

So I downloaded waptdeploy.exe on a client and ran the command (in cmd):

waptdeploy.exe --hash=2xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx7 --minversion=1.4.2.0 -- waptsetupurl=http://mywaptserver/wapt/waptagent.exe --wait=15.

It works, but it asks me for a password at the end of the installation. I enter it, and my machine appears in the console.

Is this password the problem when trying to use GPOs?
If so, how can I work around this problem?

If during server installation you selected login/password authentication or you selected domain-based Kerberos authentication but the Kerberos configuration is not done correctly, then yes, this is the expected behavior.

If you accept automatic registration without pre-authentication, restart postconf [1] and select simple registration as in wapt 1.3. Otherwise, you need to configure kerberos correctly.

Sincerely,

Denis

[1] https://www.wapt.fr/fr/doc/waptserver-i ... onfiguring