3/31/2019by admin

Vmware Thick Client

heavenlyuniversity.netlify.com › ▲▲▲ Vmware Thick Client ▲▲▲

I know VMware has provided the support for HTML5 based client to manage the VMware host.We want to use vSphere client6.0 to manage VMware ESxi 6.5u1.

I have one vSphere client with version 6.0 and two ESXi server with version6.5 and 6.5u1.

I have observed the below behavior of vSphere client and ESXi server.

I am able to access VMware 6.5 with vSphere client6.0
I am unable to access ESxi6.5u1 with vSphere client6.0 . It give me options for run installer or Save installer.

Can you please reply on my below queries?

if a can open ESXi6.5 with vSphere client6.0 then why i cannot open ESXi 6.5u1??
Where VMware has documented the compatibility of vSphere client with ESXi server?

Thanks in advance!!!

ajayajay

1 Answer

The compatibility matrix for the vSphere thick client is located here: http://partnerweb.vmware.com/comp_guide2/sim/interop_matrix.php#interop&24=&1=

I believe the thick client being operational with 6.5 ESXi hosts was a bug, and it was resolved in 6.5U1.

Also, be aware that the thick client has been deprecated and will no longer be available on future versions of vSphere: https://blogs.vmware.com/vsphere/2016/05/goodbye-vsphere-client-for-windows-c-hello-html5.html

Kyle RuddyKyle Ruddy

Not the answer you're looking for? Browse other questions tagged vmwarevirtualizationvsphereesxi or ask your own question.

Did you notice what the VMware vSphere 6.5 Release Notes mention, at this spot? Those are the (finalized?) client UI names! Yep, get ready for this:

Components of VMware vSphere 6.5, including vCenter Server, ESXi, the vSphere Web Client, the vSphere Client, and the vSphere Host Client do not accept non-ASCII input.

Let's reformat that:

vCenter Server
ESXi
vSphere Web Client
vSphere Client
vSphere Host Client

Yeah, we're stuck with vSphere Web Client for a while longer, since the vSphere Client functionality is not all there yet, details here:

Functionality Updates for the vSphere Client
Updated on: 15 November 2016
vSphere Client 6.5 15 NOVEMBER 2016 ISO Build 4564106
The Unsupported Functionality table documents the vSphere Web Client workflow functionality not available in the vSphere Client at the release of VMware vSphere 6.5. Any vSphere Web Client functionality not documented in this table is supported in the vSphere Client at release. Check periodically for updates to the Unsupported Functionality table.

#rant start
Interested in my original piece about this transitional state we're still stuck in? See:

VMware announced there's no vSphere Client for Windows for the next vSphere release, HTML5 web UIs are the future, forcing us to suffer vSphere Web Client during this transition
May 18 2016

# rant end

Going forward, I continue to try to avoid any videos that feature the relatively sluggish vSphere Web client, to reduce obsolescence, and because the HTML5 UIs are much more pleasant and faster to use. Sure wish VMware development dollars were directed at dumping Adobe Flash/Flex earlier.

We'll get there, fewer better UIs, but we're just not quite there yet.

vSphere Client for Windows still works, sort of...

Oh yeah, didn't VMware say this about vSphere 6.5:

...the C# client (AKA Desktop Client/thick client/vSphere Client for Windows) will not be available for the next version of vSphere?

True, no 6.5 version of it exists for download at the usual Download URLs for VMware vSphere Client [KB2089791]. But guess what? The VMware vSphere Client 6.0 Update 2 still works! That doesn't mean it is supported, or that you should use it, given a lot of the newest and most innovative features can't be configured with it. But at least VMware doesn't block you from logging in and using it, I suppose to appease customers with mixed environments, at least for a while longer. It only works connected to ESXi 6.5, won't connect to VCSA, seen below.

Nov 17 2016 Update

Have you noticed what happens when you point your browser to the VCSA appliance? Yeah, multiple options, with the cling to Flash disclosed in that first link for the still-needed vSphere Web Client. At least they explained it, and made it easy to launch from there.

The big news is that the vSphere HTML5 Web Client is now baked right into the VCSA 6.5 appliance, seen as the second link below. This is MUCH less clumsy than the standalone appliance you had to configure for the 6.0 compatible version.

So fingers crossed that VMware rips off this bandaid as soon as possible and gets the HTML5 UI fully equipped to handle all vSphere functions as quickly as possible, without making us wait for the next major release (vSphere 7.0?). I say this because of the 20-months-between-major-releases cadence of late. Probably wishful thinking, but one can always hope.

Comments

Share your feelings about this transitional state we're in below! Don't miss reading about the UI purgatory that Reuben Farrelly is stuck in with his Nexus 1000V issue.

heavenlyuniversity