Hello,
I'm having trouble with BIOS data retrieval, specifically the serial number of the machines.
Some machines retrieve the information correctly, while others don't.
I've checked the execution of dmidecode.exe, which works correctly and displays all the machine information in a text file.
I can't see where the problem lies with retrieving the information, even after updating the BIOS.
Do you have any suggestions?
Rudy
random DMI - serial number
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Hello,
Could you please send a copy of the dmidecode report?
Steven
Could you please send a copy of the dmidecode report?
Steven
Steven Samson - Tranquil IT Systems
Feel free to leave us your opinion on Wapt in the forum, or to answer our questionnaires
.
Feel free to leave us your opinion on Wapt in the forum, or to answer our questionnaires
.Hello,
I was able to solve my problem by running the following command on the client machines: `wapt-get register`.
It's strange that the agent wasn't sending the information during installation.
So I created a package incorporating the above command and then deployed it to all my machines.
I was able to solve my problem by running the following command on the client machines: `wapt-get register`.
It's strange that the agent wasn't sending the information during installation.
So I created a package incorporating the above command and then deployed it to all my machines.
The order is executed at the end of the waptagent.exe installation.
Code: Select all
wapt-get registerSteven Samson - Tranquil IT Systems
Feel free to leave us your opinion on Wapt in the forum, or to answer our questionnaires.
Feel free to leave us your opinion on Wapt in the forum, or to answer our questionnaires
.