This assumes vCenter is being deployed on a new windows 2016 server – standard edition, that has been added to the local domain and has a static IP.
In this case it is being deployed on a VM with a hostname of dartagnan.home.lab with an IP of 192.168.0.10. It has 2 vProcessors, 8GB of RAM and 60GB of disk space. The VM has been added to an Active Directory domain which will later be used as an identity source.
The VMWare-VIM-all-6.7.0-8217866.iso has been mounted from a datastore to the CD-Rom of the VM.
On he VM open a windows explorer window:
If you double click on the CD Drive in the right pane it will kick off the autorun on the CD. If you do it on the left pane you will need to navigate and run it manually.
Click Yes to proceed.
Click Install to proceed.
Accept the terms and conditions and click Next.
I am going for the embedded deployment with everything on the one server but you can split this out onto multiple hosts or even load balance components.
I have registered my host on the domain and as such there is a DNS has been created for it. If no DNS exists it will complain but allow the install continue with an IP. I prefer to have a DNS name rather than an IP.
With vSphere 6.0 and later, you can give your vSphere domain a unique name. To prevent authentication conflicts, use a name that is not used by OpenLDAP, Microsoft Active Directory, and other directory services. You cannot change the domain to which a Platform Services Controller or vCenter Server instance belongs after the fact.
If I was deploying this in a corporate environment I would be inclined to use a specific service account however, as this is my home lab, I will leave this as the local system account which is sufficient for my needs.
For my needs the embedded DB is fine.
The default ports work as they are but they can be changed to suit different environments.
If it suits to change the install paths, they can be changed here.
I choose not to participate in the Customer Experience Improvement Program.
Take note of the details on this screen. Its worth taking a screen shot.
Launch the vsphere web client and click Finish.
The new HTML5 interface looks pretty slick and a huge improvement on the old flash interface.