Tranquil IT Forum

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.

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.

Hello Gaelds,

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.

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.
Sincerely,
Denis Cardon

Thanks for the reply! Indeed, in that room the PCs reappeared in the console after a generate-uuid.