Tranquil IT Forum

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,

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?

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,

Are the workstations, server, and console on the same site?

Is everything on a LAN, including the server?

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,