In a previous article, I blogged on how to update ESXi 4.0 to 4.1.
The pricipals I described could be applied to all updates of version 4 of ESXi / v Sphere that followed thereafter.
To cut this long story short – if you have v Center Server 5.5 update 2 you will have issues if you patch your hosts to the latest available patch level for ESXi.
VMware disabled SSLv3 (POODLE and all that..) in update 3b for ESXi meaning if your v Center Server is running update 2 you won’t be able to connect until the v Center is patched to update 3b as well.
If at all you need to enable SSLv3, you need to enable the SSLv3 protocol for all components. Now, there will be few scenarios where you cannot upgrade v Center Server to update 3b or you can’t do so even if its the recommended path and you simply want to have v Center update 2 working with ESXi update 3b hosts.After some considerations, and a great tip from Andreas, I went for a solution similar to the one he described in his SBHVL posts.Make to sure to read his posts if you’re also in the market for a new and affordable home lab.Now, if you are like me and need to perform an upgrade from ESXi 4.0 to ESXi 4.1 on an existing server, you may quickly find yourself a bit miffed at VMware for getting rid of the handy client-side GUI host-update-utility/server-update-utility that previously came with ESXi 4.0; instead, you will find yourself forced to work at the "unsupported" command-line within ESXi 4.1 for a bit, but do not fear, it is rather straightforward and worth the patience.This step may sound a bit complicated or cumbersome to anyone that is used to doing all this sort of thing with nice little management GUIs, but it really is not TOO bad even for a novice.