Access methods for managing vSphere 6.5

Goals

Inform readers about changes in vSphere 6.5 that affect how vCenter Server and hosts are accessed and managed.

Facts

• vCenter 6.5

• ESXi 6.5

Solution

Starting with vCenter 6.5 and ESXi 6.5 versions, VMware no longer supports using the vSphere Thick Client (C#) to connect to vCenter, or directly to ESXi hosts.

The typical supported methods of interacting with vCenter 6.5 are:

1. vSphere Web Client (Flash) - Familiar interface from vCenter 5.5 and 6.0 runs on the vCenter Server at https://<hostname>/vsphere-client/

2. vSphere Client (HTML5) - Partial functionality only runs on the vCenter Server at https://<hostname>/ui/. Previously was available as a "Fling" for vSphere 6.0, and now is built-in natively to vCenter 6.5

3. Platform Services Controller web interface - Runs on the PSC server(s) at https://<hostname>/psc/

4. vSphere Appliance Management Interface (VAMI) - Only applies to the vCenter Server Appliance (Linux). Runs on the vCenter Server, and external PSCs at https://<hostname>:5480/

5. PowerCLI - Command-line shell run from a remote workstation / server

The typical supported methods of interacting directly with an ESXi host are:

1. vSphere Client (HTML5) - Web service which runs directly on the ESXi hosts 6.0 Update 2 and later at https://<hostname>/ui/

2. DCUI - Direct Console User Interface is available from the server KVM console, or physical monitor/keyboard attachment

3. PowerCLI - Command-line shell run from a remote workstation / server.

4. SSH - Only recommended for temporary troubleshooting access, not for routine use.