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
PC cloning
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
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
-
dcardon
- WAPT Expert
- Messages: 1930
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hello Gaelds,
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
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).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
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
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
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
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.
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.
