Server migration

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
Answer
Typhoon
Messages: 6
Registration: Nov 9, 2022 - 09:40

March 9, 2026 - 10:57

Hello,

I reinstalled a server running Debian 13 to upgrade my production server, which was running Debian 10.

The installation went smoothly, as did the package copying and signing. I can now use the new WAPT console just like the old one, except for the migration aspect.
I tried reinstalling the agent (pushed by the production server) = failure.
I tried modifying the wapt-get.ini file by replacing it with the server URL, which works, but with each upgrade, this file is rewritten with the original server URL.
I'm going in circles. Do you have any suggestions, as I'd like to migrate the entire system as gradually as possible?
Here is my script (compressed text file).

Thank you for your help.
Attachments
wapt.7z migration
(1.46 KB) Downloaded 1502 times
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

March 9, 2026 - 11:07

Thyphoon wrote: March 9, 2026 - 10:57 I reinstalled a server under debian 13 to upgrade my production server which was under debian10.
The advantage of being on Debian is being able to easily upgrade with a dist-upgrade.

Have you not considered this possibility?
Typhoon
Messages: 6
Registration: Nov 9, 2022 - 09:40

March 9, 2026 - 11:20

I considered it, but I ran into dependency errors everywhere, so I started from scratch. ;)
I'd just like to know if it's possible to uninstall the agent via WAPT while simultaneously launching a reinstall of a new agent via a scheduled task (that's what I see, but perhaps you have another method?).
What do you recommend in my situation?
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

March 9, 2026 - 11:47

In your case, I recommend upgrading to the latest version of WAPT on Debian 10 (it's still compatible).

Then, gradually upgrade from

Debian 10 to Debian 11,
reboot
Debian 11 to Debian 12,
reboot
Debian 12 to Debian 13.

Having done this several times, there shouldn't be any dependency issues.
Typhoon
Messages: 6
Registration: Nov 9, 2022 - 09:40

March 9, 2026 - 12:23

Unfortunately, we were forced to revert to a Debian image provided by the server management service. They're giving me time to migrate but want to destroy the old server.
Once we've reached a stable situation (packages migrated, agent configured, testing on a new client successful), how can I switch the entire system to this server?
User avatar
dcardon
WAPT Expert
Messages: 1929
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

March 16, 2026 - 10:03

Hi Yann,

were you able to successfully complete the upgrade/migration of your server?

Best regards,

Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Typhoon
Messages: 6
Registration: Nov 9, 2022 - 09:40

March 19, 2026 - 09:29

Hello, and sorry for my late reply.

I'm still in the testing phase, but my migration package from the old server to the new one is working.
I'm taking this opportunity to report what I believe to be an anomaly. I currently have a machine on my new server for testing, and the console description field displays this: {user:connected_user,password:password_in_plain_text}. I haven't made any special adjustments, and yet I'm potentially seeing all the passwords of the connected users (it's not a major issue at the moment), but I need to find the source of this so I can stop seeing this information.

If you have any ideas, I'd appreciate it.
Sincerely,
Alexandre
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

March 19, 2026 - 11:12

Your behavior is very strange.

Can you give me the value of

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\SrvComment

on the machine?
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

March 19, 2026 - 11:29

One more thing: if you do

`wapt-get register toto`,

it will add `toto` to the description.
Answer