Hello,
I recreated the images of an entire room of Windows 10 PCs using my Fog server. Now, only the last PC on which I ran `wapt-get register` appears in the console. What is the procedure to ensure that Wapt correctly recognizes all PCs after cloning? I am using Wapt 1.8.2 on a Debian server.
PCs cloned with Fog
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
Hello,
Normally, to clone, you use sysprep to ensure each machine is unique.
Alternatively, it could be a CM issue where the same number is being given; there's a command to regenerate it: `wapt-get generate-uuid`.
I encountered this problem on all-in-one MSI systems.
Normally, to clone, you use sysprep to ensure each machine is unique.
Alternatively, it could be a CM issue where the same number is being given; there's a command to regenerate it: `wapt-get generate-uuid`.
I encountered this problem on all-in-one MSI systems.
-
dcardon
- WAPT Expert
- Messages: 1932
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hello Gaelds,
Sincerely,
Denis Cardon
As jpcrna mentioned, the problem stems from "perfect" cloning. The default unique identifier is the BIOS UUID, which is supposed to be unique. Some manufacturers may mistakenly ship machines with identical UUIDs, either through carelessness or by mistake. In this case, you must force a different UUID using the `generate-uuid` command, or use the machine's FQDN as the unique identifier; see the documentation.gaelds wrote: ↑Sep 14, 2020 - 4:55 PM Hello,
I recreated the images of an entire room of Windows 10 PCs with my Fog server. And now, only the last PC on which I ran `wapt-get register` appears in the console. What is the procedure to get wapt to correctly recognize all the PCs after cloning? I am using wapt 1.8.2, Debian server.
Sincerely,
Denis Cardon
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
