Latest VMware tools package and version numbers

I was trying to figure out where can I find the latest VMware tools package and what build versions were released with what ESXi host build? And voila, all the information is already published by VMware.

The latest VMware tools package is always referenced at the following URL:

Where as if you need to know what VMware tools versions were released along with which ESXi host builds, then you can find that answer at the following URL:


Windows 2003 VM Guest customization no longer supported

Today I deployed a Windows 2003 VM in a test infrastructure. I did not want to spend too much time installing and configuring the OS hence thought of using Windows 2003 instead of something like a Windows 10 or Windows 2016. ‘

Why  I still use and love to deploy Windows 2003 in my test environments? The reason is very simple:

  • Windows 2003 works very well in a nested environment
  • Windows 2003 virtual machine has a small  footprint does not require a lot of RAM nor does it require a lot of disk space.
  • Finally the important part; Windows 2003 was supported by VMware for guest customization under vCenter

Now here is twist in the story, I was trying the guest customization of Windows 2003 in vCenter 6.7 and guess what it failed. I did a bit of investigation why this was happening. I never expected VMware would stop supporting Windows 2003 guest customization under vCenter 6.7, but that’s exactly what the story is. VMware no longer supports Windows 2003 guest customization starting from vCenter 6.7

Here is the support document from VMware, that states Windows 2003 is no longer supported under vCenter 6.7:



Powercli oneliner for changing MTU to 9000

I wanted to set MTU on number of standard vSwitches across multiple ESXi hosts and Powercli made that job easier. Here’s a oneliner to get the job done across multiple vSwitches.

Get-VMHost My-ESXi-Host| Get-VirtualPortGroup "PG_SearchString*" | Get-VirtualSwitch | Set-VirtualSwitch -Mtu 9000 -Confirm:$false



Space Reclamation in VMFS 6

VMFS6 file system was in vSphere 6.5. Of the many new features introduced with VMFS6, one of the notable features is Automatic Space Reclamation.

Automatic space reclamation, also sometimes referred to as UNMAP is a feature that allows the hypervisor (vmkernel) to reclaim space when files (data) are (is) deleted from a virtual machine with a thin provisioned disk. The following video from VMware Tech Pubs provides an ease way to understand the same.


Find aggregate allocated VM CPU and Memory per host basis

Here’s a quick and dirty one-liner to find the total allocated CPU & Memory per ESXi host basis. This is useful when you want to get a quickly get your over-commitment ratios.

$TotalMem=0; Get-VMHost myESXiHost1 | Get-VM | ?{$_.PowerState -match 'PoweredOn'} | %{$TotalMem=$TotalMem+$_.MemoryGB};Write-Host $TotalMem
$TotalCPU=0; Get-VMHost myESXiHost2 | Get-VM | ?{$_.PowerState -match 'PoweredOn'} | %{$TotalCPU = $TotalCPU+$_.numCPU};Write-Host $TotalCPU