Ok, I found an answer to all the issues we encountered with vCenter 6. Not the one I was hoping for, but still.
We roll back to 5.5! Neat.
Everything is just normal now - plugins, CPU usage, strange "quick stats is not up to date" messages, even the WebClient is working normal again.
I guess, we'll try once again in a year.
You are right! It is just plain not there in the C# Client!
One minor point, in vCenter, the health status moves to its own tab, not a link on the configuration tab.
Nonetheless, it's not there!
In the dreaded Web Client, you can access health status, but that does me no good as we will not Qualify systems which use Flash. Lack of health status reporting without using the Web Client equals a step backward!
1 person found this helpful
I logged a call with VWMare as I assumed it was a bug. This was the reply.
With the introduction of vSphere 6.0 the support from C# client is slowly
moving away and the Hardware Status tab is ruled out from the C# client, it is
available only in Web Client.
In other words, we removed it by design as we want everyone to use the web client - trouble is they are adopting the "by force" method and not make a "better product method".
I hope they start loosing big money real soon, as this is the only way for them to hear us and make thigs right.
Only then they will finally understand that "something goes wrong" and start pulling back. Like MS, who finally accepted that their stupid, slow and resource hungry "tiles" are just not needed on desktop OS. It was years of agressive pushing this sh*t before they realize that it was wrong.
Current state of affairs is just not acceptable. (flash, need of 2 clients, etc,etc).
I think that decision to remove and abandon C# client is very wrong. (at least until they have fast and bug-free HTML5 client with ALL the features in one place).
And yes, WebClient 6 is even WORSE than tht 5.5 (in my environment) - it even opens from time to time giving unbelievable errors like 403, freezing and lots of bugs just everywhere.
Tail wagging the dog. VMware is TELLING users what they will get and not listening to the people who actually use the product!
Problem is, where truly mission-critical servers are deployed in a high-security environment, Qualification is the rule of the day. New systems must be tested/Qualified, sometimes for months, prior to being placed in production. For many of my clients needs, the web-client will not be utilized as Flash is excluded from mission-critical environments.
Therefore, for all intents and purposes, health status is available in vSphere 5.5 and not available in 6!
Here are topics that might interest people who believe VMware is headed in the wrong direction:
- vSphere Web Client is so bad that my experience managing and supporting VMware has turn to &^#$%@
- Good Bye VMware, Hello OpenStack. PayPal Axes Virtualization Giant - Forbes
- VMware And The Cloud Era - VMware, Inc. (NYSE:VMW) | Seeking Alpha
Oh well. So this explains my problems after installing VCSA 6.0 and adding the first hosts? I'm still not sure about the errors in the plugin view.
vCenter 6.0 do not use HW Status anymore, is only the health tab in vSphere Web Client.
Hope this helps
From version 6 onwards Hardware Tab is removed from vCenter , However same can be found in webclient ---> Go to ESXi host --> Monitor Tab (In right pane) ---> Hardware status.