Tranquil IT Forum

Hello everyone,

When use_fqdn_as_uuid=1 is used and a machine is deployed with WADS and a djoin, the machine package prepared in WADS doesn't seem to be used afterward.

I suspect that the machine package prepared in WADS is in the form

Are other users experiencing this issue? Is there a way to change the name of the prepared machine package in WADS?

WAPT Enterprise: 2.6.0.17392

Hello

, indeed the workflow doesn't work for `use_fqdn_as_uuid`.

And when we click on it, we don't see the full FQDN (only the short name) in the grid.

At best, we could know it if a `djoin` is entered, or guess it based on the machine's current domain.

I'll see what we can do here to improve this.

Hello,
In my opinion, deducing the package name from the join would be preferable.
Thank you for your reply!

Indeed, if there is Djoin (but there isn't necessarily djoin)

Hello,

Yes, unless `use_kerberos` and `use_fqdn_as_uuid=1` are used together (my case).
But wouldn't it be enough to prepare the machine package with the information available at the time of its creation?
(And if `use_kerberos` is used, to deduce the package name.)

We have two solutions to retrieve the fqdn:

fqdn retrieved from djoin (if djoin is present)
or:
hostname.currentmachine name

and if the console has the conf: use_fqdn_as_uuid=True

then we automatically offer "fqdn retrieved from djoin" if there is a djoin, otherwise hostname.currentmachine name.

Is this something that's already available in version 2.6.1.17567? (I'm still only on 2.6.0.17392)

I took a quick look and found a workaround:

In WADs, in the "uuid" column, you can change the value to "pc-01.mydomain.lan"

, then click "Prepare machine package" and it should work.

Thank you for your response.
Unfortunately, it doesn't seem to work.
Even after modifying the UUID field, the machine package is still prepared with the hostname (and this value doesn't appear to be editable).