VMware Tools Update Policy, errrrr, Updating

After hearing about the bug with ESX 3.5 Update 3 where a vMotion would cause a tools upgrade, and consequentially a VM reboot, I wanted to check and verify that my VMs would not exhibit this behavior. Apparently the bug is present when the tools update policy is set to “Update at Power On”. (Yes, I admit this bug has been known for a while, I just kept forgetting to post this script.)

There are a multitude of other scripts (including the powershell cmdlet “update-tools”) out there to kickoff a tools update task, so I wasn’t interested in that, all I wanted was to know the update policy and be able to change it.

This perl is the result of that…

5 thoughts on “VMware Tools Update Policy, errrrr, Updating”

  1. Hi,

    I tried out your script but I’m getting this message at execution:

    Can’t modify non-lvalue subroutine call in chomp at CheckVMwareToolsUpgradePolicy.pl line 78, near “))”

    Found some perl threats about this issue, but could not really do something with the solutions…

    Thx for your help.

    Regards Oliver

  2. Hello Oliver,

    It looks like I borked the usage of chomp there. Chomp returns a the number of characters that it removed from the string, so it shouldn’t have worked at all. (For reference, the context I have above is how PHP’s trim command works.)

    By changing line 78 to look like the following, it should work:

    chomp( my $provided_vm_list = Opts::get_option('vm') );

    Sorry for the confusion.

    Andrew

Leave a Reply