Update: If, like me, you only have the 6.0.0 version of the VCSA available to download, check out this post for how to install Update 1 to get the VAMI back. Thank you Christian for the reminder on the VAMI being brought back
As some folks may recall from last years #vDM30in30, I run my home lab on a single 8-core AMD box with all of the hosts nested. I do, however, prefer to run certain virtual machines such as my Domain Controller and vCenter Server in Workstation as well, so I can have those powered on without having to worry about host issues (after all this is a lab and I h0rked up my ESXi 5.5 hosts pretty good doing some testing).
Since the new vCenter Server Appliance (VCSA6) has a new deployment method, installing it in Workstation is not obvious, however Florian Grehl has a great write up on how to do just that - Thanks Florian. Once you have it deployed, there are a few things to take care of that the installer would have otherwise handled.
- Log into your DNS server/Domain Controller and create an A record for the VCSA6. This has to be done in advance of a typical deployment as well.
- Deploy the VCSA using the directions from virten.net
- Log into the vSphere Web Client for the VCSA you just deployed
- Click on System Configuration >> Nodes >> <Your VCSA6 Node> >> Networking
- Edit the hostname and DNS server to match your environment
- Next, navigate to Active Directory and click the Join button. Enter the details for your domain
For me, using the current latest version of the VCSA6, I did not receive an acknowledgement that the join was successful, however if you check AD you should see the computer object created in the OU/CN specified.
- Reboot the VCSA6 (Right click on the node in the vSphere Web Client and select Reboot). Since this is deployed in Workstation, we can monitor the progress of the restart there.
Once the VCSA6 completes the restart, you should now be able to access the vSphere Web Client by its FQDN. If you navigate back to the node, you can now see that it is joined to the domain
At this point, I would normally set the NTP server as well, however I don’t see an option to do so through the vSphere Web Client. There is where updating to Update 1 comes in handy, as the NTP server can be set through the new HTML5 VAMI (https://<vc-fqdn>:5480). See this post if you had to download the 6.0.0 version of the VCSA to install Update 1.
Next, you will need to configure SSO. Navigate to Administration >> Single Sign On >> Configuration. Here you can update the policies, and add AD as an identity source. Time to get my lab reconfigured!