Tranquil IT Forum

Published: **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.

Published: **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

Tranquil IT Forum

Wapt on Windows 2003 is obsolete

Re: Wapt on Windows 2003 obsolete

Re: Wapt on Windows 2003 obsolete