Wapt on Windows 2003 is obsolete

Questions about WAPT Server / Requests and help related to the WAPT server
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
Locked
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :
Contact Sfonteneau

July 11, 2018 - 6:32 PM

Yann44 wrote: ↑July 11, 2018 - 4:26 PM 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 cannot retrieve them.
https://www.wapt.fr/fr/doc/waptserver_u ... ws-a-linux

Code: Select all

Si les agents WAPT pointent sur une adresse IP, alors le nouveau serveur
    doit avoir la même adresse IP que l’ancien serveur WAPT sous windows.

Si vos agents WAPT pointent vers un enregistrement DNS,
    alors vous pouvez modifier le champ dns « srvwapt » en indiquant la nouvelle adresse IP du serveur WAPT linux.
Yann44 wrote: ↑July 11, 2018 - 4:26 PM For the new client, I'd like it to retrieve the DNS name of new-name-WAPT via the settings of my new Debian server.

Because currently, when I launch a new client with my new Debian server, it always provides me with the old name (I haven't found a wapt-get.ini file on the server side),
keeping the private and public keys from the old Windows 2003.
You need to regenerate the WAPT agent with the correct URL
For machines, if it is not possible to recover the old DNS name, then the WAPT agent will need to be reinstalled via GPO or manually.
High
Yann44
Messages: 12
Registration: July 9, 2018 - 1:39 PM

July 12, 2018 - 12:21

Hello,

I consulted the documentation and regenerated the WaptAgent. It works fine on a new machine.
If I manually change the C:\wapt\wapt-get.ini file (with the new DNS name) on my old machines (1000 in total!), it works.

I changed the WaptDeploy and Hash settings for the GPOs, but there's no change on the existing Windows 2003 machines, which still display an "access restricted" message. I ran WaptDeploy --hash... manually on each machine, but it doesn't work.

Is it possible to regenerate WaptDeploy like WaptAgent?


Yann
High
Locked

Return to "WAPT Server"


  • To go further with WAPT