.. Reminder for header structure:
  Parts (H1)          : #################### with overline
  Chapters (H2)       : ******************** with overline
  Sections (H3)       : ====================
  Subsections (H4)    : --------------------
  Subsubsections (H5) : ^^^^^^^^^^^^^^^^^^^^
  Paragraphs (H6)     : """""""""""""""""""""

.. meta::
  :description: Frequent problems and questions
  :keywords: lost password, lost private key, stolen private key, BIOS bug, waptdeploy, WAPT, documentation, the WAPT Deployment utility

.. _wapt_faq_system:

#################################
FAQ - System Environnement Issues
#################################

.. _my_bios_uuid_bugs:

*****************
My BIOS UUID bugs
*****************

* Some problems happen sometimes with some BIOSes.
  WAPT uses the :term:`UUID` of the host as the host identifier.

* The :term:`UUID` is supposed to be unique.
  Unfortunately, for some :abbr:`OEMs (Original Equipment Manufacturers)` and some manufacturing batches, BIOS :term:`UUID` are identical.

* The host will register in the WAPT Console but it will replace an existing device, considering that the host has only changed its name.

Solving the BIOS UUID issue
===========================

WAPT allows to generate a random :term:`UUID` to replace the one retrieved from the BIOS.

.. code-block:: bash

  wapt-get generate-uuid

The WAPT Agent :abbr:`FQDN (Fully Qualified Domain Name)` may be used instead of the :abbr:`UUID (Universal Unique IDentifier)`.
In the :file:`wapt-get.ini` configuration file, define in the :guilabel:`[global]` section:

.. code-block:: bash

  use_fqdn_as_uuid = True

.. _error_with_proxy:

**********************************************************************
I have an issue with my proxy - THttpClientSocket.SockRecv(1) read = 0
**********************************************************************

If you have this issue:

.. figure:: wapt-resources/wapt_console_proxy-error-timeout_dialog-box.png
  :align: center
  :alt: Window showing a proxy timeout error in the WAPT Console

  Window showing a proxy timeout error in the WAPT Console

The error comes from a :code:`timeout` option in the :file:`waptconsole.ini`.

Indeed, since WAPT 2.1 version, timeout is defined in milliseconds and not in seconds like before. 

You will need to remove the :code:`timeout` option in the :file:`waptconsole.ini` file located in :file:`%localappdata%\\waptconsole`.

***********************************************
Frequent problems caused by Anti-Virus software
***********************************************

Some Anti-Virus software falsely raise errors when checking some internal components of WAPT.

Among the components is :program:`nssm.exe` used by WAPT as a service manager for starting, stopping and restarting the WAPT service.

Below is a list of useful exceptions to declare in your central :abbr:`AV (Anti-Virus)` interface to solve false positives related to WAPT:

.. code-block:: ini

  "C:\Program Files (x86)\wapt\waptservice\win32\nssm.exe"
  "C:\Program Files (x86)\wapt\waptservice\win64\nssm.exe"
  "C:\Program Files (x86)\wapt\waptagent.exe"
  "C:\Program Files (x86)\wapt\waptconsole.exe"
  "C:\Program Files (x86)\wapt\waptexit.exe"
  "C:\wapt\waptservice\win32\nssm.exe"
  "C:\wapt\waptservice\win64\nssm.exe"
  "C:\wapt\waptagent.exe"
  "C:\wapt\waptconsole.exe"
  "C:\wapt\waptexit.exe"
  "C:\Windows\Temp\waptdeploy.exe"
  "C:\Windows\Temp\waptagent.exe"
  "C:\Windows\Temp\is-?????.tmp\waptagent.tmp"

*************************************
The WAPT Deploy utility does not work
*************************************

The the WAPT Deployment utility does not succeed in installing the WAPT agent.

Launching the WAPT Deployment utility locally
=============================================

Launching the WAPT Deployment utility locally can be a good method for showing errors explicitly.

.. attention::

  You **MUST** launch the command prompt using a :term:`Local Administrator` account.

Example of command to launch:

.. code-block:: bash

  C:\Program Files (x86)\wapt\waptdeploy.exe --hash=2a9971aad083d6822b6e4d1ccfb9886be9429ec58bb13246810ff3d6a56ce887 --minversion=2.1.0.10550 --wait=15 --waptsetupurl=https://srvwapt.mydomain.lan/wapt/waptagent.exe

In our case the hash for the WAPT Deploy utility is not correct.

.. figure:: wapt-resources/wapt_deploy_hash-error_text-terminal-window.png
  :align: center
  :alt: Error with the WAPT Deploy utility hash in a text terminal window

  Error with the WAPT Deploy utility hash in a text terminal window

The WAPT Deploy utility works manually but does not work with GPO
-----------------------------------------------------------------

Check that port 8088 is listening correctly on the host:

.. code-block:: bash

   gpresult /h gpo.html & gpo.html

To force the application of the GPO:

.. code-block:: bash

   gpupdate /force

If the WAPT Deployment utility does not show up you will have to double check the GPO settings:

* You may be using an old WAPT Deployment utility version, then :download:`download the latest version <https://store.wapt.fr/wapt/releases/latest/waptdeploy.exe>` of the WAPT Deployment utility from the WAPT Server web page.

* Thanks to Emmanuel EUGENE from French public research institution `INSERM <https://www.inserm.fr/en>`_ who submitted this possible cause for the WAPT Deployment utility not functioning properly, if you are replicating domain controllers, ensure that the GPOs are correctly synchronized between your DCs and that :abbr:`ACLs (Access Control Lists)` are identically applied on the :file:`Sysvol` directories.