I then uploaded the offline bundle on an SSD-backed datastore on the server called "/vmfs/volumes/My SSDR610." After uploading the offline bundle to the ESXi host, I connected to the ESXi host using Pu TTY, an SSH client, and verified the version of ESXi that the system was running by issuing the following esxcli command: After waiting about 10 minutes, I received a message in Pu TTY indicating that the system was updated and needed to be rebooted.
From a browser visit the VMware patch portal, locate the update you want to download and install, (here it’s VMware 5.0.0 Update1). Note: Patches after major updates are cumulative, I also downloaded the ‘latest’ patch. When complete, you will need to ‘scroll up’ and make sure it says, “Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.” 13. I assume they cannot be v Motioned to another host as this would require v Center, in which case why aren't you using VMware Update Manager?! Open a VMware v Sphere CLI command prompt C:\Program Files (x86)\VMware\VMware v Sphere CLI\-i -b c:\Temp\ESXi410-201010001--server=thunder Enter username: root Enter password: Please wait patch installation is in progress ... You will now see the build number has changed on that host to confirm the update the update has been installed.The update completed successfully, but the system needs to be rebooted for the changes to be effective. Your will see in the v Sphere client the update is installed on the host. NOTE: If you fail to put the host into maintenance mode you will see the error below and it will not allow the update to install:-i -b c:\Temp\ESXi410-201010001--server=thunder Enter username: root Enter password: Please wait patch installation is in progress ...After the update, I am applying the latest patch with the same esxcli syntax, like so; 16. Once the host is back online, connect and take it out of maintenance mode. Then locate the folder containing the update software and patches.