[RESOLVED] ;)

Everything is back to normal and operational/PROD mode is restored:

WAPT Server Version: 2.3.0
WAPT Agent Version: 2.3.0.13438
WAPT Setup Version: 2.3.0.13438
WAPT Deploy Version: 2.3.0.13438
Database Status: OK (2.3.0.4)

I think more detailed documentation on the...

Hello Denis,

The situation is intractable, so a complete server overhaul and agent deployment need to be redone on the test workstations across my network.

Currently,
the WAPT server is operational under HTTPS with our certificates.
We are now working to resolve the connection between the console and the server...

Hello,

I followed the usual recommendations for upgrading WAPT from version 2.2.3 to 2.3.
The server is working perfectly and I have the following status:
WAPT Server Version: 2.3.0
WAPT Agent Version: 2.2.3.12463
WAPT Setup Version: 2.3.0.13356
WAPT Deploy Version: 2.3.0.13356
Status of ...

Hello,

thank you for the advice. I just upgraded from WAPT 1.8.2 to APT 2.2 and from Debian 10 to Debian 11.

Everything works fine after the migration.

Since I only have about 150 workstations to manage, I'd like to stay on the Discovery version, but I don't have a license.

How can I obtain one?

Hello,

I'm reviving this thread:

I applied TIS-DISEABLE-IPV6 to my admin console, but I'm still seeing IPv6 addresses instead of IPv4, even with console version 1.8.2.7393. We only use IPv4 in our organization. How can I change this display?