I just configured a new WAPT server under Debian 9.
WAPT Server version: 1.5.1.21,
WAPT Agent version: 1.5.1.21,
WAPT Setup version: 1.5.1.21,
WAPT Deploy version: 1.5.1.21.
Database status: OK (1.5.1.21).
During the installation of the waptagent.exe agent, and at the very end during computer registration, a console window opens on the Windows machine asking me to enter my console credentials ("please get login").
After entering the credentials, the agent installs correctly; however, I think there's a problem during the agent generation process.
Could you give me some pointers on how to fix this issue?
Thanks in advance
.
Request for login credentials during agent installation
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
Actually, it's not a defect, but a change compared to version 1.3.13.
In version 1.5.1, machines must be authenticated in order to register for the first time on the Wapt server.
They are either through their Kerberos account if they are integrated into a domain and Kerberos was activated during the installation of the Wapt server and during the generation of the agent.
In this case, the initial registration (register) on the server does not require additional authentication.
Otherwise, you must manually provide a Wapt administrator username/password for the server to accept the machine.
Alternatively, we can also keep the unauthenticated mode from version 1.3 by adding the parameter
to waptserver.ini
see https://www.wapt.fr/fr/doc/Configuratio ... gistration
In version 1.5.1, machines must be authenticated in order to register for the first time on the Wapt server.
They are either through their Kerberos account if they are integrated into a domain and Kerberos was activated during the installation of the Wapt server and during the generation of the agent.
In this case, the initial registration (register) on the server does not require additional authentication.
Otherwise, you must manually provide a Wapt administrator username/password for the server to accept the machine.
Alternatively, we can also keep the unauthenticated mode from version 1.3 by adding the parameter
Code: Select all
allow_unauthenticated_registration = Falsesee https://www.wapt.fr/fr/doc/Configuratio ... gistration
Tranquil IT
