Tranquil IT Forum

- WAPT 1.7.4.6229 Enterprise
- Debian 9.9
- Windows 10 1703 and 1909

Hello,

We are currently testing a Windows 10 version 1909 deployment.

We are encountering an error in the information reported by WAPT.

The Windows 1909 version is: 18363.476.

In the console, the reported version is 18362 (Windows 10 1903).

I have performed several forced inventories, but the version does not change.

Mathieu wrote: ↑Nov 22, 2019 - 3:14 PM - WAPT 1.7.4.6229 Enterprise
- Debian 9.9
- Windows 10 1703 and 1909

Hello,

We are currently testing the deployment of Windows 10 version 1909.

We encountered an error in the information reported in WAPT.

The Windows 1909 version is: 18363.476.

In the console, the reported version is 18362 (Windows 10 1903).

I have performed several forced inventories, but the version does not change.

Could you try a `wapt-get register` on a client? There are certain values ​​that aren't re-inventoryed each time to avoid overloading the client machine. WMI and dmidecode queries are quite resource-intensive, and portions of the tree are cached under specific conditions for cache invalidation. This particular case might not be handled correctly.

Sincerely,

Denis

I'm using a package that forces the update:

`def audit():
WAPT.register_computer()
return 'OK'`

, but I'm still not getting the correct version.

Hello Mathieu,

Mathieu wrote: ↑Nov 25, 2019 - 5:34 PM I'm using a package that forces the update

: def audit():
WAPT.register_computer()
return 'OK'

but I'm still not getting the correct version

Clearly, there's a Wapt bug and a Windows and/or dmidecode bug... If we delete the computer to force a new registry entry, the wmi/Win32_OperatingSystem/Version value is indeed updated to 10.0.18363. However, in dmidecode, dmi/host_info/os_version is still at 10.0.18362, and if we check the wuapi.dll library version, it's still at 10.0.18362.387... So Microsoft has incremented some values ​​in the OS, but not all of them.

Regarding the inventory, the WAPT agent compares the inventories with the one previously sent to avoid resending everything each time (when there are several thousand workstations on a WAPT server, inventory parsing becomes quite complex). There is a problem with... https://github.com/tranquilit/WAPT/blob ... n.py#L5594

I'll talk to Evan about the debugging this afternoon (it's lunchtime now, and Evan is in the middle of a Mortal Kombat X game against Yohannès to try and erase his defeat from yesterday in the final of the intra-company tournament).

Sincerely,

Denis

Okay, no worries,

because it's annoying since I rely heavily on the Windows version for distributing my packages and now I'm stuck because the version isn't right.