Tranquil IT Forum

WAPT: Enterprise 2.2.3.12463
Server: Windows Server 2019
Clients: Windows 10 Pro 21H2

Hello,

I've been experiencing a problem since upgrading to version 2.2.3.
The machines on which I perform a first-time WAPT installation using waptagent.exe correctly connect to the WAPT server, but when I assign packages to them, they are not deployed.

In the package update task logs, it sees my Wapthostrepo but indicates that there are 0 packages in the repository.

In contrast, the machines that were previously using agent version 2.2.1 and were upgraded to 2.2.3 via the Waptupgrade package are functioning normally and receive the updates I deploy.

Is there some nuance I might have missed when upgrading from 2.2.1 to 2.2.3?

Hello Max.R,

could you please verify that the certificate has been added to the Waptagent? The agent will only display packets that it can validate itself. If it doesn't have the certificate, it cannot validate the packet and therefore ignores it.

Regards,

Denis

Hello Max. R.,

was that indeed the problem that led me to mark the topic as resolved?

Regards,

Denis

Hello Mr. Caron,

sorry for the delayed response, I was away.

How should I proceed to verify the presence of the certificate?
During a WaptUpgrade regeneration? It seems to me that this is the only time the path to the *.pem file is requested (apart from server installation).

Regards