Got an idea for a new feature? Maybe a tweak to make something work even better? Wish there was an integration with another product to make you even more productive? You've come to the right place.
The Product Ideas Portal lets you submit whatever product feedback you have, good, bad, ugly, and anywhere between.
Want to stay anonymous? Don't worry, no email address or name fields are shared on the public portal. You can create an account which lets you vote on other people's ideas and receive updates when your idea's status changes.
To learn more about how an idea becomes a feature, check out this infographic.
The license of some software products in our data center is bound to the hostname. To make sure the license check is OK we set the "hostname" different to what we consider the physical hostname and what should be used to register the node in AD.
To give an example: output of "uname -n" and "hostname" is different, depending on which physical host is currently the active cluster node:
# Host 1 is PowerHA active node:
# ==============================
Host 1 $ uname -n
host1
Host 1 $ hostname
virtualhost
Host 2 $ uname -n
host2
Host 2 $hostname
host2
# Host 2 is PowerHA active node:
# ==============================
Host 1 $ uname -n
host1
Host 1 $ hostname
host1
Host 2 $ uname -n
host2
Host 2 $hostname
virtualhost
When joining both nodes one host is joined as "host1" or "host2", and the other one is joined as "virtualhost".
So we are looking for a trick to force a certain name for the join other than the hostname output. Preferably a domainjoin-cli switch like "--adname" or the "uname -n" output. Or the possibility to rename the node after the join.