Tranquil IT Forum

Hello,

WAPT version: Debian server WAPT 1.5 RC1 community.

I have a problem with the new version of WAPT: My clients don't automatically connect to the server after the agent is installed. I have to type the command `wapt-get register`.
What is the cause and is there a way to fix it?

(Client workstations are running Windows 10, registered on our Active Directory server.)

Thank you
.

Can you specify your configuration?

Kerberos authentication?
Basic authentication?
No authentication (like version 1.3)?

Without authentication (like version 1.3)

If the agent fails to send its inventory, it attempts a register. I just tested it, and it works.

Can you provide the wapt-get.ini file for your agents?
Is antivirus software installed on the workstations?
Is the WAPTService running correctly on the workstation after installation?

Sorry, I had a big problem to fix last week and couldn't get back to WAPT.

Anyway, thanks to your questions, I was able to solve the problem: in the wapt-get.ini file, the server's .crt certificate wasn't at the correct address (it was looking for it in the administrator's roaming profile).
I regenerated an agent with the correct parameter: C:\Program Files (x86)\wapt\ssl\server\waptsrv.mydomain.fr.crt, and now everything is working perfectly.

However, the "agent generator" had apparently used this address by default (or perhaps I had changed it and I don't remember?).

Thanks
!

To avoid this kind of problem, we have implemented a security measure in version 1.5.1.21