Reading Time: 2 minutesUsing the legacy vSphere Client is no more possible in vSphere 6.5, but with the previous version is still an option. Unfortunately, it lacks not only in all the new features but also in consistency and error reporting.
A curios issue was with a vSphere 6.0 environment where a generic warning message appears on the Summary tab of the ESXi hosts. The error was a generic “Consiguration Issues” message.
This message doesn’t help so much, but the same message appears in a totally different way in the vSphere Web Client:
In this case is clear what’s happen and it’s related to a new feature of version 6.0: the root account can now be locked out. On the Tasks & Events tab/Events button there was a warning every time the ‘Configuration Issues” appeared.
The reason was a buggy monitoring Nagios plugin with expired credentials that was not evident in the 5.5 version.
Related Posts
-
Bye bye vSphere Client, finallyFinally VMware has announced some good news about the vSphere clients: for the (old/legacy) C# client and the web/flash one: the C# client (AKA Desktop Client/thick client/vSphere Client for Windows) will not be available for the next version of vSphere (finally!). Current versions of vSphere…
-
Bye bye vSphere ClientIn the previous new products release we have notice several changes in some core parts, and several components are gone (see What’s in and what’s out). Now with the new vSphere 5.1 a new historical component (from the VI 3.0) will die soon: the vSphere…
-
Flash issue with vSphere Web ClientThe latest Adobe Flash update (note that the update has been included also in Microsoft Update) with v 27.0.0.170 make the vSphere Web Client no more usable with all browsers. With Chrome and Firefox, you will recognize that the Flash plugin hangs, in Internet Explorer, you…
