VMware vSphere 6.5 is scheduled to reach end of general support 15 October 2022, referenced in the VMware Lifecycle Matrix. See also How to Install vSphere 7.0. Upgrade to vSphere 7 can be achieved directly from vSphere 6.5.0 and above, whereas vSphere 6.0 requires an intermediate upgrade to 6.5 or 6.7 first. For more information see the VMware Upgrade Matrix. Finally, the Windows vCenter Server is now depreciated and not available with vSphere 7.0.

VMware vCenter Server pools ESXi host resources to provide a rich feature set delivering high availability and fault tolerance to virtual machines. The vCenter Server is a centralised management application and can be deployed as a virtual appliance or Windows machine. This post gives a walk through on a clean installation of vCenter Server 6.5 on Windows Server 2016. vCenter 6.5: Download | Release Notes | What’s New | Upgrading to vCenter Server 6.5 Update 1.

Software Considerations

Architectural Considerations

embedded

Hardware Considerations

Other Considerations

Create Data Source

Before beginning if you intend to use vCenter Server with an external SQL database be sure to install the SQL Server Native Client v10 or v11.

You must also configure a 64-bit ODBC data source for external databases. ODBC Data Source Administrator can be accessed via Control Panel > Administrative Tools. Click System DNSAdd and input the details for the external database, test the data source before continuing. If you are using the internal Postgres database then the System DSN is added automatically during installation.

odbc

Installation

Download the VMware vCenter Server and Modules for Windows ISO from VMware downloads: v6.5.0 | v6.5.0 U1.

Mount the ISO and right click autorun.exe, select Run as administrator. The VMware vCenter Installer will open. Ensure vCenter Server for Windows is selected and click Install.

vsc1

The vCenter Server 6.5 Installer will open in a separate window, click Next.

vcs2

Accept the end user license agreement and click Next.

vcs3

In this guide we will be using an embedded deployment model. If you are using an external deployment model the PSC component must be installed first before the vCenter. Select the deployment type and click Next. If the Windows server does not have sufficient resources allocated the installer will error at this stage.

vcs4

Enter the FQDN in the System Name field and click Next.

vcs5

Create a new Single Sign-On domain, or join the vCenter to an existing SSO domain. If you are creating a new SSO domain give this a meaningful name, (not the same as your Active Directory name) the default is vsphere.local. Configure a password for the SSO administrator account and a vCenter specific site name, click Next.

vcs6

Select whether to run vCenter services as the local system account or enter details of a service account and click Next. Ensure the account running vCenter services has been granted permissions as per the other considerations section of this guide.

vcs7

Select an embedded Postgre database or point the installer to the DSN for an external database, click Next.

vcs8

Accept the default port configuration and click Next.

vcs9

Select the directory to install vCenter services and click Next.

vcs10

Tick or untick the VMware Customer Experience Improvement Program as appropriate and click Next.

vcs11

Check the configuration on the review page and click Install to begin the installation process.

vcs12

Once the installation has completed click Finish.

vcs13

Post-Installation

Connect to the vCenter post install using the IP or FQDN of the vCenter. Access vSphere by clicking either the vSphere Web Client (Flash) or the vSphere Client (HTML5). Connect to the vSphere Web Client to manage your system, the thick client (Windows) is no longer supported.

vsphereweb

Log in to the vSphere Web Client using the SSO administrator login. Verify the installed version is correct under the Summary tab when selecting the vCenter, you can also go to Help > About.

vsphereclient

You must apply a new vCenter license key within 60 days. From the Hosts and Clusters view select the vCenter Server. Click Actions and Assign License. Select a license or use the green plus button to add a new license and click Ok.

You can obtain a 60 day trial license for vCenter Server here. If you have purchased vCenter Server then log into your licensing portal here. If the license key does not appear then check with your VMware account manager.

client

If you have an Active Directory domain then vCenter can use this as a source for permissions and sign on credentials. First join the vCenter to the domain; from the home page click System ConfigurationNodes, and select the vCenter server. In the Active Directory section of the Manage tab click Join, input your AD details and click Ok. Reboot the appliance either right clicking the vCenter server under Nodes and selecting Reboot.

When the vCenter server comes back online we can add AD as an identity source; from the home page click Administration, under Single Sign-On select Configuration. Ensure the Identity Sources tab is open and click the green plus symbol to add a source. Fill in the Active Directory details for your domain and click Ok.

identity

You can now add permissions to vCenter objects such as datacentres, clusters, folders, individual virtual machines, etc. for Active Directory users and groups by selecting the object and clicking Permissions under the Manage tab. To learn more about how vSphere permissions work review the vSphere permissions documentation section.