Hi,
We have a Horizon 7.3 environment and vCenter 6.5. We are planning to build a new Horizon environment on the latest version 7.12 and configure it on the same vCenter.
We are using only Instant Clones in the 7.3 environment and we will use only Instant Clones in the new one.
Do you know if there are any issues with having 2 horizon environments pointing to the same vCenter for Instant Clones?
I checked a previous discussion (2 Horizon Deployments using same vCenter ) and someone said that there is a 1:1 relation between vCenter and Horizon but I am not sure if that only applies when using View Composer?
Thanks,
Javier
Hi JavierBernal
In case of linked clones, a vCenter Server instance can be associated with only one VMware Horizon View Composer service. Hence only one-to-one mapping is supported here (Configure View Composer Settings ).
However in case of instant clones, there is no such limitation, you can point same vcenter server to other horizon environment as well as long as your desktop pools are unique (name/ID) in both environment.
Hi JavierBernal
In case of linked clones, a vCenter Server instance can be associated with only one VMware Horizon View Composer service. Hence only one-to-one mapping is supported here (Configure View Composer Settings ).
However in case of instant clones, there is no such limitation, you can point same vcenter server to other horizon environment as well as long as your desktop pools are unique (name/ID) in both environment.
Thanks for confirming that!