Tranquil IT Forum

Hello everyone,

following the update from 2.2.3 to 2.3.0.13438, I'm having several issues...

1) As mentioned in this thread, since the update, the waptdeploy.exe GPO deployment no longer works. If I try the command line manually: "Unable to read file version".
The same thing happens when reverting to the old waptdeploy... 2.2.312463.

2) If I install the wapt agent manually: it asks me for a username/password at the end of the installation to register the computer. With an Active Directory username, registration works, but I have to do it manually.
During the update, the postconf was correctly set on Kerberos, as well as during the generation of the wapt agent.

3) It is no longer possible to forget a package, perform a forced installation, audit the package (etc.) via the WAPT console, in the computer's package list (by right-clicking on the relevant packages on the computer). The options are grayed out... This works locally on a machine, for example, with "wapt-get forget mypackage".

Thank you in advance.

WAPT Server version (Debian): 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)

Hello,

a new version has just been released specifically to resolve this issue of grayed-out actions for Discovery users

: https://wapt.tranquil.it/wapt/releases/ ... 3/?C=M&O=D

Thank you

, I'll take a look as soon as I can.

Have a good evening,
Alexis.

Hello,

I'm joining this forum thread because I'm experiencing problem 3) mentioned. I'm now on version 2.3.0.13470 Discovery, and the problem persists.

If you think it would be helpful for me to create a separate thread, please let me know.

WAPT Server (CentOS7) version: 2.3.0.13470
WAPT Agent version: 2.3.0.13470
WAPT Setup version: 2.3.0.13470
WAPT Deploy version: 2.3.0.13470
Database status: OK

fcomte wrote: ↑01 Feb 2023 - 12:31 I am now on 2.3.0.13470 Discovery and the problem persists.

Can you elaborate?

This thread discusses several problems

This one:
3) It is no longer possible to forget a package, perform a forced installation, audit the package (etc.) via the WAPT console, in the computer's packages (by right-clicking on the relevant packages on the computer). The options are grayed out...

I have not encountered the other problems mentioned (1 and 2).

Good morning,

For my part, everything went back to normal after upgrading to 2.3.0.13470 via "apt get" directly and then running the Post-conf script again.

However: have you changed the way you configure wapt-get with the "wapt-get.ini" file?
I'm asking because on a test VM (clean, with wapt installed via GPO / waptdeploy in 2.3.0.13470), I wanted to add the DEV maturity level to wapt-get.ini and I realize that it's practically empty:

[global]
repo_url=https://myserver.net/wapt
wapt_server=https://myserver.net
verify_cert=c:\my_path"
use_kerberos=1

Nothing else. Are there no parameters like send_usage_report, use_hostpackages, check_certificates_validity, allow_remote_reboot [etc...] that were present in older versions?


Thank you (y)
Alexis

Hello,
As far as I'm concerned, the problem is still ongoing.

I just tested it again in console version 2.3.0.13470 using the admin account, and it works.

Could you delete C:\Users\%username%\AppData\Roaming\waptconsole

and then reinstall the console to see

if that fixes it? I doubt that's the issue, but...

are you definitely using the admin account?
Are you sure you're within 300 users?

Hello,

are you using the admin account? Yes,
are you sure you have fewer than 300 machines? Yes, fewer than 200 even.

After deleting the specified folder, I switched back to Enterprise mode. I had to uncheck "Verify HTTPS server certificate" to be able to open the console and switch back to Discovery. I don't know if this is normal behavior? After that, the situation remains the same.

I can add a few troubling details:
- As part of my testing, I deleted the machine where the inventory console is located. It no longer appears, even though it has the agent up to date (via GPO).
- And I tested on 2 or 3 PCs; when I open Self Service, they don't see any packages except the agent.
- And for your information, I had also lost access to the packages in the private repository; I had to follow a procedure to resign the packages and hosts from the terminal.