[SOLVED] Missing binary 'waptagent.exe' on WAPT server

[apache]

Hello everyone,

I am currently testing wapt Discovery version 2.3. I installed the server in 2.3.0.13516 on an Ubuntu machine and I would like to deploy the agents on Windows machines.
However, I am unable to locate the installation binary for the 'waptagent.exe' agent:

• Not on the Nginx server (/wapt/waptagent.exe), error 404

• Nor in the release files available on your site (https://wapt.tranquil.it/release/wapt-2 ... -69968974/)

Did I miss a step in the installation documentation? Or do I need to use a different binary?

Thank you in advance and have a good day

[dcardon]

What documentation are you following?
Regards,
Denis

[apache]

Hello Denis,

I'm following the documentation:
https://www.wapt.fr/en/doc-2.3/wapt-ser ... based.html
The part for installing the server was very clear, however, I'm a bit lost with the next part, "installing the WAPT Console," in the link below:
https://www.wapt.fr/en/doc-2.3/wapt-con ... pt-console
After testing, it seems that the executable for the WAPT Windows client is the one available on the server at this level:
https://wapt.domain.local/wapt/waptagent/waptsetup.exe
Except that it's also the one indicated for installing the WAPT admin console, as shown in the last link in the documentation I shared.
I do have the 'WAPT Self Service Software' program, but no console. Is there another step I need to take?

Have a good day,

[dcardon]

Hello Apache,

the installer for the management machine and for client machines is more or less the same. What changes is the configuration that's been "stuffed" into it.
By default, there's no configuration in waptsetup.exe. It's installed on the management machine, which installs the agent and the console included within it.
Then, using the console, you configure waptsetup.exe, which is subsequently referred to as waptagent.exe (to differentiate it), but essentially it's the same executable with added "stuffing."

In earlier versions (version 2.2 and before), the agent was regenerated with innosetup on the management machine, but this caused problems with antivirus software because it wasn't signed (since it had been regenerated), unless you had a key-code signing system, which is quite rare.

Since version 2.3, the installer is no longer regenerated with Innosetup; instead, the configuration for client machines is configured at the end.

Regards,

Denis

[apache]

Thanks for the explanation, it was very clear.
I'm continuing with my setup.

Have a good rest of the day!

[dcardon]

Thanks for the feedback,
Denis