Which client to manage a simple ESXi 6.5 server ?

[AlexLaforge]

Hi,

I'm relatively new into VMWare ESXi, and very confused.

Basically, I own a single ESXi 6.0 Server, wich I administrate with the Windows vSphere Client 6.0

I will to upgrade the ESXi to 6.5 (VMware vSphere Essentials Kit), and I'm afraid how will I be able to administrate it, because it is a simple single ESXi server, managed WITHOUT vCenter. And I do not want to buy any additional vCenter license.

I am wondering which solution will suit for me to administrate this ESXi server remotely. Should I use ? :

- vSphere Client ( I assume that the "vCenter Server Essentials" shipped with vSphere 6.5 is that purpose..a sort of "light vCenter") ?

- vSphere Embedded Host Client (not Fling) - already integrated into the 6.5 setup ?

- vSphere Host Client (Fling) I need to download ?

- vSphere Web Client (but my ESXi server is not run under a central vCenter) ?

So much options, and very confusing !

Actually, my ESXi 6.0 server cannot be accessed from ANY of the following URL's : (I changed the IP for privacy reasons)

https://195.154.111.11/vsphere-client

https://195.154.111.11/ui

http://195.154.111.11:5480

https://195.154.111.11/psc

Thank you for your help.. because I do not want to upgrade to 6.5 and become unable to manage my ESXi !

[Mattallford · Accepted solution]

‌Hi there,

Yes, the amount of clients for a new comer to the VMware world can be a bit confusing.

The direct answer to your question is that you should use the embedded host client (EHC) (https://FQDN/UI) to manage a 6.5 ESXi host that is not being managed by vCenter Server.

The EHC is included from ESXi 6.0u2 onwards, so maybe your ESXi server is currently not running 6.0u2 or later.

The client you are currently using to manage ESXi 6 (Also known as the "C sharp" or "thick" client) can not manage an ESXi 6.5 host.

Cheers, Matt.

[AlexLaforge]

Hi Matt,

First, I thank you for your lean and clear answer : having a certainty in this world is a so satisfying must-have !

Yes, I am Running ESXi 6.0.0, and not 6.0u2, so that explains why the https://FQDN/UIhttps://FQDN/UI address cannot be accessed at this time.

So to reformulate you and be sure that I understand you well : Once I will have upgraded to ESXi to 6.5, this https://FQDN/UI address will become available, am I right ?

NOTE : in place of the FQDN, there will be the IP address of my ESXi server, is that OK ?

Cheers, Alex

[MattiasN81]

Correct, you can use IP if you want.

In 6.5 you dont need the /ui in the end, it redirects automaticly

just goto https://ESXI-IP-ADRESS