<div>
Well no, but I could throw some in there or keep them in the old vCenter. Not sure which way to go.
</div>


<div>
You need to have hosts, which host the VMs.
</div>


<div>
I do have hosts in the first vcenters new cluster that will host the VDI machines. Why remove them from inventory and add them to the new vcenter when all I need is to use the new vcenter for is composer/vcenter operations?
</div>


<div>
okay, if all you want is for composer, leave as is!
</div>


<div>
I'll lab it and report back
</div>


<div>
Well I left as is in my lab and sure enough, once you create a pool and choose the new vCenter server for provision operations, it asks you which parent VM to use for replicas. Obviously, it's looking at the new vcenter, which has no hosts or VMs. I think this means I can't simply create a new cluster and hosts within my existing VMs and just add a new vCenter server in the View Administration console.<br />
<br />
Unless I'm missing something?
</div>


<div>
That's why I said vCenter Server must manage Hosts and VMs, add Hosts to it.
</div>


<div>
That was easy enough. It was a little pain to recreate another vDS with all the settings, HA/DRS configs and permissions. Otherwise, we just added the new vCenter to the View console and made sure it was checked during pool creation. Once new VMs were up, we unassigned groups from the old pool and onto the new. I even used the same composer
</div>


<div>
<div class="content wysiwyg-content">
EE,<br />
<br />
In short, I'm trying to add a vCenter server specifically for virtual desktops in my View environment in order to separate their operations from server operations. The workload kills our vCenter often.<br />
<br />
To reiterate, I already have a vCenter called VCSA_1 for both servers and desktops. I'm trying to separate the two to offload the composer/vcenter operations from the server operations.<br />
<br />
I need to add a new vCenter called VCSA_2 to my Horizon View desktop environment.<br />
<br />
So far I have:<br />
1) Created a new cluster on VCSA_1 called VDI_Cluster. <br />
2) Added a ESX host<br />
3) Created VCSA_2<br />
<br />
I guess I can now add the new vCenter to the Horizon View Administrative console? Is it ok that the new VCSA isn't configured with a datacenter, cluster or ESX hosts, since View is using VCSA_1?<br />
<br />
edit: VCSA 5.5 has no linked mode.<br />
<br />
Thanks in advance.
</div>
</div>


EE,

In short, I'm trying to add a vCenter server specifically for virtual desktops in my View environment in order to separate their operations from server operations. The workload kills our vCenter often.

To reiterate, I already have a vCenter called VCSA_1 for both servers and desktops. I'm trying to separate the two to offload the composer/vcenter operations from the server operations.

I need to add a new vCenter called VCSA_2 to my Horizon View desktop environment.

So far I have:
1) Created a new cluster on VCSA_1 called VDI_Cluster. 
2) Added a ESX host
3) Created VCSA_2

I guess I can now add the new vCenter to the Horizon View Administrative console? Is it ok that the new VCSA isn't configured with a datacenter, cluster or ESX hosts, since View is using VCSA_1?

edit: VCSA 5.5 has no linked mode.

Thanks in advance.

VMware Horizon View additional VCSA?

VMware, a software company founded in 1998,  was one of the first commercially successful companies to offer x86 virtualization. The storage company EMC purchased VMware in 1994. Dell Technologies acquired EMC in 2016. VMware’s parent company is now Dell Technologies.

VMware has many software products that run on desktops, Microsoft Windows, Linux, and macOS, which allows the virtualizing of the x86 architecture.  Its enterprise software hypervisor for servers, VMware vSphere Hypervisor (ESXi), is a bare-metal hypervisor that runs directly on the server hardware and does not require an additional underlying operating system.