For a while we tried over and over again to install patches on our company’s VMWare ESX 3.5 and failed miserably. Until today! We discovered that the sequence in the install zip file provided by VMWare had the wrong order. I guess I should have realized that much earlier but the error messages were so misleading.
There are only a view steps to do it right:
- Setup a web server (Apache is better than IIS, you don’t need to configure mime types) and copy all unzipped patches into a directoy accessible through the web service,
- then run “esxupdate -n -r http://myrepo.domain/ESX-3.5-xxxx/ update” on each of these dirs in the correct order (if a required patch is missing install it first),
- reboot the server.
Well, this VMWare ESX is a rusty piece of crap, no shit, I am just to lazy to read hundreds of pages to perform an update (oops, just 8). 😉
Let’s see if this solves our license problem?