Tranquil IT Forum

Hello,

I have a Windows Server 2003 and WAPT 1.3.13, and it's impossible to install WAPT version 1.5.
The solution is to install it on a Windows Server 2012 or Linux server.
Has anyone done this before?
What happens to the public and private keys between the server and client?
Is there a specific procedure?

Thanks in advance for your answers.

See https://www.wapt.fr/fr/doc/waptserver_u ... ur-windows for more

WAPT Server is no longer installable on x86 versions of Windows.

information

Hello,

thank you for the reply. I will test the "Transferring WAPT 1.3 from Windows to Linux" solution with Debian Stretch 9.4.

Many thanks!

My Debian server is working, but is it possible to change the server name for client programs?
When I load a new machine, it takes the name of the old server.
I can't reclaim the name because it's being used by another server application.
Thanks.

Are you referring to the value in the wapt-get.ini file?

You can change the value manually or using a group policy.

You will also need to regenerate a WAPT agent to inform it of the new value.

It exists on the Windows server c:\wapt\wapt-get.ini but not on the Linux server

I don't understand the question.

Hello,

where is the configuration file on a Debian server to change the server name for client applications?
Currently, it's pointing to the old name of my Windows 2003 server after the file copy (Windows 2003 to Debian 9.4).

Are you perhaps referring to the DNS name?

In that case, you'll need to create a new entry for your WAPT server on your DNS server, different from the old DNS address assigned to your 2003 server which is still hosting services.

Regards,

Vincent

Good evening,

I understand the issue, but my problem is that the DNS name and IP address of my Windows 2003 server are being used by other applications, and I can't retrieve them.

That's why I want to change the DNS name and IP address of my new Debian 9.4 server. I'll manually change the DNS name of the already registered machines (in wapt-get.ini) (or automatically, since there are already 950 machines registered!). For new machines, I'd like them to retrieve the DNS name of "new-name-WAPT" via the settings of my new Debian server.
Currently, when I launch a new client with my new Debian server, it always provides the old name (I haven't found a wapt-get.ini file on the server side),
keeping the private and public keys of the old Windows 2003 server.