Unable to Join AD domain Error: Required configuration stage not enabled [code 0x0000a606]

Products

• VMware vCenter Server
• VMware vSphere ESXi

Issue/Introduction

When Joining the VC to the  Active Directory Domain you get an error similar to:

Error: Required configuration stage not enabled [code 0x0000a606]
 
The configuration of module 'set computer hostname' is required. Please either allow this configuration stage to be performed automatically (by passing '--enable hostname'), or manually perform these configuration steps and rerun the domain join:
 
The following step(s) are required:
    Change the fqdn from 'vcenter01' to 'vcenter01.fqdn.dom'. The current fqdn is invalid because it does not contain a dot in the name. Changing the fqdn could be done via DNS, but this program will change it with the following steps:
        * Making sure local comes before bind in nsswitch
        * Adding the fqdn before all entries in /etc/hosts that contain the short hostname and removing the old fqdn if it appears on the line
        * Restart nscd (if running) to flush the DNS cache

Environment

VMware vSphere ESXi
VMware vCenter Server

Cause

The vCenter /etc/hosts file contains a bad format with only the vCenter short name 
The vcenter  Hostname has been modified via /etc/hosts file and it is either incomplete or does not have the  correct format.

Resolution

In order to solve the issue follow these steps.

• check if vCenter is already showing up as joint to a domain with command  /opt/likewise/bin/domainjoin-cli query
• If joint to domain, leave domain by  using command  /opt/likewise/bin/domainjoin-cli leave
• Reboot the VCSA.
• Once rebooted Join domain with command  /opt/likewise/bin/domainjoin-cli --loglevel verbose --logfile /var/log/domain.log join  <Domain> <username> <Passwd>
• If able to Join proceed to reboot VCSA and then reconfigure AD as IS.
• If you get error  Error: Required configuration stage not enabled [code 0x0000a606]. 

The following step(s) are required:
    Change the fqdn from 'vcenter01' to 'vcenter01fqdn.dom'. The current fqdn is invalid because it does not contain a dot in the name. Changing the fqdn could
    be done via DNS, but this program will change it with the following steps:
        * Making sure local comes before bind in nsswitch
        * Adding the fqdn before all entries in /etc/hosts that contain the short hostname and removing the old fqdn if it appears on the line
        * Restart nscd (if running) to flush the DNS cache

• Edit the vCenter DNS settings with /opt/vmware/share/vami/vami_config_net   
• press option  0 to check configuration. 
• then use option 4 to edit the two DNS servers, add the search path an the domain name by entering them manually.
• Exit the tool with option 1.
• Check dns resolution in both directions forward and reverse lookupzones using commands nslookup VCSAFQDN     and nslookup  vcenterIP
• Finally, check the /etc/hosts and the /etc/resolv.conf files to make sure the names are correct and DNS settings are correct.
• Try Joining the  Domain again by using command  /opt/likewise/bin/domainjoin-cli --loglevel verbose --logfile /var/log/domain.log join  <Domain> <username> <Passwd>
• Reboot the VCSA.
• Reconfigure Identity Source. (Integrated Windows Authentication IWA /LDAP/LDAPS)

Additional Information

VMware vCenter Server Appliance hostname and DNS configuration are reverted after a reboot
https://knowledge.broadcom.com/external/article?articleId=344865