Problem installing agent on old and new wapt servers

[Skarn34]

Hello,

With the recent change in how WAPT works, we decided to switch to a new WAPT server for various reasons.

Our old server is running Debian, and so is the new one.

The only problem is that it's impossible to install the new agent on the machines because the system, of course, detects the presence of the old agent. It works if we do things manually, manually uninstalling the old agent from the machine to deploy the new one. But this isn't easy to do on 400 machines.

I've searched the forum and the documentation, but I haven't really found the right solution. What needs to be done on the old server or the new one to uninstall the agent?

Old agent: 1.3.13.0
New agent: 1.5.1.23

If anyone has a solution, I would be very grateful.

Thank you and have a good day

[sfonteneau]

The only problem is that it's impossible to install the new agent on the machines because the system, of course, detects the presence of the old agent. It works if you do it manually, manually uninstalling the old agent from the machine to deploy the new one. But this isn't easy to do on 400 machines.

This is the first time we've heard about this problem. There's no reason why agent 1.5 should refuse to install over 1.3

[Skarn34]

Hello and thank you for your reply

When I run the new script, this is the message I get.

wapt.png (16.05 KB) Viewed 4116 times

Whether the old server is on or off, it gives the same result.

It detects the presence of the old version and therefore cannot complete the installation of the new one. For the moment, I am forced to uninstall the old agent manually.

[sfonteneau]

It can't open c:\users\nfdkjfznkjfznk\AppData\Local\Temp\waptagent.exe.

Antivirus?

Accent in the username hidden?

File already open or incorrect permissions?

SRP enabled?