When trying to join a server with the same hostname but different FQDN from a server that is already joined to AD an error is returned saying that an object with that name already exists. The -n option is being used in the join command to specify the FQDN for the computer object, but this doesn't seem to be making a difference.
If you specify a computer object name as a FQDN such as linux01.test.com, only the hostname part of this name (the part up to the first period) is used for the AD "name" attribute as well as in the servicePrincipalName attribute. This will cause a conflict if you have another system joined with the same hostname, even if the full named that is passed in is different.
© 2024 One Identity LLC. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center