Hello,
I've VCSA 7.0.3 running on one of two ESXi hosts. Tried to join VCSA to DC (vm, Win Server 2019, functional domain level 2016) but in Administration\sso\configuration menu - there're no available buttons to join, just text: "There are no nodes"
I've checked with vami FQDN is right, DNS resolves both sides.
I used cli - opt/likewise/bin/domainjoin-cli join and it worked. I've got the message that join is sucesseful. In DC Users and Computers I've an instance of the VCSA.
But in administraion\sso\configuration I still have no nodes, no available buttons and can't change default sso domain.
Please can somebody advise me what's the problem?
With technical support we made some fixes with certificates but it didn't help. And as I have a small configuration of hosts and vms we decided that the easiest way to fix the problem is to re-install the instance of VCSA 🙂
And the advise was to use VCSA 7.0.2d as the most stable (support doesn't like 7.0.3 versions) as I have hosts running under 7.0.2 version.
Hope it'd be helpful for me.
share print screen please
By default, only the administrator@vsphere.local has permissions for this. Can you confirm that you logged in to the vCSA that way?
André
Yes, I've logged in with administrator@vsphere.local and didn't change any roles and rights.
i know you are using VCSA 7 but this KB address same issue
https://kb.vmware.com/s/article/2118543
try to use Supported Browser Versions
I've already used cli and successfully joined domain but I can't change default sso domain in web client (vsphere.local) to use AD accounts. Also tried to use different browsers.
I can't unfortunately tell you whether this is a bug in this version?
Anyway, since Windows Integration is a deprecated feature, why don't you instead configure LDAP?
André
Yeah, I will probably do this, but still I'm trying to undersatnd is it a bug and it's the only problem with VCSA. Or maybe I ruined something and someday I will loose connectivity to hosts and VMs 🙂
Did you try by root
With technical support we made some fixes with certificates but it didn't help. And as I have a small configuration of hosts and vms we decided that the easiest way to fix the problem is to re-install the instance of VCSA 🙂
And the advise was to use VCSA 7.0.2d as the most stable (support doesn't like 7.0.3 versions) as I have hosts running under 7.0.2 version.
Hope it'd be helpful for me.