Hello,
I would like to migrate a WAPT server from a Linux server to a Windows server.
Do you have a procedure for this type of migration?
If not, would I have to start from scratch with the new server (certificates, packages)? Since
the folders (wapt/, wapt-host/, waptwua/, wads/, conf/, ssl/) are common between Linux and Windows distributions, would a simple copy/paste allow me to retrieve the various settings from the first server?
Thank you for your answers.
Best regards,
WAPT Server Migration
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
-
GALTIER_Laurent
- Messages: 3
- Registration: January 27, 2025 - 3:50 PM
Last edited by GALTIER_Laurent on 10 Sep 2025 - 12:03, edited 2 times.
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Hello,
two points to note:
Kerberos authentication does not work on Windows servers.
Throughput is significantly worse on Windows servers than on Linux.
Our clients generally switch to Linux for this reason.
Why do you want to switch?
two points to note:
Kerberos authentication does not work on Windows servers.
Throughput is significantly worse on Windows servers than on Linux.
Our clients generally switch to Linux for this reason.
Why do you want to switch?
-
GALTIER_Laurent
- Messages: 3
- Registration: January 27, 2025 - 3:50 PM
I find the response times quite long on our server and we are experiencing the following problems:
- When creating a package, sometimes it doesn't immediately appear in the repository's package list; however, it's still possible to add it to the machines for distribution
- When adding packages to machines, the machine goes into "DISCONNECTED" mode. To verify the installation of a package, I either connect to the administrative shares of the workstation to check the installation logs, or I create a remote desktop to launch WaptTray and "force" the installation of the packages (this method is rarely used because it requires user interaction). Otherwise, I wait for the workstation to return to "OK" mode
- Sometimes, in the task tab on a machine, an error appears; I couldn't get the exact message, but it seems like a timeout, and the list of current or past tasks doesn't appear. The machine is online, however.
If you have any suggestions on how I can optimize all of this, I'm all ears.
We are on WAPT version 2.5.5.15602
Sincerely,
- When creating a package, sometimes it doesn't immediately appear in the repository's package list; however, it's still possible to add it to the machines for distribution
- When adding packages to machines, the machine goes into "DISCONNECTED" mode. To verify the installation of a package, I either connect to the administrative shares of the workstation to check the installation logs, or I create a remote desktop to launch WaptTray and "force" the installation of the packages (this method is rarely used because it requires user interaction). Otherwise, I wait for the workstation to return to "OK" mode
- Sometimes, in the task tab on a machine, an error appears; I couldn't get the exact message, but it seems like a timeout, and the list of current or past tasks doesn't appear. The machine is online, however.
- error_wapt.png (98.38 KB) Viewed 18518 times
We are on WAPT version 2.5.5.15602
Sincerely,
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Are the workstations, server, and console on the same site?
Is everything on a LAN, including the server?
Is everything on a LAN, including the server?
-
GALTIER_Laurent
- Messages: 3
- Registration: January 27, 2025 - 3:50 PM
Hello,
I'm reviving this discussion. I completely forgot to answer your questions, and I apologize.
Over time, I realized that the slightly longer response times were due to remote workstations (during a network incident that made all off-site workstations unavailable, response times were almost instantaneous, and upon their return, there was a slight delay again). I'm contacting
you again regarding the migration, but this time to a new server running Red Hat 9. We're currently on CentOS 7, and migrating to WAPT 2.6 isn't possible in its current state.
I initially wanted to update the current server from 2.5.5.15602 to 2.5.5.15691, but the repositories seem inaccessible (https://wapt.tranquil.it/centos7/wapt-2.5 is used in /etc/yum.repos.d/wapt.repo).
Thank you for your replies.
Best regards,
I'm reviving this discussion. I completely forgot to answer your questions, and I apologize.
Over time, I realized that the slightly longer response times were due to remote workstations (during a network incident that made all off-site workstations unavailable, response times were almost instantaneous, and upon their return, there was a slight delay again). I'm contacting
you again regarding the migration, but this time to a new server running Red Hat 9. We're currently on CentOS 7, and migrating to WAPT 2.6 isn't possible in its current state.
I initially wanted to update the current server from 2.5.5.15602 to 2.5.5.15691, but the repositories seem inaccessible (https://wapt.tranquil.it/centos7/wapt-2.5 is used in /etc/yum.repos.d/wapt.repo).
Thank you for your replies.
Best regards,
