Tranquil IT Forum

WAPT Enterprise version 2.6.1.17813
OS Server: Debian 11.11
OS of the administration machine: Windows 11

Hello everyone,
We have subscribed to five hours of WAPT technical support to schedule an appointment to:
- Install the WAPT agent and the Self-Service tool on an Ubuntu machine.
- Automate the subsequent installation via a script, then with the FAI (Fully Automatic Installation) tool.
Our institute uses LDAP (and not Active Directory) for authentication.
To my knowledge, integration with LDAP requires manually entering the WAPT password, unlike Active Directory, which poses a problem when automating the installation.
Is this still the case? If not, what is the recommended method for automated integration?
Regarding the Ubuntu version, which version do you recommend for optimal compatibility with WAPT?
During our exchange with Tranquil IT support, we understood that your remote access tool only works on Windows.
To facilitate handling and testing:
- Is it preferable to prepare an Ubuntu virtual machine (registered on our network as a physical machine) so that snapshots can be taken to allow for rollbacks?
- Or to directly configure a workstation with the default corporate configuration (which uses LDAP)?
Our goal is to make the most of this meeting to validate the installation, understand best practices, and prepare for future automation.
Thank you for your advice and feedback on the best approach.
Sincerely,
Adrien

Adrien wrote: ↑June 25, 2026 - 10:54 - Automate the installation afterwards via a script, then with the FAI (Fully Automatic Installation) tool.

Can you specify exactly what you want to do?

Adrien wrote: ↑June 25, 2026 - 10:54 AM Our institute uses LDAP (not Active Directory) for authentication.
To my knowledge, integration with LDAP requires manually entering the WAPT password, unlike Active Directory, which poses a problem when automating the installation.
Is this still the case? If not, what is the recommended method for automated integration?

You mean for registering machines in WAPT? Yes, indeed, you need either Kerberos (AD) credentials or a username and password (which can be entered via the command line)

Adrien wrote: ↑June 25, 2026 - 10:54 Regarding the Ubuntu version, which version do you recommend for optimal compatibility with WAPT?

We're mostly using Debian here, but the latest version of Ubuntu ltsc should work

Adrien wrote: ↑June 25, 2026 - 10:54 During our exchange with the reception of Tranquil It, we understood that your remote control tool only works under Windows.

The tishelp also works for Debian, but you can also just share your screen depending on the need

Adrien wrote: ↑June 25, 2026 - 10:54 AM - Is it better to prepare an Ubuntu virtual machine (registered on our network as a physical machine) so that snapshots can be taken to allow for rollbacks?
- Or to directly configure a workstation with the default company configuration (which uses LDAP)?

Can you specify your exact deployment workflow? Are we talking about a Linux machine? No Kerberos?
The machine doesn't really have an account in OpenLDAP? Pegina configuration?

I don't know FAI at all.

At Tanquilit, we primarily use IPXE for deployment, plus integration into an Active Directory domain using Samba4.

sfonteneau wrote: ↑June 25, 2026 - 6:31 PM

Adrien wrote: ↑June 25, 2026 - 10:54 - Automate the installation afterwards via a script, then with the FAI (Fully Automatic Installation) tool.

Can you specify exactly what you want to do?

In our institution, we have a shell script which allows, among other things, once the ubuntu operating system is installed, to configure NTP on the workstation with an internal server, to integrate ubuntu with LDAP with sssd, to install the glpi agent, etc.
I would therefore like to adapt this shell script to automatically integrate the latest version of the wapt agent compatible with the version of Ubuntu used, as well as self-service.
During my tests, as it was not working perfectly, I downloaded and installed the correct .deb file, but it was not necessarily the latest version.
(Requires updating manual links)
If the script works, I will try to make it work with ISP which allows both installing ubuntu and configuring it (installing software, launching shell scripts).
However, it is not possible to execute all shell commands as desired, because instead of running the script on a session using the relevant operating system, ISP uses a Debian operating system to install and configure Ubuntu, the shell scripts are executed in the chroot environment.
If needed, I then configure a service to run a script when the Ubuntu operating system starts.

sfonteneau wrote: ↑June 25, 2026 - 6:31 PM

Adrien wrote: ↑June 25, 2026 - 10:54 AM Our institute uses LDAP (not Active Directory) for authentication.
To my knowledge, integration with LDAP requires manually entering the WAPT password, unlike Active Directory, which poses a problem when automating the installation.
Is this still the case? If not, what is the recommended method for automated integration?

You mean for registering machines in WAPT? Yes, indeed, you need either Kerberos (AD) credentials or a username and password (which can be entered via the command line)

That's it (registration of machines in wapt).
From my side:
- I was unable to provide the password for integration into ldap, however, by entering the wapt password requested after the ldap command, the machine was integrated into the wapt console.
- Under Active Directory, I could integrate the workstation into the wapt console by providing the wapt password to the command to add it to the domain.
I would add that adding it to Active Directory requires an adaptation of the NTP configuration which I am not sure about, which explains why I prefer integration into LDAP.

sfonteneau wrote: ↑June 25, 2026 - 6:31 PM

Adrien wrote: ↑June 25, 2026 - 10:54 Regarding the Ubuntu version, which version do you recommend for optimal compatibility with WAPT?

We're mostly using Debian here, but the latest version of Ubuntu ltsc should work

I should clarify that I was referring to the client's operating system that will run the wapt agent and the self-service.
For now, the workstations are configured with ubuntu (22.04 LTS or 24.04 LTS, later addition of version 26.04 LTS under ISP).
I ask this because I read a while ago on the forum that some versions of Ubuntu worked better than others.
(If I remember correctly, it's Ubuntu version 20.04 LTS, which is now obsolete)

sfonteneau wrote: ↑June 25, 2026 - 6:31 PM

Adrien wrote: ↑June 25, 2026 - 10:54 During our exchange with the reception of Tranquil It, we understood that your remote control tool only works under Windows.

The tishelp also works for Debian, but you can also just share your screen depending on the need

I ask this question because it doesn't reassure me not to be able to check with a Wapt technician what is happening at the graphical level.
(for example, if the self-service interface does not display the software that can be installed under Ubuntu)

sfonteneau wrote: ↑June 25, 2026 - 6:31 PM

Adrien wrote: ↑June 25, 2026 - 10:54 AM - Is it better to prepare an Ubuntu virtual machine (registered on our network as a physical machine) so that snapshots can be taken to allow for rollbacks?
- Or to directly configure a workstation with the default company configuration (which uses LDAP)?

Can you specify your exact deployment workflow? Are we talking about a Linux machine? No Kerberos?
The machine doesn't really have an account in OpenLDAP? Pegina configuration?

I don't know FAI at all.

At Tanquilit, we primarily use IPXE for deployment, plus integration into an Active Directory domain using Samba4.

Wapt (self-service part) has already been used for Windows with Kerberos since 2020.
We want to extend Wapt to Linux Ubuntu for self-service.
We do not use Pegina, but users are authenticated via openldap.
We have already managed to add a post in active directory, however I do not have a good grasp of kerberos and the Wapt configuration is unstable.
Can you tell me if configuring Linux workstations already integrated with ldap will be possible by adapting the workstation configuration or will a complete reinstallation be required?