Details on that device though point to it being an ACPI device so it’s likely some virtual power thing. 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. 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. I was thinking today, “Hey, why don’t I try and install the tools from the ISO directly?” That is exactly what I did. 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.
0 kommentar(er)
