We are preparing to upgrade from vSphere 5 to vSphere 5.1 and I need a little guidance using Update Manager.
I recently installed Update Manager and the associated plugins. It shows that I have 6 critical and 41 non-critical patches for each of our 3 ESXi hosts. We are currently running ESXi 5.0.0 Build 474610, vSphere Client 5.0.0 Build 455961 and VMware vCenter Server 5.0.0 Build 913577.
I have heard that it is best to first install all incremental patches for 5.0 before performing the 5.1 upgrade. Can anyone confirm this is best practice?
Also, since we obviously did not keep up with patches since there are 47 outstanding how should I go about getting caught up? Can I just put a host into maintenance mode and remediate all 47 patches at one time? Is there anything I should be concerned about or do to prepare for this?
**I have plenty of available resources to evacuate one host at a time so that isn't a concern for upgrading.
It is better to actually install all incremental patches before updating.
I found full detailed documentation for the update to 5.1 here:
Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!
In this article, I am going to show you how to simulate a multi-site Lab environment on a single Hyper-V host. I use this method successfully in my own lab to simulate three fully routed global AD Sites on a Windows 10 Hyper-V host.
Teach the user how to configure vSphere Replication and how to protect and recover VMs
Open vSphere Web Client: Verify vsphere Replication is enabled: Enable vSphere Replication for a virtual machine: Verify replicated VM is created: Recover replica…