Scrolling through all of these other videos but none that are just directly to the point of "THIS IS HOW YOU DO IT" So i truly appreciate the time and effort sir! Thank you! I am also still seeing the weird bug in the console where it shows the "temp" IP/FQDN. Just updated from 8.0.2 to 8.0.3
Is this when selecting the PG for deployment of the new appliance, right? When connecting to your deployment target, are you connecting to vCenter or an individual host? I've not tested an ephemeral port, would have to test it.
3 หลายเดือนก่อน +1
Why do we need an iso now? It used to just download from the update servers
The 'vCenter Lifecycle Manager Service' is different from the 'vSphere Lifecycle Manager Service', understand that can be confusing. The iterative patches for each respective version are still pulldown from the VMware repos, however when upgrading vCenter from U1>>U2>>U3, a new appliance is deployed and lots of the maintenance can be done in advance to save time, and the ISO is required for this kind of upgrade. I hope that helps, check out blog below core.vmware.com/blog/vcenter-reduced-downtime-update-vsphere-8-u2
Scrolling through all of these other videos but none that are just directly to the point of "THIS IS HOW YOU DO IT" So i truly appreciate the time and effort sir! Thank you! I am also still seeing the weird bug in the console where it shows the "temp" IP/FQDN. Just updated from 8.0.2 to 8.0.3
Did you try rebooting the newly deployed appliance, I recall encountering that in my homelab as well with a previous 8.x upgrade.
Awesome vid Sarg! 😎👍
Thanks 👍
when trying to pick the port-group that my other vcenter is in (it is an ephermeral type) it says the provided network name is not valid
Is this when selecting the PG for deployment of the new appliance, right? When connecting to your deployment target, are you connecting to vCenter or an individual host? I've not tested an ephemeral port, would have to test it.
Why do we need an iso now? It used to just download from the update servers
The 'vCenter Lifecycle Manager Service' is different from the 'vSphere Lifecycle Manager Service', understand that can be confusing. The iterative patches for each respective version are still pulldown from the VMware repos, however when upgrading vCenter from U1>>U2>>U3, a new appliance is deployed and lots of the maintenance can be done in advance to save time, and the ISO is required for this kind of upgrade. I hope that helps, check out blog below
core.vmware.com/blog/vcenter-reduced-downtime-update-vsphere-8-u2
First!