1 person found this helpful
As long as the vCenter Server version supports the Horizon version, you may upgrade. However, keep in mind that provisioning, and deleting VMs will not work while vCenter Server isn't available, so plan the upgrade carefully, and consider pausing provisioning during the upgrade.
Thank you Andre. Certainly we will have close look on provisioning or deleting the VM's during the Upgrade. How about actual connectivity during the upgrade, i.e Will existing full cloned VM's , can be accessible through connection broker during the Vcenter upgrade.
I recommend adding a couple of extra desktops just in case and disabling provisioning during the upgrade. The extra desktops to cover yourself during the upgrade and when the upgrade is done, you can just remove them.
running connections or new connections to existing VDI VMs will not be affected by a vCenter update. Only tasks, that use vCenter functions (cloning etc) will not work. So if you are using full-clones your users won't notice anything from your update.Best regards
Further to this, hope you have read the below
If you upgrade vCenter Server to vSphere 6.7, then all or some of the ESXi hosts in the cluster must be upgraded to vSphere 6.7. Else, the instant-clone desktop pools might not work correctly.
I found that while planning for Horizon upgrade.With Great Regards,1 person found this helpful
vExpert 2012-2017 | VCP3-5 | VCAP5-DCD | VCP-NV | vSAN Specialist | VDI | Germany
Found Upgrade vCenter Server article which states "New Desktop cannot be launched" . Could you please clarify will new desktop connection get impacted during upgrade or not.
Note: We are using full linked Clone model.
During the vCenter Server upgrade, existing remote desktop and application sessions will not be disconnected, but the following functionality is not available during the vCenter Server upgrade:
- Remote desktops that are in a provisioning state will not get powered on.
- New desktops cannot be launched.
- View Composer operations are not allowed.
1) Instant clone API changes in 6.7; I believe you need to re-push your pools after the upgrade so that the parents leverage the new API. Until then, provisioning will fail.
2) While connectivity won’t be affected, keep in mind for full clones; if a user shuts down their desktop during the upgrade, it will be inaccessible since Horizon can’t power it on until vCenter is accessible again. Just something to keep in mind.