A while ago VMware released Update 1 of vSphere 4 and some time before that it released vSphere 4. In my homelab I have one ESXi host and vCenter as a VM running on top of it. Upgrading from ESXi 3.5 to vSphere was quite easy using the special Host Upgrade Utility shipped with the vSphere client.
Upgrading from ESX4 to ESX4 Update 1 is something different. As I run ESXi from a USB flash device I did not feel like creating a new USB device with the latest version and importing all VM’s etc.
I wanted an upgrade without too much re-configuration. Normally I would use Update Manager to do this, but since it is installed on my vCenter server and that runs virtual and there is no other host to migrate it to, this is not an option.
I used a virtual clone of my vCenter server and took it to my laptop running with VMware workstation. Since the vCenter now left the ESXi host I was able to perform the upgrade of ESXi.
- Shut down the vCenter Server;
- Install VMware Standalone Converter somewhere, except on vCenter;
- Using Standalone Converter export vCenter in Workstation format to an location outside ESXi;
- Using VMware Workstation power up the exported vCenter server;
- Reconfigure the Network (IP-address) of the workstation vCenter instance;
- Create a baseline containing ESX (i) Update 1 and assign it to the Host;
- Make sure all VM’s on the ESXi Host are powered off or suspended;
- Connect to the Workstation instance of vCenter using the vSphere Client;
- Scan & Remediate host using vCenter Update Manager
One Response to Updating a single ESXi host homelab
Leave a Reply Cancel reply
Check the latest comments
- Mark Achtemichuk on Designing vSphere Platforms for Maximum Tier 1 Application Performance #BCA2817
- Dustin Snijders on VMworld Zoetermeer edition – KPN Consulting
- Anyone home? « Adventures in systems land on DELL announces integration of acquisitions in vStart offering
- Jij komt toch ook naar het Dutch VMUG Event 2009? | Virtual Lifestyle on It’s Official: Dutch VMUG meeting 2009 on December 11th 2009
- Matt O on Connecting ESX to SAN: PCI Device resource allocation failure
Blogroll
- Arne Fokkema
- Bjorn Bats
- Bouke Groenescheij
- David Marshall
- Duncan Epping
- Edwin Friesen
- Eric Sloof
- Frank Denneman
- Gabrie van Zanten
- Hugo Peeters
- Ivo Beerens
- Joep Piscaer
- Kenneth van Ditmarsch
- Manlio Frizzi
- Mike Laverick
- Richard Garsthagen
- Roy Mikes
- Sander Daems
- Simon Long
- The official Dutch VMUG
- Tomas ten Dam
- Vincent Vliege
- Virtual Strategy Magazine
- virtualfuture.info
- Virtualization.info
- VMGuru.nl
Archive








Can we see this in a PowerCLI script