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.
Wapt on Windows 2003 is obsolete
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
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
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
WAPT Server is no longer installable on x86 versions of Windows.
information
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.
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.
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
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.
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.
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
I don't understand the question.
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
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
Vincent CARDON
Tranquil IT
Tranquil IT
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.
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.
