Applying the Time Bomb Patch to an ESXi server

Anyone running a VMware ESX server has already heard about the time bomb issue with 3.5 update 2 and have hopfully fixed the issue by now.

But I wanted to post my findings wtih patching the ESXi 3.5 U2 server using the RCLI. This is the way you need to patch a host that is not being managed by VirtualCenter server that has update manger running.

First you'll need to install the RCLI sofware on your PC, (for this I'm going to cover using the Windows version of the RCLI.

This link will help download and install the RCLI software:
http://pubs.vmware.com/vi3i_e35/server_config/wwhelp/wwhimpl/common/html/wwhelp.htm?context=server_config&file=sc_use_rcli.18.8.html

You will also need to get the u2 patch - that can be found at http://www.vmware.com/landing_pages/esxexpresspatches.html

The file you need can be found at - http://www.vmware.com/go/esxiu2patch081208

If you did a default install of the RCLI software a command prompt link will be created in the vmware folder that will take you to the following location (Start All Programs VMware RCLI)

C:\Program Files\VMware\VMware VI Remote CLI\

Once at thsi command prompt change into the bin folder making your path
C:\Program Files\VMware\VMware VI Remote CLI\bin>

Now copy the ESXi patch that you downloaded and put in the bin folder, file should be called ESXe350-200807812-O-BG.zip

Now you are ready to install the patch to your ESXi host - - -

First lets find out what versions your ESXi box is currently running - from the bin location run the following command.

vihostupdate.pl --server 10.10.1.104 -q
Where 10.10.1.104 is your ESXi IP or name - and you will be promted for an id and password of the host.

You will see results that look like this - assuming you are running ESXi 3.5 u2 gold code.
VMware ESX Server 3i 3.5.0 build-103909
Installed packages:
firmware 103909
viclient 103682
tools 103909

Run the following command from this location
C:\Program Files\VMware\VMware VI Remote CLI\bin>

vihostupdate.pl --server 10.10.1.104 -i -b ESXe350-200807812-O-BG.zip

Where 10.10.1.104 is the name or IP of your host. (its important to put the -i before the -b)

The above command will prompt you for an ID and password to the host - enter it and the patch will connect to the host and begin the install.

The fist step of this command will extract the zip file to the RCLI server; that is what the -b switch does - if you look in the Bin folder on your RCLI server will will see four folders get created.
The ESXe350-200807812-O-BG folder contains the matadata.xlm file that xml file is called buy the script and it applies the patches. The other three folders contain the actual patches; one for the firmware, one for the tools and the last is for the viclient.

When you run the command you will see the following output -
Enter username: root
Enter password:
unpacking ESXe350-200807812-O-BG.zip ...
( skipping verification : ESXe350-200807812-O-BG/ESXe350-200807812-I-BG.zip.sig )
unpacking ESXe350-200807812-O-BG/ESXe350-200807812-I-BG.zip ...
( skipping verification : ESXe350-200807812-O-BG/ESXe350-200807402-T-UG.zip.sig )
unpacking ESXe350-200807812-O-BG/ESXe350-200807402-T-UG.zip ...
( skipping verification : ESXe350-200807812-O-BG/ESXe350-200807403-C-UG.zip.sig )
unpacking ESXe350-200807812-O-BG/ESXe350-200807403-C-UG.zip ...
Installing : ESXe350-200807812-I-BG
Copy to server : VMware-image.tar.gz ...
Copy to server : VMware-OEM-image.tar.gz ...
Copy to server : descriptor.xml ...
Copy to server : install.sh ...
Copy to server : contents.xml.sig ...
Copy to server : contents.xml ...
Removed ESXe350-200807812-I-BG Success Not applicable : ESXe350-200807402-T-UG. Skipped.Not applicable : ESXe350-200807403-C-UG. Skipped.

The host needs to be rebooted for the new firmware to take effect.
Type 'yes' to continue:

Type yes to re-boot the host, when the server is finished re-booting us the -q command to verify the patch level you should be at the following levels on the three versions.
VMware ESX Server 3i 3.5.0 build-110180
Installed packages:
viclient 103682
tools 103909
firmware 110180

You'll notice that only the firmware verison is changed.

ESXi running without no USB key needed

So today I confimed (again) that you do not need to keep the ESXi USB key attached to the server once its loaded. You can make all the changes to the server, all without the bootable USB key physically attached....


Now why??? No idea even why I tested it, and have no real reason for the ability to do it. But its cool, server with no hard drives and no USB key (internal or external) running ESXi and hosting VMs. Not that is a hypervisor.

BUT - the ESXi web page will work but the VI Client download link will not work unless you attach the USB drive again. That file is not loaded in to memory.