Tranquil IT Forum

Hello,

I just upgraded from version 1.3 to 1.5 Community on Debian 9.
After installing it on the Linux side, I proceeded to the WAPT console installation on Windows.
When the console starts, a message appears saying that the WAPT agent version is 1.3.13 and the console version is 1.5.23. I thought, okay, it's not mentioned in the documentation, but it must be temporary.
I checked the server's web page and indeed my agent is version 1.3.13. I figured it should be generated later in the process.
So I continued the procedure, reaching the certificate section: Tools > Generate a certificate, but I can't find the options to add the "Code Signing" tag.
Is this a bug, or am I doing something wrong? The documentation is very well written, so I'm wondering where the problem could be.

If you've encountered this issue before, I'd appreciate any similar feedback.

Have a good day.

Indeed, the documentation shows a screenshot of the enterprise version.

In the enterprise version, you have to specify CA and/or Code signing.

In the community version, there's no need to specify this.

Okay, indeed, I continued and everything worked correctly. Thank you!

However, with the renaming of the machine packages, I now have the new package UID for each machine, for example:
"Package UID number" host package for pc-124.mydomain...

The old package, named simply with its FQDN, is no longer used. So, if we want to do it properly, I suppose we have to delete the old machine package on each machine.

steamera wrote: ↑May 22, 2018 - 11:01 The old package, simply named with its FQDN, is no longer used. So, if we want to do things properly, I suppose we have to delete the old machine package on each machine.

If everyone has migrated, you can, his presence is not a problem.