Many of our images have older versions of VMware Tools installed. I
don't know of any problems this has caused. Also, VMware Tools isn't
required. I only install it to make controlling the VM through the
vSphere console a little easier.
If you do want to upgrade every image automatically, there is a new
feature in partially done in VCL 2.3 which may help:
It essentially allows you to drop scripts and other supporting files
in the appropriate directories on the management node. The scripts
are automatically run at a particular stage in the reservation. One
of the intended uses is to allow customizations to be performed
automatically before an image is captured such as installing/upgrading
software. You would only need to add a couple lines to image.pm to
enable this functionality. You would save the VMware Tools .msi and a
script which installs it in tools/Windows/Scripts/pre_capture. During
capture, the files in the directory are automatically copied to the
computer and the script is executed. Let me know if you want to try
On Fri, May 18, 2012 at 9:40 AM, Dmitri Chebotarov <dcheb...@gmu.edu> wrote:
> We plan to update VCL ESXi hosts and it will require VMware Tools update for
> all VMs.
> I'm looking at different options on how to update vmware-tools on many base
> One option is to use web GUI to create new image revision with updated tools
> for each image.
> Other option would be to create temp. VMs using persistent disk images
> pointing to base images .vmdk files, then update vmware-tools and delete
> temp. VMs (in-place upgrade?).
> This will probably require full shutdown of VCL system to make sure no one
> is using any of the images during the upgrade.
> May be someone already done it and could share some recommendations ...
> Thank you,
> Dmitri Chebotarov
> Virtual Computing Lab Systems Engineer, TSD - Ent Servers & Messaging
> 223 Aquia Building, Ffx, MSN: 1B5
> Phone: (703) 993-6175
> Fax: (703) 993-3404