Instead of using the vSphere Client to mount VMware Tools ISO files, you can also use a repository provided by VMware to download the package. In my opinion, this is much more comfortable. You copy the installation package to your fileserver and install VMware Tools without having to use the vSphere Client.
Running an ESXi as Virtual Machine inside VMware Worksation or on another ESXi gets more and more useful for testing purposes. That installation, also called "Nested ESXi", is not officially supported by VMware but some VMware developers are willing to help in the VMware communities Nested Virtualization forum. Up to this point is was not possible to install VMware Tools on a nested ESXi, making the management a little bit cumbersome. During VMworld 2013 in Barcelona the news about an upcoming Fling called "VMware Tools for Nested ESXi" came out. The Fling contains a small vib package that can be installed on a virtual ESXi Host.
When you virtualize Linux Operating Systems with VMware you have 3 opportunities when it comes to the decision which VMware Tools to install. The well-known VMware Tools that come with the ESXi Hypervisor and can be installed from the vSphere Client, the VMware Operating System Specific Package (OSPs) and the open source project open-vm-tools. This post explains the differences between the variants and helps you to understand the advantages to choose the right package for your environment.
If you use Linux Guests inside VMware I encourage you to comment on what kind of VMware Tools you are using.
When you select Debian or Ubuntu as Operating System during the creation of virtual machines the wizard automatically selects E1000 as virtual network adapter. To get better network performance it is a best practice to change this to vmxnet3. But what if the virtual machine is already installed and running? The Adapter Type is grayed out, even when the virtual machine is powered off. How to change the Adapter Type later?Read More »Migrate E1000 Adapter to vmxnet3 with Linux Virtual Machines