Multiple domains under one vcenter cluster

[john_its]

Hello,

I have one vcenter cluster. The vcenter is joined to Domain A and was added as authentication source the AD of Domain B.

Admins from both domains can login properly.

We have 2 connection servers and 2 composer servers that are joined to Domain A.

Currently we have pools on Domain A which works fine.

Trust between Domain A and B is not possible.

So what should we do in order to create new pools for the domain B using the same vcenter cluster?

Thanks

[RyanH84]

Hi,

At my place of work we run a secure environment, which utilises VDI as the "Jump box" for management into the system.

Our VDI compute cluster + vCenter and View Servers all live in our management domain. MGMT.LOCAL.

Across the entire platform, we have other environments: DEV.LOCAL, PROD.LOCAL, etc.

For each domain, we treat it as a separate build, which requires 2 connection servers and a composer server (floating linked clones) to be built and joined to a domain (DEV.LOCAL). Then, the DEV.LOCAL connection servers talk to the MGMT.LOCAL VDI vCenter server, using a specific service account created on the MGMT.LOCAL domain. But it uses it's own domain for AD Computer objects, GPO, User entitlements, etc.

That's a way we harness multiple domains under a single compute cluster. Happy to answer further questions about it if you want?

[john_its]

Hello Ryan,

So what I need it's just different composer and connection servers for each domain (along with the specific service accounts), and we are good to go. Correct?

[RyanH84 · Accepted solution]

Hi,

That is what we have here! You will need to make sure that your composer server (if you use one) also has a database in the new domain too. (We use SQL Express on the Composer server itself).

You just need to point the new domain connection servers at the existing VDI vCenter pod with the correct role/access with a service account on the original domain.

Happy to help further if you need it!

[john_its]

Thanks a lot for your help Ryan