Tranquil IT Forum

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.

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?

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?

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.

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?

In this case, you need to follow a backup/restore procedure:

https://www.wapt.fr/fr/doc/wapt-server- ... html#linux

https://www.wapt.fr/fr/doc/wapt-server- ... html#linux

Hi Yann,

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

Best regards,

Denis

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

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?

One more thing: if you do

`wapt-get register toto`,

it will add `toto` to the description.