As of vSphere 6.7 Update 1, the vCenter vSphere Client (also referred to as the HTML5 client) has reached feature parity with the now deprecated Thick Client and Web Client. But one of the biggest annoyances with the vSphere Client is the default Session Timeout value of 120 minutes. It seems like I’m constantly re-authenticating. Good news, this can be easily changed from the vCenter Appliance Shell.(more…)
Recently I started receiving the error “VMware Remote MKS has stopped working” when starting, rebooting, and shutting down virtual machines with the VMware vSphere Client console. I searched the VMware community forums and was overwhelmed with the amount of ignorance. It turns out the problem is caused by overlapping versions of the vSphere Infrastructure Client.
It appears that the VI Client for vSphere 6 relies on the version 5.5. This is fine until you need to install version 5.1 of the VI Client which overwrites some registry values causing version 6 to become unstable. Luckily the user enriquepessoa on the VMware community forums has a solution by running a simple registry file which can be downloaded from this thread, https://communities.vmware.com/message/2576374#2576374. I no longer receive the error “VMware Remote MKS has stopped working” when starting, rebooting, and shutting down virtual machines.