Well that proved to be a big problem for my VM templates that I use to provision new systems. As soon as VMware Tools is updated on any templates you will no longer be able to clone those templates.If you’ve updated any templates with the version of VMware Tools that comes with ESXi 6.0 U1b then you need to uninstall it and reinstall the prior version that came with ESXi 6.0 build 3247720. I haven’t tested other OS’s yet, but others could be impacted.Instructions: #Enter your v Center Host below $vcenter = "your_vcenter_server" ################################ #Load the VMware Powershell Module Add-PSsnapin VMware. Core #Connect to the v Center server defined above.Ignore certificate errors Connect-VIServer $vcenter -wa 0 #Get the folder name from the user.After the couple of reboots that you have to go through with an uninstall and reinstall of VMware Tools you will find that you can now clone VM’s and have them automatically customized. I’ve logged a support call with VMware to address this problem. The Official VMware KB Article [Updated 14/01/2016] After further testing I have narrowed down the problem area to new installs where the complete option is selected, and any upgrades where the complete options was previously selected, or where the VMCI / NSX Guest Introspection Driver is included.I have been able to successfully clone from a new VM Image that has had a fresh install of Windows 2008 R2 and VMware Tools without the VMCI / NSX Guest Introspection Driver, or where VMware Tools was installed twice / installed and repaired on the same VM, when the complete option was previously selected.
Get-Cluster "Lab Hosts" | Get-VM | Where-Object | Update-Tools -No Reboot In this example I chose my Lab Hosts cluster and updated tools on all VMs that don't have SQL or DB in their names.If VMCI driver is removed by running VMware Tools Install again and selecting Modify and unselecting VMCI, then you will be able to close the VM.Historically, one of my biggest little annoyances with a VMware version upgrade has been upgrading VMware tools.If a folder was provided return only the VM's for that folder If($folder) #Else if the user left the folder blank, get all VM's Else #Perform the following for each VM returned For Each ($vm in $virtualmachines) Remember if you’re running this in Power Shell you still need to load the VMware module and connect to your v Center server first.Updating VMware-Tools on Windows is quite simple, but will require a restart of the operating system.In my case it makes sense to update VMware tools on VM’s in an individual folder (such as test).