WilliamLam.com

Search Results for: cycling

VMware Software Defined Kit

by // 10 Comments

A hobby of mine when I am not playing with VMware technologies and such is riding on my road bike. I was pleasently surprise to find out this week that my VMware cycling kit has finally arrived! The cycling kit was designed by small group of VMware employees in their free time and Scott Jobe has been managing all the orders and logistics for the past few years. When I had first joined VMware and heard about this, I had just missed the deadline for submitting my order. This year, I made sure to keep an eye out once the new kits were available for order. With a holiday this week, I took my new kit out for a spin and it fits and looks great. I even dropped by our office for a quick picture 🙂

I would like to thank Scott and the team for putting all of this together, I know it took a lot of time including the re-makes, but I am sure everyone is enjoying their new VMware kits! Thank you!

Here are some additional pictures of the items I had purchased. All the clothing were custom printed by Louis Garneau.

Jersey (front & back)

Vest (front & back)

  Bib (front & back)

Arm Warmers & Gloves

Automating VMware Tools Upgrade Policy

by // 16 Comments

I received a question this week from a reader who was looking to change the VMware Tools upgrade policy for a few hundred virtual machines and wanted to know if it was possible to automate this. The answer is absolutely yes!

By default the VMware Tools upgrade policy is disabled and set to "manual" mode. If you want the vSphere platform to automatically check and upgrade VMware Tools upon a system power cycle, then you can enable it by going to Edit VM->Options->Tools->Check and upgrade Tools during power cycling.

To update this configuration, there is a property in the vSphere API called toolsUpgradePolicy which can accept two values: manual or upgradeAtPowerCycle.

Here is a vSphere SDK for Perl script updateVMToolsPolicy.pl that supports two types of operations: "list" and "update". The list operation will show you all VMs and their currently configured upgrade policy, by default they should be all manual unless you have changed it manually. The update operation will allow you to configure a list of VMs and policy you designate. This change can be done while the VM is running, you do not need to make any changes to the guestOS that is running.

Here is an example of the "list" operation:

If you want to take all the VMs that have "manual" policy and change them over to "upgradeAtPowerCycle", you can copy the output to a file and then use a find or UNIX/Linux grep command to search for entries that have the word "manual".

Here is the command you can use if you are on a UNIX/Linux system:

cat output | grep "manual" | awk -F '["|"]' '{print $2}'

Here is the command to get the first column which contains the VM display name:

cat output | grep "manual" | awk -F '["|"]' '{print $2}' > VMLIST

Lastly, you just need to take the previous command and redirect that to a file which will then be used in the "update" operation. You can also take the output and using an editor to get to the final output, use whatever you are comfortable with.

Here is an example of the commands listed above:

Now that we have the list of VMs we are interested in updating, we just need to select the policy and perform the "update" command. Here is an example:

So there you have it, you can now easily automate the the VMware Tools upgrade policy for any or all your VMs without having to edit each one manually.