![vsphere client 5.5 windows 8.1 vsphere client 5.5 windows 8.1](https://docs.vmware.com/uicontent/images/vmware-docs-default.png)
- Vsphere client 5.5 windows 8.1 update#
- Vsphere client 5.5 windows 8.1 software#
- Vsphere client 5.5 windows 8.1 windows 8.1#
- Vsphere client 5.5 windows 8.1 windows 8#
I still use FireFox most of the time and IE11 has not had any issues with vCenter since I’ve not accessed vCenter with FireFox.
![vsphere client 5.5 windows 8.1 vsphere client 5.5 windows 8.1](https://blog.proact.de/wp-content/uploads/2018/04/VCSA65_BACKUP.png)
It appears in my case, IE11 and FireFox have an issue. So, I went back through the steps again and now IE11 is working without the message and all functionality is back. The next time I used IE11 I received the above message again. I had used FireFox again since it’s my browser of choice to do some quick tasks in vCenter. Went to the vCenter server URL and logged in.
![vsphere client 5.5 windows 8.1 vsphere client 5.5 windows 8.1](https://www.windowspro.de/sites/windowspro.de/files/imagepicker/13/vsphere-client-neue-vm-disk-controller-typ.png)
Then checked to be sure the FQDN was still in Local Intranet zone. Originally I had saved the Client Integration tools installer versus running it. Right clicked the installer and ran as admin.
Vsphere client 5.5 windows 8.1 software#
Be sure to check the parent folder before uninstalling to be sure you don’t delete other VMware software installation files. Uninstalled the Client Integration tools from Program and Featuresīrowsed to the VMware folder and removed all residuals from the Client Integration tools installation. On this Discussion, I followed ericmowatt and BKNZC’s suggestions with these changes. I added the FQDN to the Local Intranet zone in IE11, but was still receiving the message. Download vmware vsphere client 6.
Vsphere client 5.5 windows 8.1 windows 8#
I had been using IE11 for weeks without issue. .on Windows 8 or 8.1, I suggest you to take a look to this post vmware vsphere client download. I started receiving this message after running Windows Updates on 10 Enterprise when opening IE11. I spoke with a VMware engineer at a VMUG and he stated to use either Chrome preferably or IE11. I had been using FireFox, but there is some functionality that is not working/available in FireFox.
Vsphere client 5.5 windows 8.1 windows 8.1#
It might just be a very early bug on Windows 8.1 and my early suspicions is that it has something to do with software permissions and UAC in Windows 8.1. When you change IE11 back to IE9 compatibility, the option to log in is available, but when ticked, does not pick up your username.Īs I said, I don't know whether anybody else picked up on this and would like to hear your views. I don't think this is necessarily a Vmware or Google problem, because.Ģ)Using IE11 in either Windows 8 mode or Desktop mode, the plugin is not recognised as installed (Option to use local user authentication is greyed out). The remote console option within the web client also prompts for an installation of the plugin. (This will probably be the default for a lot of users, which is fine and hence the absence of related topics on Google Search)Īs soon as you switch Chrome over to Windows 8 mode, the plugin is not recognised as installed (Option to use local user authentication is greyed out) and prompts you to download. When you access the vSphere Web Client on Windows 8.1 -ġ)Using Google Chrome in Desktop Mode, the web integration plugin works fine and you can authenticate with your current AD user account and launch the remote console as well.
Vsphere client 5.5 windows 8.1 update#
The most exciting part of this update is VSAN! VMware VSAN, if you haven’t already heard, is a built-in the hypervisor storage feature that uses locally attached disk and SSD drives to create a storage pool across the entire cluster.I don't know whether anybody else have come across this: