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
WADS and uuid
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
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
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.
, 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.
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
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.)
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.)
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
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.
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.
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
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.
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.
