Page 1 of 1

Wapt console does not return the correct property for the BIOS

Published: Dec 6, 2022 - 09:23
by lfkl
Good morning,

We use the following BIOS deployment package:

Code: Select all

# -*- coding: utf-8 -*-
from setuphelpers import *

def install():
    print(f"installing {control.package}")
    run_notfatal(f'"{glob.glob("*.exe")[0]}" /p=monpasswordbios/s /r')  # le /r est nécessaire seulement pour restaurer un bios plus ancien
Created by Olivier Laplanche and Pierre Cosson. Thanks to them, it works very well!

The problem is as follows: After a successful installation, the WAPT console still returns the value of the old BIOS.
Therefore, it's impossible to know if our BIOS is up to date on the machines.
We use the property:
dmi/BIOS_Information/Version

All other BIOS-related properties also revert to the previous version.
However, on the machines in question, when you go into the BIOS, it is indeed the more recent version installed by the Wapt package that is on the machine...

No matter how many times we refresh the console or restart the machine, nothing works.

How can I make the console return the version actually installed on the machine?

Thank you for your help.

Wapt Enterprise Server: 2.2.3.12463
Debian 11

Re: Wapt console not returning the correct property for the BIOS

Published: Dec 6, 2022 - 11:11
by sfonteneau
by making a

Code: Select all

wapt-get register 
Is that bringing up the correct information?

If so, in the package one would need to be made

Code: Select all

WAPT.register_computer()
Indeed, we don't force an inventory reload every time to avoid overloading the machine

[PARTIALLY RESOLVED] Re: Wapt console not returning the correct property for the BIOS

Published: Dec 7, 2022 - 01:00
by lfkl
Hello Simon,

Thank you, that was it.
wapt-get register
It successfully updates the correct BIOS version on the console.

However, I question the usefulness of inserting
WAPT.register_computer()
in the package in question because if the package runs correctly when stopped, the BIOS update only starts on the next startup of the machine, so the BIOS inventory that will be brought back remains the old one, right?

After that, I can always manually use the "refresh workstation inventory" function from the console, which leads me to the following question:
Apart from this command, how frequently are inventory updates made to the console and/or what triggers such an update?