Tranquil IT Forum

Hello,

We have been using Wapt for several years and this is the first time we have encountered this problem.
We regularly install the Wapt client remotely via PsExec using the command "Waptagent.exe /verysilent", but since updating to version 2.5.4 (and then 2.5.5.15602), the WaptAgent.exe installer no longer writes the server's IP address to the wapt-get.ini file.

A manual installation works; when the "Default" option is selected from the dropdown list, the server's IP address is correctly displayed in the edit field just below.

The server runs on Debian 12, the clients are on Windows 10 or 11, as are the administration workstation(s).

Is this normal?

Thank you in advance.
Best regards.

Hello,

during installation, is the file correctly named:

waptagent.exe? Or has it been renamed?

Yes, it's renamed (WaptAgentXX.exe). Does that cause a problem?

The agent is now capable of storing multiple WAPT configurations.

To define a default configuration for the binary, you can put a hash in the filename to choose the configuration.

So in some cases, yes, this causes a problem (if I remember correctly, if there's an underscore in the filename).

I can confirm this. By leaving the default name (waptagent.exe), the IP address of the server from which the executable originates is correctly entered in the wapt-get.ini file.
We only added two numbers to the end of the name (no underscores).

This is just my opinion, but I'm rather frustrated that I can't rename this installer as I wish.

Thank you for the quick troubleshooting.

Hello Antony, are

using the Discovery or Enterprise version (see forum rules)?

If it's the Enterprise version, you can speak with your sales representative to escalate these issues.

Regards,

Denis

Hello,

Discovery version.