#VMWARE TOOLS FOR WINDOWS 10 ESXI 5.5 HOW TO#
#VMWARE TOOLS FOR WINDOWS 10 ESXI 5.5 NO CD#
#VMWARE TOOLS FOR WINDOWS 10 ESXI 5.5 INSTALL#

#VMWARE TOOLS FOR WINDOWS 10 ESXI 5.5 NO CD#

There is no CD mounted in the guest OS so there’s not much that can be done. Update: VMware has released an independent package VMware Tools 11.0.5.Since several releases, VMware tools are released independently from ESXi hypervisor images. Enabling the VMware tools installation results in a brief white window flicker and then nothing. NEXT release in the list, which should be released anytime soon.

#VMWARE TOOLS FOR WINDOWS 10 ESXI 5.5 HOW TO#

So anyway this is nothing revolutionary but it shows how to get VMware Tools properly installed in Windows 10 Server Technical Preview. So as could be expected, Windows 10 Server (Tech Preview) has no clue what to do with VMware tools when running VMware ESXi 5.5 which I guess is not entirely surprising. You’ll also see the unknown device above which I hope to sort out if possible.

Here you see we’ve got the VMXNET3 adapter working properly:Īnd here’s the device manager view showing the interface properly: Details on that device though point to it being an ACPI device so it’s likely some virtual power thing. The option to clobber Linux kernel modules that are included with the operating system using VMware Tools installer has been removed and no longer supported. See VMware Compatibility Guide for more information. It all works! Proper capturing of the cursor in console works as well! The only problem is that there still remains an item in device manager that is unknown. VMware Tools 10.2.5 is compatible with supported versions of VMware vSphere ESXi 5.5 and later, VMware Workstation 14.0 and VMware Fusion 10.0. At this point you can remove the 1000E or E1000E NIC you had and add a VMXNET3 adapter. That’ll kick off the VMware tools installation, simply click on typical, then next a few times, and you’re done. Mount the windows.iso file to the VM and then connect to the VM either through console or RDP, open the CD, and click on setup64.exe: In that folder there’s a tools-isoimages folder, and under that a file called windows.iso: When you check out your datastores in vSphere Client, you’ll see you have access only to your VMs and maybe any ISO’s you’ve uploaded to the datastore, for instance:īut, if you go to mount an ISO on a VM you’ll see that above any datastores you created there will be a vmimages folder.

#VMWARE TOOLS FOR WINDOWS 10 ESXI 5.5 INSTALL#

I was thinking today, “Hey, why don’t I try and install the tools from the ISO directly?” That is exactly what I did. It is possible to use nested virtualization to run VMware ESXi as a Virtual Machine in Hyper-V.To some, this may be a viable option if you are unable to acquire any new hardware, or if you simply want to test new VMware products on your Windows 10 desktop. I was using the conventional method of using Install/Upgrade VMware Tools from the “VM” menu, then the “Guest” option. Hey everyone – if you follow my blog you probably remember me mentioning the other day that I was unable to get the VMware tools to install for ESXi 5.5 in Windows 10 server.

Vmware tools for windows 10 esxi 5.5