Few reported issues when using domain 2016. msripada any thoughts??
Could you please run the below command and check if the vCenter is part if the domain,
1. Login to the VCSA using putty (SSH)
2. run the below command,
/opt/likewise/bin/domainjoin-cli query
You will get the Domain Name if the vCenter is added to the domain.
Scenario 1: if vCenter is not added to the domain
Please use the below command to join
/opt/likewise/bin/domainjoin-cli join [domainname] [user name] [password]
Then run the below command to check if it's added to the domain
/opt/likewise/bin/domainjoin-cli query
Scenario 2: If the vCenter is already added to the domain
Please check the Time in the Domain controller and the vCenter are the same.
If not please change the time synchronization of the vCenter appliance to the Domain controller IP on the VAMI (https://<fqdn or IP of the VCSA>:5480) page.
It could be due to duplicate srv records https://support.microsoft.com/en-in/help/4496901/windows-dns-registers-duplicate-srv-records-for-a-d...
Can you validate the same?