Those links don't work but I was finally able to get in through http://kb.vmware.com and link through Most Recent.

The patching was smooth thru update manager - only had to shut down a handful of guests on the first host and then round robin'd the rest.

It would have been better if not for the VI Clients recent tendency to die every 5 minutes!

I just started using ESXi when it became free...and then this.

I just now applied the patch successfully after unsuccessfully attempting to do so from 2 different Windows XP installs in 2 different VMs (1 in VirtualBox 1.6.4 on Solaris the other on VMware Server 1.0.6 in openSUSE 11.0). It only worked after trying it in a native install of Windows. Maybe it's just not me RTFM'ing, but just in case anyone else tries this, it apparently doesn't work!

...Pete

Good Work,

Just to simplify the process for the beginners as me in the ESXi.

As I am starting to use the free ESXi this bug happened, and this was my first update.

What I recommend and what I did:

1- Install the remote client called VMware-VIRemoteCLI-3.5.0-104314.exe.

2- Go to start -> vmware -> VMware VI Remote CLI -> command prompt

this was my process:

C:\Program Files\VMware\VMware VI Remote CLI\bin>vihostupdate.pl --server xxx.xxx.xxx.xxx -i -b c:\downloads\ESXe350-200807812-O-BG.zip
Enter username: root
Enter password:
unpacking c:\downloads\ESXe350-200807812-O-BG.zip ...
( skipping verification : ESXe350-200807812-O-BG/ESXe350-200807812-I-BG.zip.si
g )
unpacking ESXe350-200807812-O-BG/ESXe350-200807812-I-BG.zip ...
( skipping verification : ESXe350-200807812-O-BG/ESXe350-200807402-T-UG.zip.si
g )
unpacking ESXe350-200807812-O-BG/ESXe350-200807402-T-UG.zip ...
( skipping verification : ESXe350-200807812-O-BG/ESXe350-200807403-C-UG.zip.si
g )
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 SuccessNot applicable : ESXe350-200807402-T-U
G. 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:
yes
Rebooting host ...

End Disconnect

That it...

the real deal is the command vihostupdate.pl --server xxx.xxx.xxx.xxx -i -b <zipped file with the update...>

And everything is ok now

Thanks

Carlos Henrique Cano

I installed ESXi about 2 days before the time license bug and was not to familiar with the product, it took me some time to figure out how to deal with the update, but I finally made it... To update, you, once again, need a windows machine and the patch (ESXe350-200807812-O-BG.zip). Instead of using the update manage like everyone else, you get a zip containing 3 zips files, an xml and the zips signatures, uncompress the inner zips, it will create a folder containing a patch per zip. Inside the folder created for each zip, there's a file named remoteInstall.exe. You need to run these executable in a command prompt beiing in the folder of the patch. You need to pass the adress of your host, your username and your password in clear on the command line. In unix terms it looks like this:

unzip ESXe350-20087812-O-BG.zip

cd ESXe350-20087812-O-BG.zip

unzip ESXe350-200807812-I-BG.zip

cd ESXe350-200807812-I-BG

./remoteInstall.exe -h <hostname> -u <username> -p <password>

Good luck

My supervisor prefers to use Update Manager to fix the bug in ESX 3.5 U2 (He believes that the new U2 should be better than the express patch).

We have tried for a number of time to download latest software via UM. Unfortunately, we keep on getting the "Metadata download failed" message. Is there any suggestion ?

Thanks

I don't think it matters if you use Update Manager or esxupdate. The express patch is the express patch regardless of how its applied and I don't see the "new" update 2 on the site as of yet.