Tranquil IT Forum

WAPT Version: 2.6.0.16714 - Enterprise Edition
Server OS: Debian 12
Target Machines: Windows Server 19
Administration Machine: Windows Server 2022

Hello,

we've encountered a small issue since upgrading to version 2.6. When we go to the "Edit Agent Dynamic Configurations" menu, some advanced settings reset themselves (become empty), notably "host_organizational_unit_dn". Even if we re-enter it, it resets again on the next launch.

Have you ever experienced this problem? What can we do?

Thank you

I tried it here and I don't have the problem.

But I might have a lead. It could be another parameter currently in the configuration that no longer exists and is preventing the save.

Can you provide a list of the other parameters you have?

Alternatively, can you create another configuration to see if the problem occurs in another configuration package?

I don't know if it's actually a registration problem.
I have 5 different configurations, and the field randomly resets to one of the 5 configurations every time the console is launched: once, the "host_organizational_unit_dn" field of configuration 1 will be reset, but if you close and relaunch the console, it will be on configuration 3, and so on.

I'll add my two cents here as well. I ran the test and indeed I get the same behavior. That said, I don't use all those settings, and as Simon mentioned, they might be resetting because they're no longer supported in version 2.6?

Does it do the same thing if you do it with a newly created configuration package?

The problem is that if I create a new configuration package, it will save the empty field on an already existing package.

Actually, when I launch the console:
If I look at the "linux" configuration, the field is filled if I go to a configuration where the field is empty, for example "Srv_Hors_domain" And if I go back to the "Linux" configuration, the field appears empty So if I save, it will erase all my settings...

Okay, after your screenshot I think I know (to be confirmed)



that include_dmi_inventory and include_wmi_inventory have disappeared from the wapt configuration in 2.6.
And saving this parameter, which no longer exists, must be causing it to crash, in my opinion.

Can you try deleting the parameter on the right?

sfonteneau wrote: ↑Jan 14, 2025 - 1:20 PM Okay, after your screenshot I think I know, to be confirmed,



include_dmi_inventory and include_wmi_inventory have disappeared from the wapt configuration in 2.6.
And saving this parameter, which no longer exists, must cause it to crash in my opinion.

Can you try deleting the parameter on the right?

The same problem persists, and as a result, it cleared the field of all configurations.

However, if I delete all existing configurations and recreate them, the field remains filled in.

clafon wrote: ↑Jan 14, 2025 - 1:40 PM However, if I delete all existing configurations and recreate them, the field remains filled in...

Ah, that's interesting. I just spent 15 minutes trying to reproduce the problem here without success