Tranquil IT Forum

Hello,
what is the correct procedure when cloning a PC with a utility like Clonezilla? Since the 1.5 update, I always have to reinstall the client on the cloned PCs.
Let's say I clone PC01 to PC02: on the first boot of the cloned PC, I rename it PC02 and change its IP address. When I restart Windows, PC01 is automatically renamed PC02 in the console but shows "disconnected". And if I run "wapt-get register" on PC02, it creates a second PC02 in the console, but with the "clock" icon.

https://image.ibb.co/gsmH2S/wapt.png

Hello Gaelds,

gaelds wrote: ↑Apr 20, 2018 - 8:36 AM What is the procedure to follow when cloning a PC with a utility like Clonezilla? Since the 1.5 update, I always have to reinstall the client on the cloned PCs.
Let's say I clone PC01 to PC02: on the first boot of the cloned PC, I rename it PC02 and change its IP address. When I restart Windows, PC01 is automatically renamed PC02 in the console but shows "disconnected". And if I run "wapt-get register" on PC02, it creates a second PC02 in the console, but with the "clock" icon.
https://image.ibb.co/gsmH2S/wapt.png

In version 1.5, the WAPT client uses the BIOS UUID as the machine's unique identifier, unless otherwise specified in the configuration file (see the `use_fqdn_as_uuid` parameter in the changelog) https://www.wapt.fr/fr/doc/changelog.ht ... re-globale (I'll check with Simon to add it to the documentation).

The problem you're facing is likely related to corrupted BIOS UUIDs, such as 0000-0000-000000-..., which are the same across multiple machines. If you're experiencing this issue, you can use the setting mentioned above; that should resolve your problem.

We're considering adding a script to the installation that regenerates the UUID if it's one of those known to be problematic. However, this will also cause other issues during cloning. To be continued.

Sincerely,

Denis

No, strangely enough, the UUIDs seem correct. Today, these are brand new Vostro laptops; this has happened on other models. The second cloned PC took the place of the original model in the console. And it was after running `wapt-get register` that it obtained a different UUID, and a new line appeared in the console. Since it remained on the clock icon, I uninstalled and reinstalled the WAPT client, and it is currently reinstalling all the packages that were already present.

Here is a screenshot of my console with commentary:

https://image.ibb.co/bzTNK7/Console_WAPT.jpg

You can see that the old P1 registration in the database has kept its UUID and the correct Dell serial number, but it is renamed P3 and has the P3 IP address. It's probably best not to reboot the cloned PC directly onto the network, but in this case, the pre-configured Wi-Fi started automatically at boot.