As of ESXi 6.5 the vSphere Client is no longer supported.  This is a bit of a disappointment.  I was so used to the vSphere Client that when I started using the Web Interface I discovered very quickly that I couldn’t easily find a lot of things where I was expecting to.  The interface is nice and visually appealing, but some of it’s functionality still needs some work.

For example, I recently built a server with 6 NIC’s.  The default configuration assigned all six physical network adapters to “VM Network” which included the Management interface.  Well, I figured since I have this many NIC’s in a server, with a limited number of VM’s, I could afford to set two dedicated Management NIC’s and have four to service the VM’s.

After a lot of exploring I discovered that removing “uplinks” to the pre-existing virtual switch was simple enough.  I created a new Port Group and Virtual Switch easily enough.  But then adding those newly released NIC’s to the new Virtual Switch I created turned into a nightmare.  Only through sheer perseverance did I determine that the “Add Uplink” button provided in the list view of the Virtual Switches is completely broken.  You have to open the Virtual Switch itself, then edit it’s properties, whereupon you find another “Add Uplink” button.  This button works. 

Another issue I found was when creating a new VM, the default hardware model (Compatibility) is set to ESXi 6.5 in the menu drop-down, but the other two selection (Guest OS family and Guest OS version) remain blank.  Until you switch Compatibility to something else, then back, you cannot select either of these values.  And until you do select those values, you cannot create a VM. 

Perhaps it’s just me, or my browser, because I tried to duplicate these issues on a client site and failed to do so.