Hello,

for upgrades you have the "waptupgrade" package which allows you to update the wapt agent itself

* A dedicated interface for post-installation clients (IP: 192.168.0.1);
* A second interface dedicated to WADS/PXE deployments (IP: 192.168.100.1).


This setup is not very practical and is not recommended because it will cause several problems when the workstation changes VLANs...

Can you tell me if booting from a WinPE USB drive works?

If you have a keytab file, it means there was a wapt account in Active Directory at some point.

You can delete the keytab and run postconf to force its re-creation (be careful not to delete the machine account afterward ).

The problem is this... apparently you are using Kerberos but you don't have a WAPT machine account in your Active Directory.

Do you have a /etc/nginx/http-krb5.keytab file on your WAPT server?

Apologies for the error in my previous message:

I'll correct it:

Can you verify that the machine account in your Active Directory server still exists?

If so, what is the value of the ServicePrincipalName attribute?

Good morning
Can you verify that the machine account in your wapt server still exists?

If so, what is the value of the ServicePrincipalName attribute?

Isn't 192.168.1.11 listed in /etc/hosts? (bad configuration)

Kinit is trying to connect to 192.168.1.11...

What is the server's IP address?

Can you tell me what this returns on the WAPT server?

https://www.wapt.fr/fr/doc/wapt-securit ... -with-curl

Could you also tell me what type of server you have? Red Hat? Alma? Debian?