Tranquil IT Forum

Hello,
I'm new to this forum. Happy New Year 2019.

Installing version 1.3 of the server and client on Windows 7 worked perfectly. However, the packages are now designed for newer versions.

I couldn't update the server from 1.3 to 1.6, so I had to reinstall everything and redeploy the agent using my Kaspersky antivirus.

My setup is as follows:
Wapt Server version 1.6.2.7 on Windows Server 2012 R2.
Client PCs run on Windows 7, but primarily on Windows 10 version 1709.
I've added Wapt-related exceptions to my Kaspersky Central Console.

The Wapt agent on my PC is working; I can see it in my console.
When I try to install a Firefox package (or any other package), I get a message from WaptConsole indicating 0 actions launched, 1 error, 0 skipped, and 0 server errors. A small clock icon appears next to my PC's inventory. Nothing happens after that.

Any idea what the problem might be?

Thank you in advance for your help.

Hello,

there's a 99% chance that your computers' clocks are incorrect and therefore not properly connected to the WAPT server.

Alexandre

Hello,

Thank you for your reply, but the PCs are synchronized with the server, so their clocks are all correct. This morning I just saw that it connected when I logged in at 7:46 AM.

I had no problems with version 1.3.

I will test the Windows 7 machines and keep you informed.

Regards

Hello,

I just ran a test on a Windows 7 machine where version 1.3 worked perfectly. I'm getting the same result. So, there's a general problem somewhere.

Any ideas?

Thanks in advance.

Regards

There is a huge difference between version 1.3 and 1.5.

How did you perform the 1.3 to 1.5 update? At a minimum? Did you regenerate your keys correctly?

This type of problem mainly occurs when the request is incorrectly signed

The most frequent reasons for refusal:
- Wrong key
- Time difference between the workstation with the console (the one that signed the action) and the remote workstation (maximum 5-minute difference)

If that still doesn't work, start the service on the remote machine with:

Hello,

the update wasn't working. So, I uninstalled version 1.3 and installed version 1.6, as mentioned above.

I reused the existing certificate; perhaps that's where the problem lies.

How do I create a valid certificate? I suppose I should delete the old ones and create new ones?
However, will I need to recreate the packages I created with the old certificate so they are re-signed by the new one?

Also, it asks me to verify the key when I update a machine. Is it possible to prevent this verification?
Oh yes, do I need to update the agent on the workstations after re-creating the certificates?

Thank you for your help.

Have you followed the documentation?

https://www.wapt.fr/fr/doc/waptserver-u ... ndows.html
https://www.wapt.fr/fr/doc/waptserver-u ... regenerate
https://www.wapt.fr/fr/doc/waptserver-u ... apt-agents

Hello,

I had to do a complete reinstallation because I couldn't finalize the upgrade from version 1.3 to 1.6 due to an agent version issue. Even after updating to 1.6, it still didn't work. I hadn't found any concrete answers to this problem.

So, I'm going to start from scratch with the certificate configuration and re-sign the packages.

I'll keep you posted. Thank you very much.

Best regards

Hello,

I just repeated the process: certificates, resigned packages, and updated the agent.

I tested it on my Windows 10 PC and a Windows 7 machine in my network after updating the agent, and it works.
It also works on a newly installed Windows 10 laptop.

I am currently deploying the updated and functional agent across my entire network.

The ticket is therefore resolved.

Thank you very much to the team for the successful assistance.

Best regards