In vSphere 6.0 the vCenter Server Appliance (vCSA) has been changed a lot. Joining an Active Directory Domain is now included in the infrastructure node configuration which is part of the Platform Services Controller. Please note standard AD requirements like time synchronisation and naming. You can't join an AD if you've set an IP address as name during the VCSA guided installer.
- Open vSphere Web Client (https://[vcenter]/vsphere-client)
- Login as Single Sign-On Administrator (Password set during installation)
- Navigate to Administration > Deployment > System Configuration
- Open Nodes and select the infrastructure node that is associated with Single Sign-On
- Navigate to Manage > Advanced > Active Directory
- Click Join...
- Enter AD domain information
- Press OK
- Reboot the Appliance
When the appliance comes back up it is now part of the Active Directory Domain. The next step is to configure the AD as identity source to login to the vCenter with AD credentials.
Thanks for posting this, however it is not working for me.
I've added the server to our domain, and it adds the computer in AD, but vcenter does not show up as being in a domain once rebooted. It's as if the system doesn't finish the process. Any thoughts on this or suggestions on where I can look to troubleshoot further?
I have the same problem as Derek
@Ivo @Derek, were you guys able to fix this ?
Mine solution was to change NETBIOS name of the AD Domain to uppercase
Had to open up ports on the AD firewall (LDAP, etc) to get it to work.
I have the same. Did a domain join with the PSC UI. One of the two PSC is shown in VC as joined. The second does not show up.
Since the PSC itself shows the domain and the computer account exist in AD, how to convince the VC to show it correctly?
Pingback: vcenter 5.5 manage 5.1 | manage my link
I've had the same issue with VCSA 6.0 u2 , I was unable to join this Domain using GUI then, I tried using SSH of VCSA using domain joined command, it was successful.
However when I tried to add Identity sources it was still showing VCSA need to be joined in Domain.
I think its an issue with VCSA 6.0 U2 3634794 build, When I tried same thing in U3 version it went well without any issues.. I have spent hell lot of hours to identify the issue