Page 1 of 1

[WAPT 2.5 Discovery] Random UUID instead of FQDN

Published: February 8, 2024 - 3:04 PM
by Ellias
Hello everyone,

I'm facing a problem that's causing duplicate machine entries in the WAPT console:

Some time ago (over a year), my agent was regenerated with the specific feature of using only the machine's FQDN. However, I noticed that some machines were returning duplicates (which is normal, since the older ones retained the random UUID). So I performed a thorough cleanup.

Unfortunately, I have machines that are perfectly up-to-date with version 2.5.x (and connected), but they have a random UUID instead of their FQDN. I even tried removing them from the database and reinstalling the agent, making sure it was the correct version. I also tried restarting the affected PC, but without success: it continues to display a random UUID. :|

It's very likely that something is wrong, but I can't figure out what.

Thank you for your help :)

Re: [WAPT 2.5 Discovery] Random UUID instead of FQDN

Published: February 26, 2024 - 10:16 AM
by htouvet
On the machines in question, launch in an administrator command prompt

Code: Select all

wapt-get reset-uuid

Re: [WAPT 2.5 Discovery] Random UUID instead of FQDN

Published: March 11, 2024 - 08:18
by Ellias
Thank you very much, I'll try that

EDIT:
So I just tried it: the command works fine, however it regenerates a random UUID, not the machine's full NetBIOS name. I get this error message:
C:\WINDOWS\system32>wapt-get reset-uuid
Using config file: C:\Program Files (x86)\wapt\wapt-get.ini
2024-03-11 08:48:13,253 WARNING Host on the server is not known or not known under this FQDN name (known as None). Trying to register the computer...
New UUID: rnd-xxxfxxx6-6xxx-4xxx-xx-ax-xb-x6-xx-xx-xx-xx
A wapt-get register -l debug runs without any problem, however, the machine is registered with its netbios name, but it is only an offline duplicate, and the other one always prevails, even after deleting it.

I tried `wapt-get unregister`, then `wapt-get register -l debug` again. The machine reappears in the console, but with a random UUID again...

Re: [WAPT 2.5 Discovery] Random UUID instead of FQDN

Published: June 19, 2024 - 4:07 PM
by Fred91430
While investigating another issue, I discovered that during the management console installation there's an option to automatically generate random UUIDs.
If this option is selected, the agent created with this console will have a random UUID regardless of the initial agent creation settings.